I did it again... failed to hit the Reply to All button :(
------------------
According to what I'm seeing, it's only service that goes before the colon...
cvspserver : ALL : allow
With the ": allow" being optional.
DISCLAIMER: I've never used hosts.allow and hosts.deny, only firewall rules, so "what I'm seeing" is the results of about 15 minutes worth of looking at google search results. :)
-----Original Message-----
From: Andy Wardley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 24, 2001 10:34 AM
To: Template Toolkit List
Subject: Re: [Templates] Template Toolkit Developer Release 2.05c
On Wed, Oct 24, 2001 at 09:57:47AM -0400, darren chamberlain wrote:
> inetd is only necessary for pserver access.
[ssh details snipped]
> pserver is only necessary
> for anonymous access, and it doesn't sound like that's your goal.
That's one of the goals. Anonymous access for regular punters, ssh access
for me (who has a shell account) and other trusted developers (who don't).
I've got pserver running in a chrooted shell and it seems to be OK.
> As an aside, why does inetd care what the address is?
I don't know. Our box has numerous IP addresses and domain names.
If I do:
cvs -d :pserver:[EMAIL PROTECTED]:/template-toolkit login
then it works fine, but if I try:
cvs -d :pserver:[EMAIL PROTECTED]:/template-toolkit login
then I get dropped out of the bottom of the /etc/hosts.allow file with
the message "You are not welcome to blah blah blah":
# The rest of the daemons are protected.
ALL : ALL \
: severity auth.info \
: twist /bin/echo "You are not welcome to use %d from %h."
The docs seemed to suggest that adding the following line to /etc/hosts.allow
should do the trick:
[EMAIL PROTECTED] : ALL : allow
but it doesn't :-(
A
_______________________________________________
templates mailing list
[EMAIL PROTECTED]
http://www.template-toolkit.org/mailman/listinfo/templates
