Re: SSH access restrictions

2003-10-18 Thread Marc Schiffbauer
* Rudi Starcevic schrieb am 18.10.03 um 03:23 Uhr: > Hi, > > Is there anyway to resistict a non-root user's shell account ? > > For example once he/she is logged in is there any way to deny, say, > reading the /etc/passwd file ? > Can they be restricted like the way a user can be restricted usi

Re: SSH access restrictions

2003-10-18 Thread Rudi Starcevic
Thanks Marc, Thanks also to Russel. > I did it with pam_chroot which is really nice Great - I'll start looking here. Currently we only really offer FTP access but would like to include SSH access too. I know with the right permissions a user account cannot do any damage but I would just like t

Re: SSH access restrictions

2003-10-18 Thread Rudi Starcevic
Hi, Just a quick question on libpam-chroot. This package is not availalbe in 'stable'. I've only ever used 'stable'. It should be OK to grab this package from 'testing' and use it hey ? Thanks again Regards Rudi. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe".

Re: SSH access restrictions

2003-10-18 Thread Jason Lim
> Hi, > > Just a quick question on libpam-chroot. > > This package is not availalbe in 'stable'. > I've only ever used 'stable'. > > It should be OK to grab this package from 'testing' and use it hey ? Usually you can't... as they have dependency problems. What you need is a "backport" to stabl

Re: SSH access restrictions

2003-10-18 Thread Rudi Starcevic
Thanks Jason, > Usually you can't... as they have dependency problems. Well I think it may be OK to just use the 'testing' .deb. Why ? Because I just did. It all installed OK without any error's. I just downloaded it and dpkg -i it. I haven't used it yet as I'm still reading the readme but it ha

Re: How to investigate kernel failure?

2003-10-18 Thread Arnt Karlsen
On Sat, 18 Oct 2003 01:33:24 +0200, aCaB <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>: > > The above are stack dumps. As you can see the most-recently invoked > > function in each case was getblk(), so I'd say you need to check > > your filesystem (and/or replace the hard drive). > >