gpg - difference --encrypt-to and --recipient
MFPA
2017-r3sgs86x8e-lists-groups at riseup.net
Fri Jan 4 04:09:53 CET 2019
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi
On Thursday 3 January 2019 at 12:02:39 AM, in
<mid:20190103000240.08304C0157 at smtp.hushmail.com>, vedaal via
Gnupg-users wrote:-
> [2] encrypt only to the sender, but also encrypt the
> plaintext only
> to you, and store the encrypted file in your sent or
> other
> convenient folder, with the date and the recipient.
I guess if you had an MUA that encrypted separately to BCC recipients,
you could achieve this by BCC-ing yourself.
> [3] only for the overly paranoid who revel in tedious
> work-arounds 8^) :
> (a) Encrypt to both yourself and the recipient
> (b) Remove your own id packet from the ciphertext,
> (c) Re-calculate the crc of the ciphertext
> (d) Send the 'hacked' ciphertext along to the
> original recipient
> (e) Store the first ciphertext from (a) along with
> the one from (d), in your sent folder
> (f) now you will always be able to decrypt and
> retrieve the original plaintext
Would the ciphertext at (d) be much different than encrypting to the
recipient and hidden-encrypt-to your own key?
- --
Best regards
MFPA <mailto:2017-r3sgs86x8e-lists-groups at riseup.net>
He's an environmentalist - his arguments are 100% recycled
-----BEGIN PGP SIGNATURE-----
iNUEARYKAH0WIQSWDIYo1ZL/jN6LsL/g4t7h1sju+gUCXC7OkV8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0OTYw
Qzg2MjhENTkyRkY4Q0RFOEJCMEJGRTBFMkRFRTFENkM4RUVGQQAKCRDg4t7h1sju
+oXLAP9VS4KkIcC46uXVbRrxMMnMb3uU3DnyWlQAN3BnerHiXQD+Mew6XBCf1Vsy
arODK2wCXESbLQGsX+zXveX+bNpzegyJApMEAQEKAH0WIQRSX6konxd5jbM7JygT
DfUWES/A/wUCXC7Okl8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0NTI1RkE5Mjg5RjE3Nzk4REIzM0IyNzI4MTMw
REY1MTYxMTJGQzBGRgAKCRATDfUWES/A/139EACpg6S+lm2f56sqJzF4pWkosYFm
XzkgfMSIFgL241vmewDNAb54RsDtQ7sxZvy9jhIYVA0BFsRhmYmWNHjUWqEvb+iO
Q59yngpjJJkueCfVW6WiC1iCIURVZQ+wrSaQqks1/UyIk8JfwNPMntcjHbMPJt+M
hXxsxpBzy3wgbFfIxjNEx9XdcMOkt6wZHt1SmJQIhP2nw8QydqQAphcKEyBp7T/k
vRKOxExv6PgCWs93dCVWHhO/ek2BDBm5oDMZ0aFz/ZehhtRQapdQYZ5upWXBFcQc
DZgr/G+gDFtEmHjVyYugnBMT9sITau9WYZ+NedhIndwFNHmbd5EfI+i7KNd67kN0
zn0YT21Lh37IMBeki87XcDMiTvNfmejs3ogUgiNwbsr8SGcHpwojKStWJdzlw381
leN5VpLC921BojCgna+2k+xrx+z1+s6b5SZx3FV4118KuXoixRtfWTB52CB9KnzX
MRzfTy4IpjKjdpjqoLrQg7H+VlwVgHzU4p52OA0fWJHxDaYDZpl0mWA2ffL1qn4w
G2cMJKvOQacu2Me241z/tQ7FvLpZ6oKmeaFNM8wzN0vK2bYlh1PTrEE5hEDbWgIm
/J8Qmlg94QqPy7S/lB6BqaWb1lqe48AkdfjFiFwQYcw+3ibsnmhDmQyPe0OkWgqC
1fjyulUQXjXBkJ19bg==
=yhZM
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list