diff options
| author | Owen Jacobson <owen.jacobson@grimoire.ca> | 2014-06-05 23:56:17 -0400 |
|---|---|---|
| committer | Owen Jacobson <owen.jacobson@grimoire.ca> | 2014-06-05 23:56:17 -0400 |
| commit | ef47cf878b0af030488e7d194c1e4266233643bf (patch) | |
| tree | 3a5a936f5d0906d7127d023e3bc93d1418022eb0 /wiki | |
| parent | b2120d75e4c340100b25a2045b141e3b26ca0414 (diff) | |
Fix quote marks.
Diffstat (limited to 'wiki')
| -rw-r--r-- | wiki/gpg/terrible.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/wiki/gpg/terrible.md b/wiki/gpg/terrible.md index b183ae2..6b11ac5 100644 --- a/wiki/gpg/terrible.md +++ b/wiki/gpg/terrible.md @@ -28,7 +28,7 @@ users. ## The Real Name Policy -The GPG community has a massive "legal names" fixation. [Widespread GPG +The GPG community has a massive “legal names” fixation. [Widespread GPG documentation](http://cryptnet.net/fdp/crypto/keysigning_party/en/extra/signing_policy.html), and years of community inertia, stand behind expecting people to put their legal name in their GPG key, and conversely expecting people to verify the @@ -62,12 +62,12 @@ even without publishing their personal identity. Sending a GPG-signed message to a non-GPG-using normal human being is a great way to confuse the hell out of them. You have two options: -* In-band "cleartext" signing, which litters the email body with technical +* In-band “cleartext” signing, which litters the email body with technical noise, or -* PGP/MIME, which delivers a meaningless-looking "signature.asc" attachment. +* PGP/MIME, which delivers a meaningless-looking “signature.asc” attachment. In both cases, the recipient is left with a bunch of information they (a) -can't use and (b) can't hide or remove. It might as well say "virus.dat" for +can't use and (b) can't hide or remove. It might as well say “virus.dat” for all the meaning it conveys. Some of this is not GPG's fault, exactly, but after over a decade, surely |