Personal tools
You are here: Home Forums SecMX RFC Discussion : CLOSED 6. Security Considerations
Document Actions

6. Security Considerations

by Mike Pearson last modified 2006-11-11 12:32

SecMX is a building block for more secure email; it does not purport to be "the solution".

6.  Security Considerations

6.1.  What SecMX is not

   SecMX:

   o  Is not about sender authentication.  SecMX simply assumes that it
      happens (the technology and technique utilised are not important
      to SecMX);

   o  Assumes that the TLS connections are negotiated between the two
      parties;

   o  Assumes both parties are responsible for their own internal
      security;

   o  Assumes that DNS is good enough for now (DNSSEC [RFC4033] is a
      future option).

6.2.  SecMX and DNS

   A DNS hijack could potentially see secure email messages being routed
   to spoofed BERs or SORs.  If this were deemed to be a serious threat,
   upgrading the DNS system to DNSSEC ([RFC4033]) could help to
   alleviate this problem.

Security Considerations - Response

Posted by NeilSherratt at 2006-09-27 13:33

The above descriptions clearly show that TLS is the technology you use when you discard all of the hard bits about security and need to solve only the easy bits. Remember it’s easy to assume that Certificate Authorities (or ANY ‘Trusted Third Party’ for that matter) undertake proper due diligence on the certificate applicant - this is a concept that is directly at odds with good security practice.

Any system that allows anonymous users is inherently insecure regardless of what technology is used. Everything in this section clearly shows that SecMX is not and can never be a secure method to deliver emails. Moving to a TLS protocol, as previously mentioned, will not change anything.

Emails from one Government Minister will still end up stolen and found in the hands of another.

The above descriptions clearly show that TLS is the technology you use when you discard all of the hard bits about security and need to solve only the easy bits. Remember it’s easy to assume that Certificate Authorities (or ANY ‘Trusted Third Party’ for that matter) undertake proper due diligence on the certificate applicant - this is a concept that is directly at odds with good security practice.

Any system that allows anonymous users is inherently insecure regardless of what technology is used. Everything in this section clearly shows that SecMX is not and can never be a secure method to deliver emails. Moving to a TLS protocol, as previously mentioned, will not change anything.

I am relieved to see that the State Services Commission recognises SecMX will not work and trust they will NOT take it as a new New Zealand Standard for electronic messaging.

« December 2008 »
Su Mo Tu We Th Fr Sa
1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31
 

Powered by Plone, the Open Source Content Management System

This site conforms to the following standards: