[Gpg4win-devel] signature in body: no-mime and new "double no-mime"
Andre Heinecke
aheinecke at intevation.de
Mon Aug 26 16:53:17 CEST 2013
Hi,
On Monday 26 August 2013 16:21:53 Bernhard Reiter wrote:
> On Monday 26 August 2013 at 14:58:13, Dr. Peter Voigt wrote:
> > > Some example messages are at
> > > http://wiki.gnupg.org/MailClients/Screenshots
> >
> > Well, thanks for this link. Unfortunately, I could not find any Outlook
> > example with an "double no-mime" signed message. Instead I see a new
> > term - at least new to me - called "opaque signed".
An opaque signature means that text that is signed is embedded in it. It's
what you get when you use "gpg --sign -a" without the detached option.
>
> Well, we need to adjust the terminology on some examples
> and probably also add some.
>
> Andre, can you add a "double no-mime" example mail please. :)
There is one already (as you can see in this screenshot):
http://wiki.gnupg.org/MailClients/Screenshots?action=AttachFile&do=view&target=kontact_opaque.png
Additionally here is the opaque signature of this message (Making it what we
call "double no-mime", clear text above an opaque signature):
--
Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-----BEGIN PGP MESSAGE-----
Version: GnuPG v2.0.19 (GNU/Linux)
owGVlM9rJEUUx8esLtgquCBevDzmEBPS3ZP5keykIS6zSn6sZCNZ172sSk33m+7a
rq5qq6rTGfAg6kE86cWrIv4DgnhaQQgI4sGrFw8ri/jj4EWPgq96MjEaPEhf6tf7
9nuf961677ELrYVLL/88vP31UfuPB775Zdw6eCr/YIf7nrcvYU/JhE2htw6jKq2M
hd5qtw/d9ajXjdb6cBW1zJhO4AC5RQ21VhYj7xn4z1BmoTuI1oZRt+/DczqEF9AF
vqR4av8Od98NVSDgEStKgVCgMSxFA0wjaZwcyawto06n5jkPU1mVaah02tljXDwr
OEprOjdijShNpqxxMU3cLRTCB5sxmRuYKE1DbkBwmYdwU9KCrSSzKKY+7EKsKpGA
VBYmXCbA5BT2KyuUyhuteX41txltQjtR1ZjmUgUFL7ANhqcSk3n+IexKY5ElpGyQ
KgGJdSNEEAoIHB6BjGDROlhFcbQYMyFIo61K9lqFJ5Lt0PNGEs6sMVtpR4pJ46qz
pHlkZyOq7yQRGmExxiRxYwncUkr2aQO1OzZVFaRIfchQNpPKILTTMoUgcPEQsHZT
qqqcMEKClsUZSanSciUpJYd4BrgmCkhbVAVL7jgDuAhXJ5dKqHQKSoI502TXIUaM
S63GbCymwIRxsUlzKmykRzLR6BORWX5uk52HfuoacgKUDiiRj5Y978UMCRExUJLg
C02dmMISM42YE3VNISyNI8ypd5aj/2e1Kyx2ODZH1uHZ4gIXE7V5yLFetEwT4c1c
Sdqyr87aF5YypW4mCXdh1O0pzBN1zM71WE1mGZ64Cpb2WM5lSt2c9ZHQO8+cA0Pg
CIaeGYON1SE6z/5T/stFjcuR5wUBeA1t2EEuMc4RXgdYWRlsBGuDbtDvr60O+0Fv
vQdufY6nrkMuLR6yxg4Jdrzd0ylsF+MdH65jRRd+W7Mxmax72YfBxurlAewbycb6
+G6ck95o+8zch50DuArd4cbG0NtGE2fHn0ysmRzfzTTqCLY03WR4XildMCn9fz9K
s2fmGpPBvuCH9OtbjG6CfmfrwdalhdbFhxbovfu45T38+PwRfPvP1ofXfvvx23s/
XIm9z35/hL/5xsq9X3/6rvXR+299ev37Jz6//e7SF/eXLj7qtb965cm/AA==
=Xevd
-----END PGP MESSAGE-----
More information about the Gpg4win-devel
mailing list