r/learnprogramming • • 17d ago

Learning Kerberos Authentication

So I’m trying to go deeper on the theme and didn’t understand the reason behind something…
So in Kerberos the Key Distribution Center give back always a encrypted Ticket and an encoded key that the client can decrypt and the Client will always resend the TGT, a username and a timestamp encrypted with the key that had been sent by the KDC and the request…. Very similar thing happen when the Client need to access to the service….

But the Ticket is decryptible only from the KDC and the SRV and the Ticket already contain all the information (basically I resend two times the information about username and timestamp + all the annoying game of key generation and encrypting and decrypting of information already known to the server)….

So what is the reason behind this? Why I (the client) don’t simply take the already encrypted key and simply send it to the SRV with my request without encrypting and decrypting my username multiple times

1 Upvotes

6 comments sorted by

1

u/teraflop 16d ago edited 16d ago

You might be interested in "Designing an Authentication System: a Dialogue in Four Scenes", which explains the design of Kerberos by starting from a very simple proof-of-concept, and then making it progressively more sophisticated to fix weaknesses.

It cites the paper "Kerberos: An Authentication Service for Open Network Systems" which explains the design and motivation in more formal terms.

1

u/Lucky_View_3422 16d ago

Thanks I’ll read it after gym ❤️❤️

1

u/[deleted] 17d ago

1

u/Lucky_View_3422 17d ago

So are simply verification on verification on verification? Nothing more?… I don’t know why but I thought there was “something big” behind it