科技回声

On all the encryption tutorials I found they always assume 2 and only 2 people trying to talk privately.I wonder how would one encrypt a conversation between say 15 people.

This article also suggests that you should use a 2048 Bit key, and you really shouldn't. Better to go with 4096 Bit. And I guess every CPU is fast enough.

This does not go into the Web of Trust and having your key signed, maybe the most complicated part of PGP, and perhaps also its most important feature.

There seems to be also a windows implementation: <a href="http://www.gpg4win.org/" rel="nofollow">http://www.gpg4win.org/</a> (Wondering why the site doesn't use ssl, though)On a related note, I have a hard time understanding why a web site talking about digital security also doesn't have a certificate.

Did anyone else see reop recently? It's a sort of simple reimagining of easy-to-use public key crypto. <a href="http://www.tedunangst.com/flak/post/reop" rel="nofollow">http://www.tedunangst.com/flak/post/reop</a>

"To encrypt a File:"<pre><code> gpg -o encrypted_file.gpg –encrypt -r original.file </code></pre> # they didn't put recipient after -r ?

Best blog on using GPG that I have seen. Thanks!

On all the encryption tutorials I found they always assume 2 and only 2 people trying to talk privately.I wonder how would one encrypt a conversation between say 15 people.

This article also suggests that you should use a 2048 Bit key, and you really shouldn't. Better to go with 4096 Bit. And I guess every CPU is fast enough.

This does not go into the Web of Trust and having your key signed, maybe the most complicated part of PGP, and perhaps also its most important feature.

"To encrypt a File:"<pre><code> gpg -o encrypted_file.gpg –encrypt -r original.file </code></pre> # they didn't put recipient after -r ?

Best blog on using GPG that I have seen. Thanks!

Encryption with Gnu Privacy Guard (GPG)

7 条评论

Encryption with Gnu Privacy Guard (GPG)

7 条评论