Switching to ccache v4?

[Nicolas.Williams@ubsw.com]

A daemon approach would facilitate interesting features, such as:

 - the daemon can know how to prompt the user in order to fetch
   new creds when the ones it has expire
 - the daemon could "proxy" the ccache over to the user's
   initial point of login so that the daemon itself has no TGT
   and TGT forwarding is not necessary instead being replaced
   with ticket proxying

The daemon can be changed at any time to implement interesting
features like these; the shared memory approach would require
changes to libkrb5 to implement such features.

Shared memory would do, yes. But then, why bother with CCAPI?
What's the difference between using shmget(), or open()/mmap()
to get to a ccache and plain open()?

Nico
--  

> -----Original Message-----
> From: Sam Hartman [mailto:hartmans at mit.edu]
> Sent: Friday, May 17, 2002 4:22 PM
> To: Williams, Nicolas
> Cc: kenh at cmf.nrl.navy.mil; kerberos at mit.edu
> Subject: Re: Switching to ccache v4?
> 
> 
> >>>>> "Nicolas" == Nicolas Williams 
> <Nicolas.Williams at ubsw.com> writes:
> 
>     Nicolas> Ick. CCAPI sounds so cool. I want it for Unix. Can't be
>     Nicolas> hard. I figure that Unix domain sockets / STREAMS pips w/
>     Nicolas> cred (uid) passing should do for IPC - the daemon would
>     Nicolas> be simple and would use MEMORY ccaches.
> 
> Wouldn't a shared memory (shmget and friends) ccache with no daemon be
> even better?
> 
> 

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.