Well, you have to commend Mark's honesty. He did say, I really didn't
want to use this excellent mailing list as a sales platform. And he
answered the question.
It's better than being subversive and saying something like, I am a
_very_ _happy_ customer of company XYZ. They rule
On Mon,
I agree. If you are running in a production environment that is exposed
to the Internet definently stick with stable. It's much easier to compile
a few latest and greatest programs that fit your needs than it is to
keep track of and compile all of the security updates.
On Fri, 15 Nov 2002,
I agree. If you are running in a production environment that is exposed
to the Internet definently stick with stable. It's much easier to compile
a few latest and greatest programs that fit your needs than it is to
keep track of and compile all of the security updates.
On Fri, 15 Nov 2002,
NoCatAuth (nocat.net) does exactly this. Although I think NoCat is
designed with wireless in mind. Not sure if it works with normal wired
network cards, but I can't see any reason why it wouldn't.
On Wed, 30 Oct 2002, C. R. Oldham wrote:
I don't believe it's possible to have a user log in to
NoCatAuth (nocat.net) does exactly this. Although I think NoCat is
designed with wireless in mind. Not sure if it works with normal wired
network cards, but I can't see any reason why it wouldn't.
On Wed, 30 Oct 2002, C. R. Oldham wrote:
I don't believe it's possible to have a user log in to
kernel, etc... and as we all know, jumping from stable to unstable is
problem-prone and doesn't worth flawlessly every time.
Why jump all the way to unstable, why not use testing? Testing is
usually stable enough for most applications plus the various software
packages are pretty up to date.
kernel, etc... and as we all know, jumping from stable to unstable is
problem-prone and doesn't worth flawlessly every time.
Why jump all the way to unstable, why not use testing? Testing is
usually stable enough for most applications plus the various software
packages are pretty up to date.
how about setting the user's shell to /bin/true. this allows ftp, but no
login shell. so it may work for scp as well.
-- Forwarded Message --
Subject: scp, no ssh
Date: Wed, 9 Jan 2002 09:49:10 +0100
From: Robert Janusz [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
How to allow,
On Wednesday 09 January 2002 21:23, Joel Michael wrote:
On Thu, 2002-01-10 at 12:19, Tim Quinlan wrote:
how about setting the user's shell to /bin/true. this allows ftp, but no
login shell. so it may work for scp as well.
This is true, but you can still (probably) use ssh to execute
how about setting the user's shell to /bin/true. this allows ftp, but no
login shell. so it may work for scp as well.
-- Forwarded Message --
Subject: scp, no ssh
Date: Wed, 9 Jan 2002 09:49:10 +0100
From: Robert Janusz [EMAIL PROTECTED]
To: debian-isp@lists.debian.org
How
On Wednesday 09 January 2002 21:23, Joel Michael wrote:
On Thu, 2002-01-10 at 12:19, Tim Quinlan wrote:
how about setting the user's shell to /bin/true. this allows ftp, but no
login shell. so it may work for scp as well.
This is true, but you can still (probably) use ssh to execute
11 matches
Mail list logo
