![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| restrict the user not to key in more than 50 chars | injeti | Shell Programming and Scripting | 18 | 08-16-2008 08:06 AM |
| restrict the user not to key in more than 50 chars | injeti | UNIX for Advanced & Expert Users | 1 | 08-14-2008 07:08 AM |
| Restrict FTP access to a single directory for only one user. | santhoshkumar_d | UNIX for Advanced & Expert Users | 8 | 05-23-2008 05:08 AM |
| restrict a user to certain command | vikas027 | SUN Solaris | 1 | 03-07-2008 06:52 AM |
| need to restrict user to his home dir | lidram | SUN Solaris | 5 | 02-06-2008 08:03 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#8
|
|||
|
|||
|
red:
actually - this is also a good point... and I have made this change... however, I still really want the user "rooted" to their home directory - I just believe that is a much cleaner, safer, more professional appearance. I'm also thinking about user maintenance. If I know that all users will be added by default - "rooted to their home directory", then the maintenance of users is a task I can delagate. Quote:
|
| Forum Sponsor | ||
|
|
|
#9
|
|||
|
|||
|
I guess I should clarify some things...
when I said chroot wasn't an acceptable solution - I only meant by itself. I do, in fact, use chroot; which limits the user ONLY to sftp. In fact, my chroot jail, is about as lean as you can possibly have one. - the whole jail (excluding the home directory) contains only 20 files in total (~ 4M in size) - in only 3 directory's: /dev; /lib; and /usr (and /dev only contains null) I guess in the ideal - if I could have a user chroot'd to their home directory (without the need for them to see those 3 directories), and if sftp existed in some "rsftp" version, where I could eliminate the 'cd' command (or restrict) it, and if I could have all of this in a form that's easy enough to delagate user maintenance, I would be perfectly happy. It doesn't seem to me that, that's asking for alot... I suppose the easy/delagate part may simply be me writing a bash script - I'm ok w/ that. But the rest seems to be very difficult to attain - which surprises me. |
|
#10
|
|||
|
|||
|
Isn't sftp basically just a wrapper for ssh? Then perhaps you could assign the users a custom shell which lacks or restricts the commands you find problematic.
|
|
#11
|
|||
|
|||
|
an interesting question...
I'm not sure that sftp is a wrapper, but I'm guessing it is not... I make this statement based on the fact that my own chroot jail does not include ssh in it. The only "executable" in my jail is "sftp-server" (which is located under /usr/lib) So I've always seen sftp as a separate app; I'm not sure if it does work thru ssh (even in a chroot jail)? Anyone know if the command set can be limited somehow - either thru sftp itself or ssh (if that's the "mother app") ? |
|||
| Google The UNIX and Linux Forums |