Re: Failing pim/messagelib tests for text/pgp data
Sandro Knauß <[email protected]> Wed, 27 Aug 2025 11:05:00 +0200
| Newsgroups | gmane.comp.kde.devel.pim |
|---|---|
| Message-ID | <3005663.vCJZsxu672@tuxin> |
--nextPart7386599.31tnzDBltd Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Sandro =?UTF-8?B?S25hdcOf?= <[email protected]> To: KDE PIM <[email protected]> Subject: Re: Failing pim/messagelib tests for text/pgp data Date: Wed, 27 Aug 2025 11:05:00 +0200 Message-ID: <3005663.vCJZsxu672@tuxin> In-Reply-To: <4983270.OV4Wx5bFTl@daneel> MIME-Version: 1.0 Hey, > I have added a work around to kmime which ensures that text/pgp isn't > decoded as text. https://invent.kde.org/pim/kmime/-/merge_requests/134 great - thanks. > Your commit message points to https://phabricator.kde.org/D8521 which points > to https://bugs.kde.org/show_bug.cgi?id=324365 where I don't see anything > about text/pgp. *shrug* Finally a grep in my archive helped to found matches with Roundcube 1.1.7 and 1.1.9 all sent in 2017. With the mail address I remember the person and how they do encrypted mail communication. The person used RCube to send/receive mails, but do the encryption on a air gaped device and used openpgp to encrypt the files on that device and send those encrypted files as attachment named xx.pgp. Those files were are not armored. RCube interpreted those attachments as text/PGP instead of application/octet- stream. So it is not a client that used those content-type but a php mimetype parser function that returned text/pgp for an encrypted data blob. Because I didn't wanted to use the commandline too - I added the support to handle text/pgp successfully. Regards, hefee PS: a sample: Subject: ... X-PHP-Originating-Script: 1008:rcube.php MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="BBBBB" Date: Sat, 25 Feb 2017 01:12:34 +0000 From: [email protected] Message-ID: <[email protected]> X-Sender: [email protected] User-Agent: Roundcube Webmail/1.1.7 --BBBBB Content-Transfer-Encoding: base64 Content-Type: text/PGP; name=test.text.pgp Content-Disposition: attachment; filename=test.text.pgp; size=1890 ENCRYPTEDCONTENTBASE64ENCODED --BBBBB-- --nextPart7386599.31tnzDBltd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmiuyjwACgkQ462wCFBg Vjbx7RAAjhDDFFjjLYp1cq9X6MPOJHliFfNVWEltnaSLRK1bD4Lvq/pggf8olWFd LNlw38p1JdmnEyF9TYGt5Wv1S25oTOtXPOZroXKuEGZWrfkTg5BeKOAhFXc7uBNf kxGFvWHlLhylgYgYLxYblu3WQaL0rOmarc3Xw02GzTgReslrFWhAmX0tCsDbY3a2 xJyQuWUyKTbLTogbM22tDSIhF39UDGJXaFcxYT/1oNjW33Nmlw6+govf/CjbXhyw nhrOdj5HRB8ZutdgrGExKdwRJ71axVhDiUcFqr77N6k3DByGHF0Rr4evloAqflFR yccxPB2+7Z0gNLmkFkjyVy83HarMTV7zLRcvfT+P7NtNnAtTrbSV5WVQM1E2UFWR s8q77q1c9yWDdwI9+i52R6e8s6NfeYC/Vg8WAiohNYEiIZO7xepzhkwqfQZVkWU2 TxYa957+Z0Fi/ZX8aM1rlCHcGLDJV+WhOyFIEq7pac9V7AvMLMrJTaaCAP/179Zs G5R1pHR+LlVQSGwcfuFx8WP0Wduw5DrQnoksiaovduUUe8QCXsvID+EStoZ8XQET YsSQGxUe+kBj9+C5AuVG6X23cvqnmpPWFC8MnY0IcaGrhboKE3Cf0leyKh9HrcJV KaN5nTsnovqEqoe9Qt+cv9gXvAtWlNfcbm8mGn4dSQOPCSPRhOg= =3ItA -----END PGP SIGNATURE----- --nextPart7386599.31tnzDBltd--