directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <elecha...@gmail.com>
Subject [Kerberos] Ticket structure
Date Fri, 26 Oct 2007 20:02:03 GMT
Hi,

I'm currently reviewing the Ticket structure, and I'm wondering why we 
do store the  encrypted data _and_ the encrypted ticket part, 
considering that the first structure is a sealed version of the second 
one ? I understand that it is an optimization as we will manipulate a 
lot the data from the second structure, but why can't we simply extend 
the Ticket class to add a new field (this encTicketpart) in the 
inherited part?

Something like :

Ticket
{
    int versionNumber;
    KerberosPrincipal serverPrincipal;
    EncryptedData encPart;
}

and

TicketWithTicketPart extends Ticket
{
    EncTicketpart encTicketPart;
}

I don't know... wdyt ?

Mime
View raw message