11.05.2012 19:53, Chris Bannister kirjoitti: > On Fri, May 11, 2012 at 03:18:02PM +0100, Brad Rogers wrote: >>> Whilst the above is true, it's also true that inline signing isn't >>> going away soon because of certain companies reticence about >>> implementing it correctly or at all. >> >> Where "it" refers to the PGP/MIME standard, of course. > > Even if Enigmail made PGP/MIME the default, or even better remove inline > signing completely? > Enigmail uses mailing list software which makes PGP/MIME unverfiable, because of headers. -- [Mika Suomalainen](https://mkaysi.github.com/) || [gpg --keyserver pool.sks-keyservers.net --recv-keys 4DB53CFE82A46728](http://mkaysi.github.com/PGP/key.txt) || [Why do I sign my emails?](http://mkaysi.github.com/PGP/WhyDoISignEmails.html) || [Please don't send HTML.](http://mkaysi.github.com/articles/complaining/HTML.html) || [Please don't toppost](http://mkaysi.github.com/articles/complaining/topposting.html) || [This signature](https://gist.github.com/2643070) ||
Attachment:
signature.asc
Description: OpenPGP digital signature