Re: Cryptography problem

From: Dean Hallman (deanh_at_sc.rr.com)
Date: 06/23/04 

Date: Wed, 23 Jun 2004 16:24:44 GMT

 
> Maybe tickets solve your problem ?
>
> You ship each of your rich clients with a unique ticket.
> Each request validates the ticket, supplies an answer, and a new
> ticket, to be used for the clients next request.
> You could even use the ticket as an encryption key to part of the
> message.

Yes, I had considered something similar to this. But, connect the current
search with the next search in this way could lead to "out of sync"
problems. What if the client is uninstalled and reinstalled, for example.
The ticket for use on the next search could be lost.

Dean

Relevant Pages

  • Re: How to set Kerberos 5 ticket lifetime
    ... Does anybody have experience with AIX clients? ... The ticket lifetime a user can obtain as part of the login process on AIX ... and what are the necessary configuration in the server and the client ...
    (comp.protocols.kerberos)
  • local ticket-cache for ldap requests
    ... i have SuSE 10.0/9.3 Clients (krb5 rpm), which get their tickets right at ... After sign-on of the clients ... SuSE client. ... that the default ticket cache of Kerberos has to be overwritten ...
    (comp.protocols.kerberos)
  • VPN client lost DNS on LAN
    ... I have a windows 2K server that is an internet gateway server. ... Last week I changed the DNS server on the LAN where the Ticket ... and now the VPN clients cannot find the Ticketing application ...
    (microsoft.public.win2000.ras_routing)
  • Re: kerberos time skew
    ... The easies way is to make sure domain time synchronisation actually works. ... You need to inspect the clients' logs to see if there are entries from the ... > Service Ticket Request: ...
    (microsoft.public.security)
  • Re: Cryptography problem
    ... > You ship each of your rich clients with a unique ticket. ... > Each request validates the ticket, supplies an answer, and a new ...
    (alt.computer.security)