-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Paul Pelzl пишет: | Another idea: it is possible that Sophos just looks at the .ZIP file | extension to decide that the file may be "unsafe." I wonder if simply | using a different archive name, e.g. "library.foo" would solve the | problem.
Here is test build with mangled name of library.zip (renamed to just 'python'). http://bzrdev.bialix.com/bzr-setup-1.2.0.dev.0-mangled.exe
Paul, can you test it? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHqAHSzYr338mxwCURApNmAJ47d6zJpjWs+eiFRBwLtFLwTiiZjACfZsdH cEbPGsNMPkf8M6BLsQofaqY= =/Eqy -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul Pelzl пишет:
| Another idea: it is possible that Sophos just looks at the .ZIP file
| extension to decide that the file may be "unsafe." I wonder if simply
| using a different archive name, e.g. "library.foo" would solve the
| problem.
Here is test build with mangled name of library.zip (renamed to just 'python'). bzrdev. bialix. com/bzr- setup-1. 2.0.dev. 0-mangled. exe
http://
Paul, can you test it? enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFHqAHSzYr 338mxwCURApNmAJ 47d6zJpjWs+ eiFRBwLtFLwTiiZ jACfZsdH LsQofaqY=
cEbPGsNMPkf8M6B
=/Eqy
-----END PGP SIGNATURE-----