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 CISSP-Discussion
[Top] [All Lists]

RE: [CISSP-D] Question about kerberos

Subject: RE: [CISSP-D] Question about kerberos
Date: Wed, 6 Apr 2005 12:36:08 +0100 (BST)

My understanding is User/Service Registration mandatory in Kerbose 
environment.. Without that it is not possible to authenticate the user or 
service

Regards,

Nishi

-----Original Message-----

From: blcjr [mailto:blcjr@yahoo.com] 

Sent: Tuesday, April 05, 2005 8:48 PM

To: CISSP-Discuss@yahoogroups.com

Subject: [CISSP-D] Question about kerberos

A feature of kerberos that is often cited is that clients do not transmit 
passwords to the AS/KDC, but merely their user id. 

Supposedly, both the KDC and the client the user is on will have the users' 
private key. But how does the private key get associated with a user on any 
given client, especially in a network environment where users can log on 
remotely from numerous clients? To wit, if a user sits down and logs in 
remotely from a client they've never logged in from before, how do they get the 
private key to open the TGT?

 

Yahoo! Groups Links

http://groups.yahoo.com/group/CISSP-Discuss/

CISSP-Discuss-unsubscribe@yahoogroups.com

http://docs.yahoo.com/info/terms/



 

 


Yahoo! India Matrimony: Find your partner online.
<Prev in Thread] Current Thread [Next in Thread>