Added introduction to public key cryptography. Added some misc stuff to the doc. It needs prof read and ideas/questions. If any one has ideas please say now.
Created attachment 21488 [details] gnupg-user.xml
Note that this doc is not present in the summary table at the end of http://www.gentoo.org/doc/en/
A few quick comments on the fly: Please apply coding style (including titles on figures 5.x) "i" (as in myself) should always be in upper case, I think. In abstract: s/small// (do not dimish your work) s/Here you have chance to choose/Here you can choose/ s/Normally 1024/Generally/ (otherwise 2x normal in same sentence) s/password two times/password twice/ s/Luis's key/Luis' key/ (twice) s/Theorem (No prof here)/Theorem (No proof here)/ s/only one that knows/only one who knows/ s/have ower public/have our public/ ? s/a e-mail/an email/ s/Remenber/Remember/ s/importante/important/ s/you dont have/you don't have/ s/can creat messages/can create messages/ s/Key Servers where created/Key Servers were created/ s/retrive/retrieve/ s/authors key/author's key/ s/persons key/person's key/ s/, etc etc/, etc./ s/belong." ./belong."/ s/bellongs/belongs/ s/Lets imagine/Let's imagine/ s/good frind/good friend/ s/a a signed/a signed/ s/user that is new/user who is new/ s/don't talk of other tools/did not write about other tools/ "For more information go <here>." This is known as the "here" syndrome, please use descriptive text in link. Copyright notice is superfluous as you already included <license/>. Given your own notice, I suppose you would agree with the CC license. Sorry for not giving you a patch but I chose to read the .html version.
Created attachment 21801 [details] second version Thanks to Xavier for the corrections. This IS NOT the final version. I still want to write about Sylpheed, and maybe some windows tools.
Could you please apply the coding style to the document? See http://www.gentoo.org/doc/en/xml-guide.xml#doc_chap3 for more information. Also, <c> should not be used inside <pre>'s. Further, my suggestion (which you don't have to follow, it's just a suggestion) is to remove the credits/pointers to the other people. Users aren't interested in that. A professional document shouldn't contain that info imho.
Created attachment 22142 [details] Third version Well swift, most of what you asked is done. Please give a look at it. Also i did not remove the credits section because i feel that it gives a personal touch to the doc and does not make it less professional, if more people say that it does i will reconsider :). This is completly witought identation right now. I will work on that next and will finish this soon.
Created attachment 22145 [details] Fourth version Some internal fixups; I haven't searched for typo's and such yet (I'm only good at that at the first half of my day :)
Created attachment 22498 [details] Last version This is probably the last version. Only small typos now (i hope). If any one thinks i should talk about something i am missing please say so.
Erm, this is a translated version without all the fixups I did in the previous attachment :/
Created attachment 22519 [details] The real last version Hrrrr i sent the file from the "es" folder and not from the "en" folder :)
Created attachment 23608 [details] Reviewed and updated version This one is a fully reviewed and updated guide. I would commit it immediately, but I've changed some parts when you described public key cryptography. I know it isn't easy to describe without too much math so your first description does give a nice overview on the "complexity" of the situation. However I didn't like calling it PKC immediately because people might think it's that easy. Therefor I have changed it to read something about: """ As an (unrealistic) example... In this setup the two large prime numbers would be called the PRIVATE KEY. """ If you don't mind this little change I can commit.
I just read the text and could hardly notice the changes untill i did a diff, and then i noticed that the edits were very good. As far as I am you can submit it.
Committed. Thanks for rewriting (and maintaining) the guide!
