| Rev | Author | # | Line |
|---|---|---|---|
| 10 | AristotlePagaltzis | 1 | !!! Why Worry About The Entire PublicKeyInfrastructure Thing? |
| 1 | PerryLorier | 2 | |
| 10 | AristotlePagaltzis | 3 | ! Verifying Remote Users |
| 4 | |||
| 5 | On the Undernet [IRC] network we have ScriptKiddie~s try and disrupt anything and everything they can. They have in the past forged emails from core developers with patches to be applied. If you contribute to FreeSoftware or the OpenSource movement then you are likely to have to interact with developers at potentially very remote locations, are you going to phone them up after every email to make sure they sent it? Using [GPG] and having a PublicKey in the WebOfTrust is now a prerequsite to becoming a [Debian] developer. | ||
| 6 | |||
| 7 | ! Automated Verification | ||
| 8 | StuartYeates | 8 | |
| 9 | Voting in [Debian] elections is performed automatically and securely using [GPG] signed [Email] votes. | ||
| 1 | PerryLorier | 10 | |
| 10 | AristotlePagaltzis | 11 | ! Future Proofing |
| 12 | |||
| 2 | PerryLorier | 13 | It takes time to build up a [PKI]. By getting your key signed today, and signing other peoples keys then when you need to send email to someone else in the world you will hopefully already have a trust path to them. |
| 1 | PerryLorier | 14 | |
| 10 | AristotlePagaltzis | 15 | ! Raise Awareness |
| 16 | |||
| 1 | PerryLorier | 17 | Setting up a loose [PKI] is very simple especially if your email client supports it natively. By signing outgoing messages you're raising awareness about signed and encrypted email. |
| 18 | |||
| 10 | AristotlePagaltzis | 19 | ! Setting a pattern |
| 20 | |||
| 1 | PerryLorier | 21 | If you have never signed an email in your life and someone forges an email from you containing important information (eg: "I am going to officially resign from my place of work"), then you can't argue that "if it was important then I would have sent it encrypted/signed! It obviously wasn't from me!" |
| 3 | CraigBox | 22 | |
| 10 | AristotlePagaltzis | 23 | ! Spam |
| 24 | |||
| 4 | PerryLorier | 25 | Any email that is encrypted (that you can decrypt of course...) is unlikely to be spam -- spending time encrypting the same message for millions of recipients costs the sender far too much in CPU time. Any encrypted email is obviously important and personal. |
| 3 | CraigBox | 26 | |
| 4 | PerryLorier | 27 | You can also use the web of trust as a way of figuring out who spammers are. If the email you recieved is signed by someone in your web of trust then they are unlikely to be a spammer. If it turns out that they are you can set their level of trust to "none" and perhaps lower the amount of trust of everyone who signed their key. A spammer will have a hard time finding people to sign their new key every time they want to send another email. |
| 5 | JohnMcPherson | 28 | |
| 10 | AristotlePagaltzis | 29 | ! Viruses |
| 30 | |||
| 11 | AristotlePagaltzis | 31 | Email [Virus]es typically send themselves to random recipients with a fake <tt>From:</tt> header, so yours will invariably be used even if you run a better OperatingSystem. If you have a history of signing your email, it is easier to convince other people that you didn't send them a particular email. (The Sobig family of viruses have been very successful at propagating using email). |
| 8 | StuartYeates | 32 | |
| 5 | JohnMcPherson | 33 | ---- |
| 34 | Part of CategorySecurity |
lib/blame.php:177: Warning: Invalid argument supplied for foreach()