[ Please don't Cc: public replies to me. ] Marc Singer: > Don't take this as volunteering, yet. I wonder if we can use pgp5? I > have scoured the documentation for it and cannot figure out if it is > export controlled or not. I assume it has the same restrictions as > pgp2 due to the necessary inclusion of RSA algorithms. Pgp5 is as export controlled as pgp2 is. Pgp5 is also not completely compatible with pgp2. If we're to replace pgp2 with something, it should be gnupg, which is at least free (pgp2 and pgp5 are non-free). BTW, in my opinion the new pgp2 maintainer should probably not be a new maintainer, if possible. The package is complicated and important enough that the maintainer should probably be someone we know[1]. However, I won't pick my successor, and (I forgot to say this earlier) volunteering messages should go to debian-devel, not to me. Lasu who is already going to sleep better not having to look at PGP source code anymore [1] New people are cool, but given that PGP is _the_ single package on which all of Debian's security against forged uploads rests, the new maintainer should be picked somewhat carefully. (I _really_ don't intend to criticize any new maintainers.)
Attachment:
pgpcxLG508coC.pgp
Description: PGP signature