On 11 Jan 2002, at 0:06, martin f krafft wrote:
--+xNpyl7Qekk2NvDX
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
also sprach Marcel Hicking [EMAIL PROTECTED]
[2002.01.10.1646 +0100]: /bin/true will log you out right
On 11 Jan 2002, at 0:06, martin f krafft wrote:
--+xNpyl7Qekk2NvDX
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
also sprach Marcel Hicking [EMAIL PROTECTED]
[2002.01.10.1646 +0100]: /bin/true will log you out right
What about setting ssh and scp to a diffenrent user an make appropiate sudo settings ?
Resent-Sender: [EMAIL PROTECTED]
Resent-Bcc:
Resent-Date: Thu, 10 Jan 2002 03:24:06 +0100
On Thu, 2002-01-10 at 12:19, Tim Quinlan wrote:
how about setting the user's shell to /bin/true. this allows
also sprach Tim Quinlan [EMAIL PROTECTED] [2002.01.10.0319 +0100]:
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.
nope. as i said, scp uses ssh and needs a shell
--
martin; (greetings from the heart of the
also sprach Gernot Glawe [EMAIL PROTECTED] [2002.01.10.0905 +0100]:
What about setting ssh and scp to a diffenrent user an make appropiate
sudo settings ?
and how do you want to get that working remotely? i supposed you could
create a shell script scp and a shell script ssh that would call
also sprach Joel Michael [EMAIL PROTECTED] [2002.01.10.0323 +0100]:
This is true, but you can still (probably) use ssh to execute commands,
like /bin/sh, and effectively get a shell.
that's not possible either. try it.
--
martin; (greetings from the heart of the sun.)
\
What about setting rbash as login shell and then PATH=/usr/local/bin
in .bash_profile and then ln -s /usr/bin/scp /usr/local/bin/scp and
and and then chattr +i .bash_profile
That is what i do and it works ( as far as i know .. )
--
__
What about sftp?
Clients should be available by now. I mean,
Windooze clients ;-)
As secure as scp, as restricted as ftp.
Cheers,
Marcel
On 9 Jan 2002, at 21: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
No way.
/bin/true will log you out right away,
and therefore you cannot start scp.
I've doublechecked this yesterday, and
even tried to put exit into the .bashrc
*This* did work fine, no ssh anymore, but scp
works. But! unforunatelly the user can scp
an new .bashrc or use ssh and rm to remove
On Thu, Jan 10, 2002 at 04:46:26PM +0100, Marcel Hicking wrote:
No way.
/bin/true will log you out right away,
and therefore you cannot start scp.
I've doublechecked this yesterday, and
even tried to put exit into the .bashrc
*This* did work fine, no ssh anymore, but scp
works. But!
also sprach Marcel Hicking [EMAIL PROTECTED] [2002.01.10.1646 +0100]:
What about sftp?
Clients should be available by now. I mean,
Windooze clients ;-)
As secure as scp, as restricted as ftp.
but you still need to enable a shell and ssh, because sftp does nothing
else but pipe over ssh...
also sprach Marcel Hicking [EMAIL PROTECTED] [2002.01.10.1646 +0100]:
/bin/true will log you out right away,
and therefore you cannot start scp.
I've doublechecked this yesterday, and
even tried to put exit into the .bashrc
*This* did work fine, no ssh anymore, but scp
works. But!
also sprach Tim Quinlan [EMAIL PROTECTED] [2002.01.10.0319 +0100]:
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.
nope. as i said, scp uses ssh and needs a shell
--
martin; (greetings from the heart of the
also sprach Gernot Glawe [EMAIL PROTECTED] [2002.01.10.0905 +0100]:
What about setting ssh and scp to a diffenrent user an make appropiate
sudo settings ?
and how do you want to get that working remotely? i supposed you could
create a shell script scp and a shell script ssh that would call
also sprach Joel Michael [EMAIL PROTECTED] [2002.01.10.0323 +0100]:
This is true, but you can still (probably) use ssh to execute commands,
like /bin/sh, and effectively get a shell.
that's not possible either. try it.
--
martin; (greetings from the heart of the sun.)
\
What about setting rbash as login shell and then PATH=/usr/local/bin
in .bash_profile and then ln -s /usr/bin/scp /usr/local/bin/scp and
and and then chattr +i .bash_profile
That is what i do and it works ( as far as i know .. )
--
__
What about sftp?
Clients should be available by now. I mean,
Windooze clients ;-)
As secure as scp, as restricted as ftp.
Cheers,
Marcel
On 9 Jan 2002, at 21: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
No way.
/bin/true will log you out right away,
and therefore you cannot start scp.
I've doublechecked this yesterday, and
even tried to put exit into the .bashrc
*This* did work fine, no ssh anymore, but scp
works. But! unforunatelly the user can scp
an new .bashrc or use ssh and rm to remove it.
On Thu, Jan 10, 2002 at 04:46:26PM +0100, Marcel Hicking wrote:
No way.
/bin/true will log you out right away,
and therefore you cannot start scp.
I've doublechecked this yesterday, and
even tried to put exit into the .bashrc
*This* did work fine, no ssh anymore, but scp
works. But!
also sprach Marcel Hicking [EMAIL PROTECTED] [2002.01.10.1646 +0100]:
What about sftp?
Clients should be available by now. I mean,
Windooze clients ;-)
As secure as scp, as restricted as ftp.
but you still need to enable a shell and ssh, because sftp does nothing
else but pipe over ssh...
--
also sprach Marcel Hicking [EMAIL PROTECTED] [2002.01.10.1646 +0100]:
/bin/true will log you out right away,
and therefore you cannot start scp.
I've doublechecked this yesterday, and
even tried to put exit into the .bashrc
*This* did work fine, no ssh anymore, but scp
works. But!
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 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 commands,
like /bin/sh, and effectively get a shell.
--
Joel
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
26 matches
Mail list logo
