[LINK] Telstra Clouds its Profit Results
kim at holburn.net
Sat Feb 11 21:13:46 AEDT 2012
Email encryption works OK to send encrypted emails to *one* other person who is technically capable of decrypting it and who has a public key you know and trust. To use email encryption you have to understand the technology and have all the recipients of your emails understand it too. This would mostly limit the people you could email to a fraction of the people you now email. You have to trust them and you all have private keys and keep them safe.
Sending an encrypted email to more than one person gets linearly (or more than linearly) more difficult. i.e. you can't use cc or bcc in encrypted emails. Encrypted email is not a simple plugin replacement for email.
On 2012/Feb/10, at 9:07 PM, Karl Auer wrote:
> On Fri, 2012-02-10 at 20:30 +1100, Jan Whitaker wrote:
>> And don't get me started on the University uses
>> of gmail, no matter how many complaints various
>> people have made. They have drunk the koolaid,
>> too. Bye-bye research confidentiality. Contract security anyone?
> Research confidentiality can be maintained across the open Internet by
> using encrypted email. If you have valuable information that must be
> kept from prying eyes, send it encrypted.
> It is not difficult for a moderately intelligent person to encrypt their
> emails. There are squillions of how-tos on the web.
> There are two main methids - certificates and keys.
> Certificates are somewhat easier to use, but be aware that they depend
> utterly on trust hierarchies over which you have no control; hierarchies
> that have already been compromised several times (that we know about).
> These hierarchies often have their peaks in jurisdictions that should
> give you pause for thought - like the US.
> Use keys (GPG or PGP) if you want absolute control over your own
> encryption, at the cost of a little more work getting your public key(s)
> distributed. This is the method I would strongly recommend.
> All major mail clients support both mechanisms. Both mechanisms can be
> used to sign, encrypt, or sign AND encrypt messages. No clients require
> that *all* emails be signed or encrypted - you can choose which messages
> you sign or encrypt, so you are still able to send emails to addresses
> that do not support encrypted emails.
> Regards, K.
> Karl Auer (kauer at biplane.com.au)
> GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017
> Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
> Link mailing list
> Link at mailman.anu.edu.au
IT Network & Security Consultant
T: +61 2 61402408 M: +61 404072753
mailto:kim at holburn.net aim://kimholburn
skype://kholburn - PGP Public Key on request
More information about the Link