[PYTHON-CRYPTO] Having trouble reading MIT CredCache programatically

[Mayers, Philip J]

As my follow up indicated (which of course you read), I do realise that a
client doesn't have the service key - I wasn't thinking when I typed the
mail and it was a stupid question.

I could give many flippant, impolite answers to your first question, but
instead I'll say: Why not? Are you so sure that the MIT or Heimdal
implementations are so perfect that there's nothing I can contribute by
making a third interoperable one? If so, I envy your confidence.

Regards,
Phil

+------------------------------------------+
| Phil Mayers                              |
| Network & Infrastructure Group           |
| Information & Communication Technologies |
| Imperial College                         |
+------------------------------------------+


-----Original Message-----
From: Sam Hartman [mailto:hartmans at MIT.EDU]
Sent: 23 November 2001 23:03
To: Mayers, Philip J
Cc: 'kerberos at MIT.EDU'; PYTHON-CRYPTO at NIC.SURFNET.NL
Subject: Re: Having trouble reading MIT CredCache programatically


>>>>> "Mayers," == Mayers, Philip J <p.mayers at ic.ac.uk> writes:

    Mayers,> All, I'm writing a Python kerberos library that's
    Mayers,> file-compatible with the MIT CredCache, and I'm having a
    Mayers,> weird time.

Why do you do this thing?  Aren't there enough implementations of
Kerberos out there?  Do you really want to keep up with all the crypto
system changes in Kerberos or upcoming ccache changes to support
ticket extensions?

Also, you are aware that the client generally never has the service
key necessary to decrypt the ticket, right?