Ben Rasmussen wrote:
Hi Tom,
I am truly an idiot. After my last message I dug around a little more
and realized that I had my /home partition mounted noexec.
So, this is not a bug at all. I am really sorry for wasting your time
with this.
Thanks,
Ben
OK no problem, thanks for resolving it yoursel
Hi Tom,
I am truly an idiot. After my last message I dug around a little more
and realized that I had my /home partition mounted noexec.
So, this is not a bug at all. I am really sorry for wasting your time
with this.
Thanks,
Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
Hi Tom,
Sorry, I am an idiot. I was looking in syslog, not auth.log. Here's
what I'm getting in auth.log:
Feb 23 20:06:49 hostname sshd[9634]: Accepted password for scponly from
xx.xx.xx.xx port 32935 ssh2
Feb 23 20:06:49 hostname sshd[9636]: subsystem request for sftp
Feb 23 20:06:49 hostname
Hi Tom,
I did increase it up to 3, but nothing showed up in the logs.
Thanks,
Ben
On Wed, Feb 23, 2005 at 01:35:03PM +0100, Thomas Wana wrote:
> Ben Rasmussen wrote:
> > Package: scponly
> > Severity: important
> >
> > When using scponlyc, the connection is closed immediately
> following
> > s
Ben Rasmussen wrote:
> Package: scponly
> Severity: important
>
> When using scponlyc, the connection is closed immediately following
> successful authentication. This is scponly 4.0-1 on a pure-sarge
> machine. setup-chroot.sh was used to create the user & chroot. If
> user's shell is set to /u
Package: scponly
Severity: important
When using scponlyc, the connection is closed immediately following
successful authentication. This is scponly 4.0-1 on a pure-sarge
machine. setup-chroot.sh was used to create the user & chroot. If
user's shell is set to /usr/bin/scponly, user is able to co
6 matches
Mail list logo
