By Date: <-- -->
By Thread: <-- -->

installation security best practice question




--On 15. MÃrz 2006 11:00:03 -0500 Tres Seaver <tseaver (at) palladion.com> wrote:

OK, after some investigation: the issue is not the weird UID/GID on the files (which get preserved when unpacking the tarball as root); the issue is that the person making the file had their umask set to harshly (0077, likely), which means that the files are not readable by anyone but the owner. A workaround is to change the readability after unpacking the tarball, e.g.:

 $ chmod -R a+r .

Andreas, can you confirm?

ACK

Usually I build the release on my Linux box where the umask is 0002
however 2.8.6/2.9.1 have been build during Pycon on my Powerbook where
the umask is 0077.

I recreated the archives and re-uploaded them just some minutes ago.

Andreas

Attachment: pgph0eSszTgsV.pgp
Description: PGP signature

_______________________________________________
Zope maillist  -  Zope (at) zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )