[Zope] New Version of Zope RPMS Available

[Jeff Rush]

I've upgraded my systems to Red Hat 6.1 and just this morning put up
new RPMs for Zope that fix problems reported to me re RH 6.1.  They
are Zope-2.0.1-*5*... and you can get them from:

    http://starship.python.net/crew/jrush/Zope/Zope2.html


On 26 Oct 1999 17:38:29 -0700, Karl Anderson wrote:

>I'll confirm that a vanilla RedHat 6.1 dist. with the Zope/zserver
>2.0.1-4 RPMs doesn't work.  This is bothersome because 6.1 (or maybe
>6.0) is the only RedHat dist. that comes with a recent enough Python.
>
>I think that this is because the system logger isn't listening to a
>port by default.  I changed /etc/rc.d/init.d/syslog.d to do this by
>default (with -r) & then restarted it.  For the paranoid, this is yet
>another port being listened to, with DoS vulnerabilities mentioned in
>the man page.

Correct and since I can't go changing your syslog settings from within
an RPM, I removed the env var I had set in zserver.sh that caused it
to log via syslog.  The original Zope tarball didn't log via syslog either
and I added it when I made the RPMs.  Compatibility is more important
and RPM users can always rework the logging to suit their admin
and security policy.  I shouldn't by default depend on syslog.

On Tue, 26 Oct 1999 19:54:59 -0600, Paul Grunwald wrote:

>Thanks for your help,  I was able to get it started by following your
>instructions.  I uninstalled the 2.0.1-2 RPMS and installed the  2.0.1-4. I
>commented out ZSYSLOG.  BTW,  the python syslog library was working before
>the change to syslogd, I wrote a little test program.  I had also tried
>the -r switch on syslogd but I didn't enable theZSYSLOG_SERVER; I think that
>was the key.  I also didn't see the problem with /var/zope/syslog.pid,
>the -2 and -4 RPMS put it in different places. I hope we can get this fixed
>because I don't want to leave the 514 port open.

The problem with /var/zope/zserver.pid only occured on some systems
and not others, for no apparent reason I could see.  However, the point
is moot as I've changed the /etc/rc.d/init.d/zope script to _not_ delete
the .pid file when shutting down zserver, so it will work everywhere.

One other change -- at Michel's suggestion Zope.cgi now points to
an empty file via the PCGI_PUBLISHER line, so that if PCGI cannot
find ZServer, it won't try to start one and mislead people when it gets
the euid/egid permissions wrong.  It will give a 500 - temporary error
window instead -- not perfect but the best that can be done w/o reworking
PCGIwrapper in detail.

-Jeff Rush