Editing Kerberos (protocol)

{{Short description|Computer authentication protocol}}
{{Infobox software
| name = Kerberos
| title = Kerberos
| logo = Kerberos protocol logo.png
| screenshot = <!-- [[File: ]] -->
| caption = 
| collapsible = 
| author = 
| developer = [[Massachusetts Institute of Technology]]
| released = {{Start date|1989|01|24|df=yes}} (version 4)
| discontinued = 
| latest release version = Version 5, Release 1.21.3
| latest release date = {{Start date and age|2024|06|26|df=yes}}<ref>{{cite web | url=https://web.mit.edu/kerberos/krb5-1.21/ | title=Kerberos 5 Release 1.21.3 }}</ref>
| latest preview version = 
| latest preview date = <!-- {{Start date and age|YYYY|MM|DD|df=yes}} -->
| programming language = [[C (programming language)|C]]
| operating system = [[Cross-platform]]
| platform = 
| size = 
| language = 
| genre = [[Authentication protocol]]
| license = 
| website = {{URL|https://web.mit.edu/kerberos/}}
}}
'''Kerberos''' ({{IPAc-en|ˈ|k|ɜːr|b|ər|ɒ|s}}) is a [[computer network|computer-network]] [[authentication]] [[cryptographic protocol|protocol]] that works on the basis of ''tickets'' to allow [[Node (networking)|nodes]] communicating over a non-secure network to prove their identity to one another in a secure manner. Its designers aimed it primarily at a [[client–server]] model, and it provides [[mutual authentication]]—both the user and the server verify each other's identity. Kerberos protocol messages are protected against [[Computer insecurity#Eavesdropping|eavesdropping]] and [[replay attack]]s.

Kerberos builds on [[symmetric-key cryptography]] and requires a [[trusted third party]], and optionally may use [[public-key cryptography]] during certain phases of authentication.<ref name="rfc4556">RFC 4556, abstract.</ref> Kerberos uses [[UDP port]] 88 by default.

The protocol was named after the character ''[[cerberus|Kerberos]]'' (or ''[[Cerberus]]'') from [[Greek mythology]], the ferocious three-headed guard dog of [[Hades]].<ref>{{Cite web |title=Kerberos authentication |url=https://www.ionos.com/digitalguide/server/security/kerberos/ |access-date=2022-08-25 |website=IONOS Digitalguide |language=en}}</ref>

==History and development==
The [[Massachusetts Institute of Technology]] (MIT) developed Kerberos in 1988 to protect network services provided by [[Project Athena]].{{Sfn|Garman|2003|p=5}}<ref name="Athena Network Services">{{cite conference |title=Network Services in the Athena Environment |first1=Jennifer G. |last1=Steiner |first2=Daniel E. |last2=Geer |date=21 July 1988 |conference=Proceedings of the Winter 1988 Usenix Conference |citeseerx=10.1.1.31.8727 }}</ref> Its first version was primarily designed by Steve Miller and Clifford Neuman based on the earlier [[Needham–Schroeder protocol|Needham–Schroeder symmetric-key protocol]].<ref>{{cite conference |last1=Steiner |first1=Jennifer G. |last2=Neuman |first2=Clifford |last3=Schiller |first3=Jeffrey I. |title=''Kerberos'': An authentication service for open network systems |conference=Proceedings of the Winter 1988 USENIX Conference |date=February 1988 |citeseerx=10.1.1.112.9002 |s2cid=222257682 }}</ref><ref name="Building Internet Firewalls">{{cite book |title=Building Internet Firewalls: Internet and Web Security |url=https://archive.org/details/buildinginternet00zwic |url-access=registration |author=Elizabeth D. Zwicky |author2=Simon Cooper |author3=D. Brent |date=26 Jun 2000 |publisher=O'Reilly |isbn=9781565928718}}</ref> Kerberos versions 1 through 3 were experimental and not released outside of MIT.{{Sfn|Garman|2003|p=7}}

Kerberos version 4, the first public version, was released on January 24, 1989. Since Kerberos 4 was developed in the United States, and since it used the [[Data Encryption Standard]] (DES) [[encryption algorithm|encryption]] algorithm, [[Export of cryptography from the United States|U.S. export control restrictions]] prevented it from being exported to other countries. MIT created an exportable version of Kerberos 4 with all encryption code removed,{{Sfn|Garman|2003|p=7}} called "Bones".{{Sfn|Pröhl|Kobras|2022|p=7}} Eric Young of Australia's [[Bond University]] reimplemented DES into Bones, in a version called "eBones", which could be freely used in any country. Sweden's [[Royal Institute of Technology]] released another reimplementation called KTH-KRB.{{Sfn|Garman|2003|pp=7-8}}

Neuman and John Kohl published version 5 in 1993 with the intention of overcoming existing limitations and security problems.  Version&nbsp;5 appeared as [http://www.rfc-editor.org/info/rfc1510 RFC&nbsp;1510], which was then made obsolete by [http://www.rfc-editor.org/info/rfc4120  RFC&nbsp;4120] in 2005.

In 2005, the [[Internet Engineering Task Force]] (IETF) Kerberos working group updated specifications. Updates included:
* Encryption and Checksum Specifications ([http://www.rfc-editor.org/info/rfc3961  RFC&nbsp;3961]).
* [[Advanced Encryption Standard]] (AES) Encryption for Kerberos 5 ([http://www.rfc-editor.org/info/rfc3962  RFC&nbsp;3962]).
* A new edition of the Kerberos V5 specification "The Kerberos Network Authentication Service (V5)" ([http://www.rfc-editor.org/info/rfc4120  RFC&nbsp;4120]). This version obsoletes RFC&nbsp;1510, clarifies aspects of the protocol and intended use in a more detailed and clearer explanation.
* A new edition of the [[Generic Security Services Application Program Interface]] (GSS-API) specification "The Kerberos Version&nbsp;5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version&nbsp;2" ([http://www.rfc-editor.org/info/rfc4121  RFC&nbsp;4121]).

MIT makes an implementation of Kerberos freely available, under copyright permissions similar to those used for [[BSD licenses|BSD]]. In 2007, MIT formed the Kerberos Consortium to foster continued development. Founding sponsors include vendors such as [[Oracle Corporation|Oracle]], [[Apple Inc.]], [[Google]], [[Microsoft]], Centrify Corporation and TeamF1 Inc., and academic institutions such as the [[Royal Institute of Technology]] in Sweden, Stanford University, MIT, and vendors such as CyberSafe offering commercially supported versions.

==Protocol==

===Description===
The client authenticates itself to the '''Authentication Server (AS)''' which is part of the '''[[key distribution center]]''' '''(KDC)'''. The KDC issues a '''ticket-granting ticket (TGT)''', which is time stamped and encrypts it using the '''ticket-granting service's (TGS)''' secret key and returns the encrypted result to the user's workstation.  This is done infrequently, typically at user logon; the TGT expires at some point although it may be transparently renewed by the user's session manager while they are logged in.

When the client needs to communicate with a service on another node (a "principal", in Kerberos parlance), the client sends the TGT to the TGS, which is another component of the KDC and usually shares the same host as the authentication server. The service must have already been registered with the TGS with a '''Service Principal Name (SPN)'''. The client uses the SPN to request access to this service. After verifying that the TGT is valid and that the user is permitted to access the requested service, the TGS issues a '''service ticket (ST)''' and session keys to the client. The client then sends the ticket to the '''service server (SS)''' along with its service request.
[[File:Kerberos protocol.svg|thumb|upright=1.5|Kerberos negotiations]]
The protocol is described in detail below.<!-- The image file Kerberos.svg needs to be improved; the TGS server is missing from the graphic. -->

====User Client-based Login without Kerberos====
# A user enters a username and password on the [[client (computing)|client machine(s)]].  Other credential mechanisms like pkinit (RFC 4556) allow for the use of public keys in place of a password. The client transforms the password into the key of a symmetric cipher.  This either uses the built-in [[key scheduling]], or a [[one-way hash]], depending on the [[Cipher suite|cipher-suite]] used. 
#The server receives the username and symmetric cipher and compares it with the data from the database. Login was a success if the cipher matches the cipher that is stored for the user.

====Client Authentication====
# The client sends a [[plaintext]] message of the user ID to the AS (Authentication Server) requesting services on behalf of the user. (Note: Neither the secret key nor the password is sent to the AS.)
# The AS checks to see whether the client is in its database. If it is, the AS generates the secret key by hashing the password of the user found at the database (e.g., [[Active Directory]] in Windows Server) and sends back the following two messages to the client:
#* Message A: ''Client/TGS Session Key'' encrypted using the secret key of the client/user.
#* Message B: ''Ticket-Granting-Ticket'' (TGT, which includes the client ID, client [[network address]], ticket validity period, and the ''Client/TGS Session Key'') encrypted using the secret key of the TGS.
# Once the client receives messages A and B, it attempts to decrypt message A with the secret key generated from the password entered by the user.  If the user entered password does not match the password in the AS database, the client's secret key will be different and thus unable to decrypt message A.  With a valid password and secret key the client decrypts message A to obtain the ''Client/TGS Session Key''. This session key is used for further communications with the TGS. (Note: The client cannot decrypt Message B, as it is encrypted using TGS's secret key.)  At this point, the client has enough information to authenticate itself to the TGS.

====Client Service Authorization====
# When requesting services, the client sends the following messages to the TGS:
#* Message C: Composed of the message B (the encrypted TGT using the TGS secret key) and the ID of the requested service.
#* Message D: Authenticator (which is composed of the client ID and the timestamp), encrypted using the ''Client/TGS Session Key'' (found by the client in Message A).
# Upon receiving messages C and D, the TGS retrieves message B out of message C. It decrypts message B using the TGS secret key. This gives it the ''Client/TGS Session Key'' and the client ID (both are in the TGT). Using this ''Client/TGS Session Key'', the TGS decrypts message D (Authenticator) and compares the client IDs from messages B and D; if they match, the server sends the following two messages to the client:
#* Message E: ''Client-to-server ticket'' (which includes the client ID, client network address, validity period, and ''Client/Server Session Key'') encrypted using the service's secret key.
#* Message F: ''Client/Server Session Key'' encrypted with the ''Client/TGS Session Key''.

====Client Service Request====
# Upon receiving messages E and F from TGS, the client has enough information to authenticate itself to the Service Server (SS).  The client connects to the SS and sends the following two messages:
#* Message E: From the previous step (the ''Client-to-server ticket'', encrypted using service's Secret key by the TGS).
#* Message G: A new Authenticator, which includes the client ID, timestamp and is encrypted using ''Client/Server Session Key''.
# The SS decrypts the ticket (message E) using its own secret key to retrieve the ''Client/Server Session Key''. Using the sessions key, SS decrypts the Authenticator and compares client ID from messages E and G, if they match server sends the following message to the client to confirm its true identity and willingness to serve the client:
#* Message H: The timestamp found in client's Authenticator (plus 1 in version 4, but not necessary in version 5<ref>{{cite web |url=https://tools.ietf.org/html/rfc1510#section-3.2.4 |title=The Kerberos Network Authentication Service (V5) |last1=Neuman |first1=C. |last2=Kohl |first2=J. |year=1993 |doi=10.17487/RFC1510 |url-status=live |archive-url=https://web.archive.org/web/20160821221402/https://tools.ietf.org/html/rfc1510#section-3.2.4 |archive-date=2016-08-21 |doi-access=free }}</ref><ref>{{cite web |url=https://tools.ietf.org/html/rfc4120#section-3.2.4 |title=The Kerberos Network Authentication Service (V5) |last1=Neuman |first1=Clifford |last2=Hartman |first2=Sam |last3=Yu |first3=Tom |last4=Raeburn |first4=Kenneth |year=2005 |doi=10.17487/RFC4120 |url-status=live |archive-url=https://web.archive.org/web/20160821232023/https://tools.ietf.org/html/rfc4120#section-3.2.4 |archive-date=2016-08-21 }}</ref>), encrypted using the ''Client/Server Session Key''.
# The client decrypts the confirmation (message H) using the ''Client/Server Session Key'' and checks whether the timestamp is correct. If so, then the client can trust the server and can start issuing service requests to the server.
# The server provides the requested services to the client.

==Support by operating systems==

===Microsoft Windows===
[[Windows 2000]] and later versions use Kerberos as their default authentication method.<ref name="MSTN-Kerberos-Auth">{{cite web|url=https://technet.microsoft.com/pt-br/library/cc780469(v=ws.10).aspx|title=What Is Kerberos Authentication?|date=8 October 2009 |publisher=Microsoft TechNet|url-status=live|archive-url=https://web.archive.org/web/20161220084434/https://technet.microsoft.com/pt-br/library/cc780469(v=ws.10).aspx|archive-date=2016-12-20}}</ref> Some [[Microsoft]] additions to the Kerberos suite of protocols are documented in RFC 3244 "Microsoft Windows 2000 Kerberos Change Password and Set Password Protocols". RFC 4757 documents Microsoft's use of the [[RC4]] cipher.  While Microsoft uses and extends the Kerberos protocol, it does not use the MIT software.

Kerberos is used as the preferred authentication method: in general, joining a client to a Windows domain means enabling Kerberos as the default protocol for authentications from that client to services in the Windows domain and all domains with trust relationships to that domain.<ref name="MSTN-Kerberos-Auth"/>

In contrast, when either client or server or both are not joined to a domain (or not part of the same trusted domain environment), Windows will instead use [[NTLM]] for authentication between client and server.<ref name="MSTN-Kerberos-Auth"/>

Internet web applications can enforce Kerberos as an authentication method for domain-joined clients by using APIs provided under [[SSPI]].

Microsoft Windows and Windows Server include {{Mono|setspn}}, a [[command-line interface|command-line]] utility that can be used to read, modify, or delete the Service Principal Names (SPN) for an Active Directory [[service account]].<ref>[https://ss64.com/nt/setspn.html Setspn - Windows CMD - SS64.com]</ref><ref>[https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc731241(v=ws.11) Setspn | Microsoft Docs]</ref>

===Unix and other operating systems===
Many Unix-like operating systems, including [[FreeBSD]], Apple's [[macOS]], [[Red Hat Enterprise Linux]], [[Sun microsystems|Oracle]]'s [[Solaris (operating system)|Solaris]], IBM's [[AIX]], [[HP-UX]] and others, include software for Kerberos authentication of users or services. A variety of non-Unix like operating systems such as [[z/OS]], [[IBM i]] and [[OpenVMS]] also feature Kerberos support. Embedded implementation of the Kerberos V authentication protocol for client agents and network services running on embedded platforms is also available from companies {{which|date=November 2023}}.

==Drawbacks and limitations==
* Kerberos has strict time requirements, which means that the clocks of the involved hosts must be synchronized within configured limits. The tickets have a time availability period, and if the host clock is not synchronized with the Kerberos server clock, the authentication will fail. The default configuration [http://web.mit.edu/Kerberos/krb5-1.5/krb5-1.5.4/doc/krb5-admin/Clock-Skew.html per MIT] requires that clock times be no more than five minutes apart. In practice, [[Network Time Protocol]] daemons are usually used to keep the host clocks synchronized. Note that some servers (Microsoft's implementation being one of them) may return a KRB_AP_ERR_SKEW result containing the encrypted server time if both clocks have an offset greater than the configured maximum value. In that case, the client could retry by calculating the time using the provided server time to find the offset. This behavior is documented in [http://www.rfc-editor.org/info/rfc4430  RFC&nbsp;4430].
* The administration protocol is not standardized and differs between server implementations. Password changes are described in [https://www.rfc-editor.org/rfc/rfc3244.html RFC&nbsp;3244].
* In case of symmetric cryptography adoption (Kerberos can work using symmetric or asymmetric (public-key) cryptography), since all authentications are controlled by a centralized [[key distribution center]] (KDC), compromise of this authentication infrastructure will allow an attacker to impersonate any user.
* Each network service that requires a different host name will need its own set of Kerberos keys. This complicates virtual hosting and clusters.
* Kerberos requires user accounts and services to have a trusted relationship to the Kerberos token server.
* The required client trust makes creating staged environments (e.g., separate domains for test environment, pre-production environment and production environment) difficult: Either domain trust relationships need to be created that prevent a strict separation of environment domains, or additional user clients need to be provided for each environment.

==Security==
The [[Data Encryption Standard]] (DES) cipher can be used in combination with Kerberos, but is no longer an Internet standard because it is weak.<ref>{{cite web |url=https://tools.ietf.org/html/rfc6649 |title=Deprecate DES, RC4-HMAC-EXP, and Other Weak Cryptographic Algorithms in Kerberos |first1=Yu |last1=Tom |first2=Astrand |last2=Love |year=2012 |doi=10.17487/RFC6649 |url-status=live |archive-url=https://web.archive.org/web/20151027034313/http://tools.ietf.org/html/rfc6649 |archive-date=2015-10-27 }}</ref> Security vulnerabilities exist in products that implement legacy versions of Kerberos which lack support for newer encryption ciphers like AES.

==See also==
{{Portal|Free and open-source software}}

* [[Single sign-on]]
* [[Identity management]]
* [[SPNEGO]]
* [[S/Key]]
* [[Secure remote password protocol]] (SRP)
* [[Generic Security Services Application Program Interface]] (GSS-API)
* [[Host Identity Protocol]] (HIP)
* [[List of single sign-on implementations]]

==References==
{{Reflist}}

;General
{{Refbegin}}
*{{cite book |last1=Garman |first1=Jason |title=Kerberos: The Definitive Guide |date=2003 |publisher=[[O'Reilly Media, Inc.]] |isbn=978-0-596-00403-3 |url=https://books.google.com/books?id=ltWbAgAAQBAJ |language=en }}
* {{cite book |last1=Pröhl |first1=Mark |last2=Kobras |first2=Daniel |title=Kerberos: Single Sign-on in gemischten Linux/Windows-Umgebungen |url=https://books.google.com/books?id=k-VqEAAAQBAJ |publisher=dpunkt.verlag |page=7 |language=de |date=14 April 2022 |isbn=9783960888512 }}
*{{cite web|author=Lynn Root (May 30, 2013)|url=http://www.roguelynn.com/words/explain-like-im-5-kerberos|title=Explain like I'm 5: Kerberos|work=Blog of Lynn Root|date=2 April 2013}}
*{{cite web |author=Microsoft TechNet |url=https://technet.microsoft.com/en-us/library/cc961976.aspx |title=Basic Concepts for the Kerberos Protocol |work=MSDN Library |date=18 July 2012 }}
*{{cite web |author=Resource Kit Team |url=http://msdn.microsoft.com/en-us/library/aa378747(VS.85).aspx |title=Microsoft Kerberos (Windows) |work=MSDN Library |date=7 January 2021 }}
*{{Cite journal |author1=B. Clifford Neuman |author2=Theodore Ts'o |title=Kerberos: An Authentication Service for Computer Networks |journal=IEEE Communications |volume=32 |issue=9 |pages=33–8 |date=September 1994 |url=http://gost.isi.edu/publications/kerberos-neuman-tso.html |doi=10.1109/35.312841 |s2cid=45031265 }}
*{{cite book |last1=Kohl |first1=John T. |last2=Neuman |first2=B. Clifford |last3=Ts'o |first3=Theodore Y. |chapter=The Evolution of the Kerberos Authentication System |pages=78–94 |citeseerx=10.1.1.120.944 |editor1-last=Brazier |editor1-first=F. M. T.|editor1-link=Frances Brazier |editor2-last=Johansen |editor2-first=D |title=Distributed open systems |date=1994 |publisher=IEEE Computer Society Press |isbn=978-0-8186-4292-0 |oclc=1191406172 }}
*{{cite web |url=http://www.cisco.com/en/US/tech/tk59/technologies_white_paper09186a00800941b2.shtml |title=Kerberos Overview: An Authentication Service for Open Network Systems |publisher=Cisco Systems |date=19 January 2006 |access-date=15 August 2012 }}
*{{cite web |url=http://learn-networking.com/network-security/how-kerberos-authentication-works |title=How Kerberos Authentication Works |publisher=learn-networking.com |date=28 January 2008 |access-date=15 August 2012 |archive-date=2 April 2015 |archive-url=https://web.archive.org/web/20150402074954/http://learn-networking.com/network-security/how-kerberos-authentication-works |url-status=dead }}
*{{cite web |url=https://technet.microsoft.com/pt-br/library/cc780469(v=ws.10).aspx |title=What is Kerberos Authentication?: Logon and Authentication. |date=8 October 2009 |publisher=Microsoft TechNet |access-date=7 December 2016 }}
{{Refend}}

;RFCs
*{{IETF RFC|1510|link=no}} The Kerberos Network Authentication Service (V5) [Obsolete]
*{{IETF RFC|1964|link=no}} The Kerberos Version 5 GSS-API Mechanism
*{{IETF RFC|3961|link=no}} Encryption and Checksum Specifications for Kerberos 5
*{{IETF RFC|3962|link=no}} Advanced Encryption Standard (AES) Encryption for Kerberos 5
*{{IETF RFC|4120|link=no}} The Kerberos Network Authentication Service (V5) [Current]
*{{IETF RFC|4121|link=no}} The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2
*{{IETF RFC|4537|link=no}} Kerberos Cryptosystem Negotiation Extension
*{{IETF RFC|4556|link=no}} Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)
*{{IETF RFC|4557|link=no}} Online Certificate Status Protocol (OCSP) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)
*{{IETF RFC|4757|link=no}} The RC4-HMAC Kerberos Encryption Types Used by Microsoft Windows [Obsolete]
*{{IETF RFC|5021|link=no}} Extended Kerberos Version 5 Key Distribution Center (KDC) Exchanges over TCP
*{{IETF RFC|5349|link=no}} Elliptic Curve Cryptography (ECC) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)
*{{IETF RFC|5868|link=no}} Problem Statement on the Cross-Realm Operation of Kerberos
*{{IETF RFC|5896|link=no}} Generic Security Service Application Program Interface (GSS-API): Delegate if Approved by Policy
*{{IETF RFC|6111|link=no}} Additional Kerberos Naming Constraints
*{{IETF RFC|6112|link=no}} Anonymity Support for Kerberos
*{{IETF RFC|6113|link=no}} A Generalized Framework for Kerberos Pre-Authentication
*{{IETF RFC|6251|link=no}} Using Kerberos Version 5 over the Transport Layer Security (TLS) Protocol
*{{IETF RFC|6448|link=no}} The Unencrypted Form of Kerberos 5 KRB-CRED Message
*{{IETF RFC|6542|link=no}} Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Channel Binding Hash Agility
*{{IETF RFC|6560|link=no}} One-Time Password (OTP) Pre-Authentication
*{{IETF RFC|6649|link=no}} Deprecate DES, RC4-HMAC-EXP, and Other Weak Cryptographic Algorithms in Kerberos
*{{IETF RFC|6784|link=no}} Kerberos Options for DHCPv6
*{{IETF RFC|6803|link=no}} Camellia Encryption for Kerberos 5
*{{IETF RFC|6806|link=no}} Kerberos Principal Name Canonicalization and Cross-Realm Referrals
*{{IETF RFC|6880|link=no}} An Information Model for Kerberos Version 5
*{{IETF RFC|8009|link=no}} AES Encryption with HMAC-SHA2 for Kerberos 5

==Further reading==
{{Refbegin}}
*{{cite web
 |url=http://www.usdoj.gov/atr/cases/ms_tuncom/major/mtc-00029523.htm
 |title= Novell Inc's Comment to the Proposed Settlement between Microsoft and the Department of Justice, pursuant to the Tunney Act
 |work=Civil Action No. 98-1232 (CKK): United States of America v. Microsoft Corporation
 |publisher=Department of Justice
 |date=29 January 2002 |access-date=15 August 2012
}}
*{{cite web
 |url=http://web.mit.edu/kerberos/www/dialogue.html
 |title=Designing an Authentication System: A Dialogue in Four Scenes
 |work=Humorous play concerning how the design of Kerberos evolved
 |publisher=[[MIT]]
 |date=February 1988
 |first=Bill |last=Bryant
}}
*{{cite web
 |title       = Kerberos FAQ, v2.0
 |archive-url  = https://web.archive.org/web/20021203013358/http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html
 |url         = http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html
 |publisher   = [[Secretary of Navy]]
 |date        = 18 August 2000
 |archive-date = 3 December 2002
 |access-date  = 15 August 2012
 |first       = Ken
 |last        = Hornstein
 |url-status     = dead
}}
*{{cite journal |last1=Bellovin |first1=S. M. |last2=Merritt |first2=M. |title=Limitations of the Kerberos authentication system |journal=ACM SIGCOMM Computer Communication Review |date=1 October 1990 |volume=20 |issue=5 |pages=119–132 |doi=10.1145/381906.381946 |s2cid=8014806 |doi-access=free }}
*{{cite journal |last1=Neuman |first1=B.C. |last2=Ts'o |first2=T. |title=Kerberos: an authentication service for computer networks |journal=IEEE Communications Magazine |date=September 1994 |volume=32 |issue=9 |pages=33–38 |doi=10.1109/35.312841 |s2cid=45031265 }}
*{{cite book |doi=10.1007/BFb0055875 |chapter=Kerberos Version IV: Inductive analysis of the secrecy goals |title=Computer Security — ESORICS 98 |series=Lecture Notes in Computer Science |year=1998 |last1=Bella |first1=Giampaolo |last2=Paulson |first2=Lawrence C. |volume=1485 |pages=361–375 |isbn=978-3-540-65004-1 }}
*{{cite book |doi=10.1109/CIT.2010.285 |chapter=Improved Kerberos Security Protocol Evaluation using Modified BAN Logic |title=2010 10th IEEE International Conference on Computer and Information Technology |year=2010 |last1=Abdelmajid |first1=N.T. |last2=Hossain |first2=M.A. |last3=Shepherd |first3=S. |last4=Mahmoud |first4=K. |pages=1610–1615 |isbn=978-1-4244-7547-6 |s2cid=6246388 }}
{{Refend}}

==External links==
{{Commons category|Kerberos}}
{{Prone to spam|date=May 2019}}
<!--     {{No more links}}

       Please be cautious adding more external links.

Wikipedia is not a collection of links and should not be used for advertising.

     Excessive or inappropriate links will be removed.

 See [[Wikipedia:External links]] and [[Wikipedia:Spam]] for details.

If there are already suitable links, propose additions or replacements on
the article's talk page.

-->
* [http://www.kerberos.org/ Kerberos Consortium]
* [http://web.mit.edu/kerberos/ Kerberos page] at [[MIT]] website
* [https://web.archive.org/web/20040707075602/http://www.ietf.org/html.charters/krb-wg-charter.html Kerberos Working Group] at [[IETF]] website
* [http://www.eventhelix.com/RealtimeMantra/Networking/kerberos/kerberos-sequence-diagram.pdf Kerberos Sequence Diagram] {{Webarchive|url=https://web.archive.org/web/20150326142031/http://eventhelix.com/RealtimeMantra/Networking/kerberos/kerberos-sequence-diagram.pdf |date=2015-03-26 }}
* [https://github.com/heimdal/heimdal/wiki Heimdal/Kerberos implementation]

{{Authentication APIs}}
{{Authority control}}

{{DEFAULTSORT:Kerberos (Protocol)}}
[[Category:Computer-related introductions in 1988]]
[[Category:Authentication protocols]]
[[Category:Computer access control protocols]]
[[Category:Computer network security]]
[[Category:Key transport protocols]]
[[Category:Symmetric-key algorithms]]
[[Category:Massachusetts Institute of Technology software]]
[[Category:Cerberus]]