On Fri, 24 Jul 2015 17:49, ved...@nym.hush.com said:
PGP 2.x can be used as a uuencode, and automatically split a signed
and encrypted armored file into 100 smaller files ready to be emailed
and reconstitued by the receiver.
OpenPGP also defines such an armor option but it is not implemented
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Friday 24 July 2015 at 4:49:54 PM, in
mid:20150724154954.3fc5041...@smtp.hushmail.com, ved...@nym.hush.com
wrote:
[2] Large File Transfers PGP 2.x can be used as a
uuencode, and automatically split a signed and
encrypted armored file
On Thu, 23 Jul 2015 23:13, r...@sixdemonbag.org said:
1. PGP 2.6 is *small*. The original PGP specification (RFC1991) is a
small fraction of the size of the modern OpenPGP specification
(RFC4880). When it comes to trustworthy code, small is beautiful.
FWIW, RFC-1991 is not a complete
On 7/23/2015 at 2:58 PM, A.T. Leibson jupell...@riseup.net wrote:
Do people (other than John Young) still use PGP? Why would someone
want to do that?
=
The only possible reasons I can think of are:
[1] Remailer use,
Original remailers used PGP 2.x and even though some use GnuPG,
I know this list doesn't deal with PGP, but since no else does either
any more, it seems like the best place to start.
Old versions of PGP were at least FOSS-friendly, if not FOSS themselves,
so it's probably safe to discuss it here. :)
Do people (other than John Young) still use PGP? Why
