PGP/MIME considered harmful for mobile

[Avi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

As usual, Robert explains it clearly and succinctly.

- --Avi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32) - GPGshell v3.77
Comment: Most recent key: Click show in box @ http://is.gd/4xJrs

iJcEAREKAEAFAk1qx1I5GGh0dHA6Ly9wZ3AubmljLmFkLmpwL3Brcy9sb29rdXA/
b3A9Z2V0JnNlYXJjaD0weEY4MEUyOUY5AAoJEA1isBn4Din5oCgA91VmmVWU15cj
jukZ2K71UTA9fisSfLWQbd9brx4aBukA+QHshimsCmiWTVQ/L3GcyhJkqpH7iqQT
6r9pPjoQXgP0
=B/Tt
-----END PGP SIGNATURE-----


----
User:Avraham

pub 3072D/F80E29F9 1/30/2009 Avi (Wikimedia-related key) <avi.wiki at gmail.com
>
   Primary key fingerprint: 167C 063F 7981 A1F6 71EC  ABAA 0D62 B019 F80E
29F9


From: "Robert J. Hansen" <rjh at sixdemonbag.org>
> To: gnupg-users at gnupg.org
> Date: Sun, 27 Feb 2011 12:21:35 -0500
> Subject: Re: PGP/MIME considered harmful for mobile
> On 2/26/11 9:24 PM, Jameson Rollins wrote:
> > http://josefsson.org/inline-openpgp-considered-harmful.html
>
> * IT DOESN'T HANDLE ATTACHMENTS.  That's fine with me: 95%+ of my
> messages don't require attachments.  Any technology that can hit 95% of
> the use case is fine by me.
>
> * IT DOESN'T LIKE CHARACTER ENCODINGS.  Works fine for me with Latin-1
> and UTF-8.
>
> * FORMAT=FLOWED DOESN'T WORK RELIABLY.  I don't use format=flowed in the
> first place.
>
> ... and so on and so on.  When I look at the objections to inline PGP,
> the more I realize inline PGP hits the sweet spot for me and for a great
> many other users.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20110227/65700af2/attachment.htm>