The only security worth implementing is what the majority of people wouldn't know how to get past. By increasing the obstacles you decrease the amount of people that could break into the system. Taking all things into consideration, your box doesn't need to be THAT secure as a home pc or small business pc. I believe in minimal security or as joker20 said, i dont believe in TOTAL security.

and besides, both of you are fools, the dictionary CLEARLY states that hacking is one that hacks. And to hack is to unskillfully chop away at something, which happens to take precedence due to its order.

Im going to go hack some firewood now. :P

PostScript: OH BTW arguing like dat int kewl :P

what's kewl fewl?

..... lol........ heh.....uurrrr

i'll get my coat.

what you don't realise is .hack is 6 and in a couple of years he will "ssh infidels && rm -f /" all our computers for our insolence!!!!

To try to bring this somewhat back on track, and make sure I'm not missing something:

to dirtyol: password hashes are no longer stored in the /etc/passwd file. You can now find them in the /etc/shadow file. The 'x' in passwd is simply meant to tell the system to look in shadow for the hash.

I know that the chroot and passwd commands are the easiest way to reset the password (from bootable disk), but wouldn't setting the password segment of the shadow file to anything but the hash or blank totally prevent login? If it was blank, would it be treated as an anonymous login?

to scuzzman: I think that only works the way you wrote it if your kernel is named "linux" or you have a sym link named "linux" pointing at it.


Now, If I have any gaps or inaccuracies, please fill me in. I come here to help and learn!