Results 1 to 2 of 2
thanks for reply my post but now i have some questions
i read on G. Mourani books to disable account is add (* - asterisk mark) on front of the ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 01-20-2005 #1Just Joined!
- Join Date
- Feb 2004
- Location
- Indonesia
- Posts
- 84
/bin/false again !
thanks for reply my post but now i have some questions
i read on G. Mourani books to disable account is add (* - asterisk mark) on front of the encrypted password is that right and whats the diffrent using with ( ! ) (at /etc/shadow file)
but when i disable those users, FTP account is also disable .... mmmh am i have to configure again on VSFTP server
and last how to make users can't change directory at above of his directory
thanks before
- 01-20-2005 #2
Re: /bin/false again !
There really is no difference except that /etc/shadow is *not* world readable. If you edit /etc/shadow to disable an account, other users can't tell if that account is disabled or not by reading /etc/passwd. The cleanest way to lock an account, however, is to use 'passwd -l username'. You can then unlock it with 'passwd -u username'.
Originally Posted by kamtono
If you disable the account on the system, then it cannot log into anything that uses system logins (i.e.-most FTP daemons).but when i disable those users, FTP account is also disable .... mmmh am i have to configure again on VSFTP server
In VSFTP? This is called 'chrooting'. It's built into VSFTP. Check the docs on their site for a guide to setting it up.and last how to make users can't change directory at above of his directory
thanks before[/quote]"Time is an illusion. Lunchtime, doubly so."
~Douglas Adams, The Hitchhiker's Guide to the Galaxy


Reply With Quote
