On Fri, Dec 08, 2023 at 09:02:45AM -0500, Tom Talpey wrote:
So, this next statement makes an incorrect assumption:
Hard links are in-fact pointing to the same file. So I would've
assumed that the server would have treated both links to have the same
lease.
Not at all - the lease key is chosen by the *client*, not the server,
and the key can only look up one actual lease. So the protocol enforces
it, meaning the server must verify the path.
IMHO this was a big mistake in the protocol design.
The server has complete knowledge of what paths map
to what files, so the lease key really should have
been a server created token.
Well, too late now :-).
