Quoting Chad A. Adlawan ([EMAIL PROTECTED]):
> hello all,
>when i invoke 'lastb', i get the following output :
>
> UNKNOWN ttyp1ruf2-6.evoserve. Tue Jul 27 21:13 - 21:13 (00:00)
> chadittyp1ruf2-6.evoserve. Tue Jul 27 21:12 - 21:12 (00:00)
>
>that is, UNKNOWN for so
>> Any user can run lastb.
>
>you can fix that with chmod o= /var/log/btmp*
When the file is rotated, the old permissions will be restored, so you
would have to fix the cron entry as well.
I agree that it is possible to prevent others from running lastb, but
it is easy to do it incorrectly, and
On Tue, 27 Jul 1999, Carl Mummert wrote:
> Note that this is a Bad Idea (to get the usernames or passwords)
> since it tends to 1) give you a list of the users' passwords and
> 2) give others a well-known place to look for them too.
> Any user can run lastb.
you can fix that with chmod o= /var/lo
>UNKNOWN ttyp1ruf2-6.evoserve. Tue Jul 27 21:13 - 21:13 (00:00)
>chadittyp1ruf2-6.evoserve. Tue Jul 27 21:12 - 21:12 (00:00)
>
> question, is there any way for as to know as to what exactly is the 'guess'
> user name someone tried to enter w/c resulted in the UNKNOWN record
hello all,
when i invoke 'lastb', i get the following output :
UNKNOWN ttyp1ruf2-6.evoserve. Tue Jul 27 21:13 - 21:13 (00:00)
chadittyp1ruf2-6.evoserve. Tue Jul 27 21:12 - 21:12 (00:00)
that is, UNKNOWN for someone who tried to enter a non-exixtent username (w/
refer
5 matches
Mail list logo
