On Mon, Dec 27, 2004 at 12:13:55AM +0100, Martin Dalecki wrote:
No the first value that worked in the whole setup of course. And I
said it clearly that would be just a workaround because uniqueness
can be established in the easiest way on the side of the part which
is interested in the persistency - the server peer not the client.
actually, the bk lease server could give out id's and those could be
caches in ~/.bk<whatever> --- server side it could be a counter that
you just xor with some s3kr1t value and then blind using a hash or
cryto-function, something good-enough (statistically unlikely to
break) is all that is required, it doesn't have to be perfect surely?