[Zope] Re: installation security best practice question

[Andreas Jung]

--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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope/attachments/20060315/8c2157b2/attachment.bin