Cary O'Brien wrote:
I've done it this way:
http://www.zope.org/Members/otto/portfw
[snip]
How can this work? Won't Zope put a "base href=http://server:8080" tag
into the head of the document and mess things up? Won't you need
site-access to work around this?
-- cary
You're
Bill wrote...
Of course, it is entirely possible the user meant something other than s/he wrote.
;) But
that last one doesn't seem to indicate that.
To put it succinctly:
If you want Zope to bind to port 80 on *nix
you have few options:
o Change Zope to run SID ** Bad Idea
o
Interesting argument. However, consider this: if you completely trust your
'firewalled' box, then why not run the web server as root? One response,
Protection of the system from simple mistakes by trusted users? Also
root can do a lot more, such as putting interfaces into promiscious
mode.
Hello I'm the man who generate this jungly mailing
Simply, I use thesescripts:
---/usr/local/scripts/zstart-
#!/bin/bash
$ZOPE_BASE/start -u $ZOPE_USER -w 80 1/dev/null 21
---
the previous is
I've done it this way:
http://www.zope.org/Members/otto/portfw
It's also relatively easy to convince a hosting provider to add this, as
long as you have a dedicated IP address.
Perhaps I should have done a news item when I created this... seems a
lot of people have hacked around the issue is
I've done it this way:
http://www.zope.org/Members/otto/portfw
It's also relatively easy to convince a hosting provider to add this, as
long as you have a dedicated IP address.
Perhaps I should have done a news item when I created this... seems a
lot of people have hacked around the
Cary O'Brien wrote:
[...]
in your case is the fact that you mention your trust on users(humans are
the most easy to compromise, however that argument is a bit OT). However,
do you trust all of your webserver code? Do you trust your cgi-bin
scripts and applications? And by trust I not
Nitesh Dhanjani wrote:
yes, but it would solve the permission problem the original poster
mentioned.
No, because the orignal user wanted to _start_ Zope as user zope. Unless that user has
a
UID/GID of 0 (is, is root by another name), the file permissions are irrelevant. Now,
as
to
I receive an error becouse root hasn't granted the need privileges on
/Zope/var/ directory.
That is what i was responding to. I am aware of the facts you mention
regarding the 3 points you make below, and agree with them.
nitesh.
On Sun, 30 Jul 2000, Bill Anderson wrote:
Nitesh
Cary O'Brien wrote:
Well...
If you are running on Linux you could simply edit the kernel code to
elimitate the check on being root to bind to low ports. That's what
we did.
Which is an even worse idea.
Why? On a sufficiently firewalled off box, where the few logins are
Interesting argument. However, consider this: if you completely trust your
'firewalled' box, then why not run the web server as root? One response,
in your case is the fact that you mention your trust on users(humans are
the most easy to compromise, however that argument is a bit OT). However,
(Quoting reversed for sake of continuity.
On Sun, 30 Jul 2000, Cary O'Brien wrote:
Cary O'Brien wrote:
Well...
If you are running on Linux you could simply edit the kernel code to
elimitate the check on being root to bind to low ports. That's what
we did.
e
argument for the hack is backwards compatibility, any other explanation
usually ends up as rationalization or circular logic. My $.02.
-Original Message-
From: Bill Anderson [mailto:[EMAIL PROTECTED]]
Sent: Sunday, July 30, 2000 5:04 PM
To: [EMAIL PROTECTED]
Subject: Re: [Zope] Sta
Costagliola Giovanni wrote:
Il gio, 27 lug 2000, Oleg Broytmann ha scritto:
On Thu, 27 Jul 2000, Costagliola Giovanni wrote:
How can I to start Zope whit a different user than root and cath the
default HTTP port?
Use different way - start Zope as root, catch port 80
Cary O'Brien wrote:
Well...
If you are running on Linux you could simply edit the kernel code to
elimitate the check on being root to bind to low ports. That's what
we did.
Which is an even worse idea.
--
Do not meddle in the affairs of sysadmins, for they are easy to annoy,
and have
chown the var directory to the zope user. This is what I do with my setup.
On Sat, 29 Jul 2000, Cary O'Brien wrote:
Costagliola Giovanni wrote:
Il gio, 27 lug 2000, Oleg Broytmann ha scritto:
On Thu, 27 Jul 2000, Costagliola Giovanni wrote:
How can I to start Zope whit
Nitesh Dhanjani wrote:
chown the var directory to the zope user. This is what I do with my setup.
That will not let you bind to ports 1024.
--
Do not meddle in the affairs of sysadmins, for they are easy to annoy,
and have the root password.
yes, but it would solve the permission problem the original poster
mentioned.
On Sat, 29 Jul 2000, Bill Anderson wrote:
Nitesh Dhanjani wrote:
chown the var directory to the zope user. This is what I do with my setup.
That will not let you bind to ports 1024.
--
Do not
Il gio, 27 lug 2000, Oleg Broytmann ha scritto:
On Thu, 27 Jul 2000, Costagliola Giovanni wrote:
How can I to start Zope whit a different user than root and cath the
default HTTP port?
Use different way - start Zope as root, catch port 80 and drop uid.
I receive an error
Hi there..
I've just tried to install the new Zope with daemontools .. but I seem
to get an error after I initiate zope through dameontools with "svc -u
/service/zope" .. here what it continues to output;
16:52 zope@nexus [ /usr/local/zope/Zope-2.2.0-solaris-2.6-sparc more temp.txt
Traceback
I'm having difficulty starting Zope.
Versions:
Zope: 2.1.6, compiled from source with "python wo_pcgi.py"
Python: 1.5.2, (#2, Jan 17 2000) [GCC 2.7.2.1] on freebsd2
Python is compiled with pthreads enabled.
FreeBSD: 2.2.8 (yes, I know it is outdated).
Problem Description: The
+[ Loren M. McCarter ]-
| I'm having difficulty starting Zope.
|
| Versions:
| Zope: 2.1.6, compiled from source with "python wo_pcgi.py"
| Python: 1.5.2, (#2, Jan 17 2000) [GCC 2.7.2.1] on freebsd2
| Python is compiled with
22 matches
Mail list logo
