Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security NTBugtraq
[Top] [All Lists]

Re: kerberos!

Subject: Re: kerberos!
Date: Sat, 11 Sep 2004 13:33:14 -0700
-----Original Message-----
From: Windows NTBugtraq Mailing List
[mailto:NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM] On Behalf Of David Schenz
Sent: Friday, September 10, 2004 9:37 AM
To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
Subject: Re: kerberos!

Two important points need to be remembered here: first, in order to
join
a domain in the first place, NTLMv2 is still necessary (as the joining
member is not a part of the Kerberos realm),
[Paul Leach] A small nit: this is not true; Kerberos is used to join
machines to the domain -- the _user_ has a domain account that can be
authenticated with Kerberos, even though the machine does not.

and second, windows
requires NTLMv2 to authenticate when opening a cif share via ip
address.
Authentication falls back to NTLMv2 if Kerberos can't meet the
following
conditions:


<snip>


So yes, you're certainly right in that it is less secure.
Unfortunately,
as currently designed, fallback to NTLMv2 is still necessary.
[Paul Leach] Actually, even if fallback to NTLM were never necessary,
there are a large number of protocols in Windows, primarily ones for
remote administration, that simply do not support Kerberos; they
explicitly specify NTLM. It is for this reason that NTLM is not disabled
by default. It is our intent to remove all such explicit specification
of NTLM by anything shipped with Windows in Longhorn.

-----
NTBugtraq Editor's Note:

Want to reply to the person who sent this message? This list is configured such 
that just hitting reply is going to result in the message coming to the list, 
not to the individual who sent the message. This was done to help reduce the 
number of Out of Office messages posters received. So if you want to send a 
reply just to the poster, you'll have to copy their email address out of the 
message and place it in your TO: field.
-----

<Prev in Thread] Current Thread [Next in Thread>