sounds easy enough. can anyone give me some more in depth instruction? i looked at the downloaded files and decided i should ask for help before i break my comp (with my luck it wouldnt surprise me at all)
GnuGP Video Tutorials
Oh and yes it definitely works with web mail.
The parts you omitted with "..." provide qualifying context, your flippant one line response misrepresents what I was saying.
What I was implying was that once configured you should encrypt all e-mail to recipients that can en/decrypt it. The "once configured" includes key exchange and what not so it implies a correspondent that is also setup and therefore knows about encryption. I further went on to say "between me and a select few individuals." No part of that requires any mass uptake of encryption so your guess about the percentage or people that know about encryption is completely irrelevant. <rant>Don't pick numbers out of your orifices; if you don't know use a vague qualifier like "most".</rant>
woh simmer down there...
For one I have never really truly needed encryption at all. I have been on the internet for so long already and have never sent 'sensitive information' over the internet and I never will.* (*by email of course*)
This is a Systems Security class. Last week we learned about PKI. I know the concept behind how it works, just maybe not about the programs that implement it.
Some other 'topics' we also studied;
PKIX
PKCS
X.509
ISAKMP
XKMS
CMP
WEP
Then some application protocols;
S/mime
SSL
TLS
WTLS
IPsec
PPTP
PGP
It just so happened that PKI interested me because encrypted email was something small and fun I could play around with for a few days --
NOT something I planned on using effective immediately.
<rant>Don't pick numbers out of your orifices; if you don't know use a vague qualifier like "most".</rant>
BTW where I
volunteer I assist the technology staff with day to day problems. There are roughly 300 staff members. I can list by name the few people who would know the dangers of un-encrypted mail. --And even fewer that would actually need it. It will be close to exactly 95%. This will-not reflect the rest of the world obviously, but it is pretty close
guesstimate on the percentile
of people at work that can understand PKI.
Even if I did suggest implementing it, I know exactly what they would say, and as a matter of fact what the other IT members would say; 'We have been fine up till now, why would we need to start this now?'
I should also note; the other, well one other member of the IT dept. who holds a higher rank than me, is really anti-non-Microsoft. So if it isn't from Microsoft or Microsoft recommended, then he will absolutely not do it. Its like he is afraid that using software under GPL has some 'licensing' issues or whatever and will not use it.
I say again
this was for fun, not to actually figure a way to for implementing it.
Your original question was asking about specific cases and my point is that if one has a need/desire to encrypt ANYTHING to a specific correspondent then it's pretty trivially (and a good idea) to then encrypt EVERYTHING to that correspondent.
Good idea, encrypting everything will mean that the sniffer will have to guess at which ones are worth breaking into, and sometimes to only find a 'Hi how are you doing?'. As soon as I start emailing someone
, I'll start doing exactly that.
---------- Post added at 10:26 AM ---------- Previous post was at 10:11 AM ----------
Oh yeah also on the topic of authentication, when say you would share your public key with me now, how would I know it is really you?
Well for starters I dont really know you so I couldn't, obviously, I wouldn't know that that was your public key with 100% assiduity endless I saw you make it myself.
This is probably why businesses use companies like Verisign, because to sign up you probably need to provide all information down to you SSN. So with businesses with 30+ members the 30+ members don't have to stand in the same room to know that that is your actual public key.