Kerberos: Difference between revisions

From Chorke Wiki
Jump to navigation Jump to search
Line 27: Line 27:
* [https://github.com/NottingHack/hms/blob/master/vagrant_config/bootstrap.sh NottingHack/hms]
* [https://github.com/NottingHack/hms/blob/master/vagrant_config/bootstrap.sh NottingHack/hms]
* [http://thejavamonkey.blogspot.my/2008/04/clientserver-hello-world-in-kerberos.html Kerberos Hello World]
* [http://thejavamonkey.blogspot.my/2008/04/clientserver-hello-world-in-kerberos.html Kerberos Hello World]
* [https://web.mit.edu/kerberos/krb5-1.12/doc/admin/admin_commands/ Administration programs]
* [https://docs.oracle.com/cd/E19683-01/806-4078/6jd6cjrve/index.html How to Configure a Master KDC]
* [https://docs.oracle.com/cd/E19683-01/806-4078/6jd6cjrve/index.html How to Configure a Master KDC]
* [http://www.rjsystems.nl/en/2100-d6-kerberos-openldap-provider.php Integrated Kerberos-OpenLDAP provider]
* [http://www.rjsystems.nl/en/2100-d6-kerberos-openldap-provider.php Integrated Kerberos-OpenLDAP provider]

Revision as of 21:45, 27 May 2018

Overview

Kerberos is an authentication protocol developed by the Massachusetts Institute of Technology. Kerberos allows individuals communicating over an insecure network to prove their identity to one another in a secure manner. Kerberos authentication can be used to overcome weak points such as eavesdropping and replay attacks in other authentication mechanisms and to ensure the integrity of the data that is communicated.

The Kerberos authentication process involves several systems connected in a network, or a Kerberos realm. Kerberos authentication within a realm works on the basis of tickets, which serve to prove the authenticity of client requests. Kerberos authentication makes use of a trusted third party system called Key Distribution Center (KDC).

The KDC maintains a database of secret keys where each member system of a realm - whether a client or a server - shares a secret key known only to itself and to the Kerberos KDC. Knowledge of this key serves to prove the system's identity and this key never leaves the KDC. After the client is authenticated the KDC generates a session key for communication between the client and the application server, which they can use to secure their interactions.


Keywords Usages

Keyword Elaboration
KDC Key Distribution Center
TGT Ticket Granting Ticket
TGS Ticket Granting Server

References