You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a patch for Bug 755031: If a null byte appears in
a file name, Python zipfile.py retains it, but InfoZip
terminates the name. Null bytes in file names are used
as a trick by viruses. I tested WinZip, and it also
truncates the file name at the null byte.
I am about 80% sure this patch is a good idea, but it
does add a little more complexity. If the consensus is
that virus files are not Python's problem, I won't be
offended if it is rejected. It does seem useful to be
consistent with WinZip and InfoZip.
The patch also fixes a buglet: If a zipfile incorrectly
uses a directory separator other than '/', there was an
invalid complaint that the central directory name does
not match the file header name.
I also removed my name from the top of the file. It was
there for legal reasons which I believe no longer apply.
Many people have worked on this file besides me.
I don't believe there should be a test for null bytes in
the zipfile.py test suite.
Thanks Jim! Your patch works for me, and the test still
passes. I've checked it in on the trunk (rev 1.29, 1.30)
and backported it to release22-maint branch.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: