What is the most likely reason a user cannot capture logons using L0phtcrack on a Windows 2000 network?

Study for the EC-Council Certified Ethical Hacker (CEH) v13 Exam. Utilize flashcards and multiple-choice questions with helpful hints and detailed explanations. Excel in your exam preparation!

Multiple Choice

What is the most likely reason a user cannot capture logons using L0phtcrack on a Windows 2000 network?

Explanation:
When password hashes are needed for cracking, tools like L0phtcrack rely on obtaining those hashes from the system (NTLM/LM hashes from SAM or captured traffic). In a Windows 2000 domain that uses Kerberos for authentication, logon requests don’t send password hashes over the network. Instead, the user’s credentials are validated via Kerberos tickets, which are encrypted and do not expose the password hash. Because there’s nothing to capture in the logon process that L0phtcrack can crack, the tool can’t work for logon capture in this environment. WEP or AES encryption and compatibility notes aren’t the limiting factor here; Kerberos is the reason.

When password hashes are needed for cracking, tools like L0phtcrack rely on obtaining those hashes from the system (NTLM/LM hashes from SAM or captured traffic). In a Windows 2000 domain that uses Kerberos for authentication, logon requests don’t send password hashes over the network. Instead, the user’s credentials are validated via Kerberos tickets, which are encrypted and do not expose the password hash. Because there’s nothing to capture in the logon process that L0phtcrack can crack, the tool can’t work for logon capture in this environment. WEP or AES encryption and compatibility notes aren’t the limiting factor here; Kerberos is the reason.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy