Printable View
It's called a "Hardware Interrupt". Meaning it makes it harder for someone to use something other than a password to get on. I can't think of a time where it would matter off hand but it is early. I'll check my book later or something unless someone else replies and gives an example instead. I think it was something with being able to use a program to get things at log in....I forgot, I've never really looked into it much but had to do some readin on it for my Security + So I'll check later on.
I just want to point out that you have to be careful cause there are tools that can still keylog the password even at windows startup. To my knowledge it works like a driver and that is how it does it.
http://www.keylogger.org/program.cgi?id=6
So be careful
Quote:
Originally posted here by coderecycle
I just want to point out that you have to be careful cause there are tools that can still keylog the password even at windows startup. To my knowledge it works like a driver and that is how it does it.
http://www.keylogger.org/program.cgi?id=6
So be careful
I think what they ment is that it only logs the TIME it starts up and shuts down.
I do believe the CTRL+ALT+DEL sequence was to prevent automated brute force attempts too? Or am I gravely mistaken?
dont think so, but i maybe wrong. MS get this sequence (already in use previously) and make it impossible (as far i know) to be hooked by any program. So you can hook on keyboard, but you cant get that sequence, even with a system driver. Im looking for an old documentation, but apparently its done on 1st level int handler and it cannot be overrided by any other program. Im trying to dig that paper....Quote:
Originally posted here by RejectKnowledge
I do believe the CTRL+ALT+DEL sequence was to prevent automated brute force attempts too? Or am I gravely mistaken?