Question about pgp headers using GnuPG Inline option

RT Users
1

Hello,

I am trying to implement GnuPG on my RT (version 4.2.10) with the Inline
option, but when I send a message people are receiving this type of
wrapping :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

my message

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQEcBAEBCAAGBQJVpc9kAAoJEJ2MEvV/kJGBs6kH/iPSHRLOcXXYwz+tXqp4QmOL
pHmS1yPnAOTluanYul4Mromo6LIQNAHk6FdGPXDMBBBWf/0+GaeNW3q8ap6GKble
+r8pGuygb4fJAlMT4kjDSXVW+b2KeS3dSlSkRKOxnjiQiMfP7ISQ3zXtGYCGI2ix
d0HzRkQ/01qpqKA716CU+G6ft6drtdIDsRqHAg5r9TaEF0bw5lBrUhj4zaaYhAus
a/g+53JdtRqPZ4m7Ve0NT+409I+wxgWJQT74pR9YyYA8hYTh2kbcBKXlCh8BwGMt
SwXgJ4OnBYLJzbmnnXUGaCO/7bsya5aJqyL0d5sSwAxMeOukRY2LSWdVfgZMWuI= =C+re
-----END PGP SIGNATURE-----

instead of something like

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I vote YES on this important measure.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: See Alan’s GPG guide at https://futureboy.us/pgp.html

iQIcBAEBCAAGBQJT3MFeAAoJEF8rR1bthz0jslMP/RMRODVKLmLwZ3sMR62COGc/
0yQSh3c37qkkVjD0RvgdziHuCSSYelhNl7UMQofpdLonnJgPW3svlftE3Gn11JLp
ZYv2iMwCzwyM2eLYpSQoJBNnGZzQDGnZRBkFOwdkkohUSBjhPjiszYw3KwnpsuxG
I+m81IMJATR0wOylLumVdjbvS1/f9bOzBRvhgu2HS54lfPnl162RRZpycrrb5IOi
07QWIlUGVUdAxFUq4Jlm99KB17lQhri3zm6m7O5k0faD3IKFRTQGKseq7j88pRs6
j85v/cc35CHW9+66jcz7Y3UtOIj3gqDQd/Wj05YP01QSwSCuuVAezvXngljF8fLP
OKQhFpLoLnWvDPgX3nKwGbX52qZwLGN0bZduhOmMPYwKAEFAYDOOW7q+i/dyz5xT
od54j32QiNkSqDCVkvOT6dKiCdCa8GvtwwXPKa9X7+VZB2xYeJorJiaIesD7wyVN
CQDx11uMGMkpZ/BmCIA5mDIkDnUTIxHxNFpn2kS6nHJqmJ/LleTpAKLhPWuY1U28
YVraBzmAZ/Wj2Frq0utPi4cFf5r3x9jXIzie4fYrUjMKCN+CNfLL15Py/z9OY1ux
vvYdMiLAzL1Ujvjpyw7sCdc2KnbXaM9jmbBGjmVCMX/wGcGKT6cIxYnkR4NOW62L
jaBgelaHIL5kZ+E/kpS6
=wh+e
-----END PGP SIGNATURE-----

do you have any idea, why is it wrapping the pgp headers that way?

Best regards,

Mario

2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On Tue, 14 Jul 2015 22:51:55 -0500 Mario Góngora mariogongora01@gmail.com wrote:

I am trying to implement GnuPG on my RT (version 4.2.10) with the
Inline option, but when I send a message people are receiving this
type of wrapping :

Can you show your %Crypt, %GnuPG and %GnuPGOptions settings? What
version of GPG does gpg --version say you’re running?

  • Alex
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlWl4ZEACgkQMflWJZZAbqBi1gCdHYg/6/ZAbfv2a1DyCDggmJYY
MPYAn1Hz3vr0JA4LUhJ4m2ckFC3QSXc2
=/E5T
-----END PGP SIGNATURE-----

3

Hello,

Well, I am using this gnupg’s version: gpg (GnuPG) 1.4.16

And below are the options I am actually using for this plugin.

Set( %GnuPG,
Enable => 1,
OutgoingMessagesFormat => ‘Inline’,
);

Set( %GnuPGOptions,
homedir =>
keyserver => ‘pgp.mit.edu’,
‘always-trust’ => undef,
‘auto-key-locate’ => ‘keyserver’,
‘keyserver-options’ => ‘auto-key-retrieve’,
passphrase =>
);

Regards,On Tue, Jul 14, 2015 at 11:28 PM, Alex Vandiver alex@chmrr.net wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 14 Jul 2015 22:51:55 -0500 Mario Góngora mariogongora01@gmail.com wrote:

I am trying to implement GnuPG on my RT (version 4.2.10) with the
Inline option, but when I send a message people are receiving this
type of wrapping :

Can you show your %Crypt, %GnuPG and %GnuPGOptions settings? What
version of GPG does gpg --version say you’re running?

  • Alex
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlWl4ZEACgkQMflWJZZAbqBi1gCdHYg/6/ZAbfv2a1DyCDggmJYY
MPYAn1Hz3vr0JA4LUhJ4m2ckFC3QSXc2
=/E5T
-----END PGP SIGNATURE-----