This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients gregory.p.smith, loewis, manis
Date 2009-08-24.01:05:29
SpamBayes Score 3.498525e-06
Marked as misclassified No
Message-id <1251075932.67.0.0659537823242.issue6749@psf.upfronthosting.co.za>
In-reply-to
Content
The decryption provided by the zipfile module is for the worthless
32-bit crc based "encryption" of zipfiles.  I think promoting the use of
that is a bad idea.

zipfile can be used by people to get their data out of such files.  We
should not encourage them to put it and/or their code into such a stupid
format.

-1 on supporting this.

Anyways as to implementation details, yes you'd need a way to accept a
key on the command line (or prompt for it using getpass?) and pass it to
the import mechanism at import time.  For zip files with only the
contained file data "encrypted" (the only thing the zipfile module
supports) a zip file could be checked for __init__.py and .py files
without decrypting first so that a password is only prompted for when
such a module is imported.

Again I don't see value in that.
History
Date User Action Args
2009-08-24 01:05:32gregory.p.smithsetrecipients: + gregory.p.smith, loewis, manis
2009-08-24 01:05:32gregory.p.smithsetmessageid: <1251075932.67.0.0659537823242.issue6749@psf.upfronthosting.co.za>
2009-08-24 01:05:30gregory.p.smithlinkissue6749 messages
2009-08-24 01:05:30gregory.p.smithcreate