Duplicate SMB file_ids leading to Windows client cache poisoning

[Ralph Boehme]

On 12/10/21 17:56, Andrew Walker wrote:
> That's a good point, but if MacOS SMB client is faking up an inode 
> number based on a hash of the filename in the zero-id case, isn't it 
> even more likely to yield a collision at some point?

well, it's somehash(name) combined with the parent-inode number. I know, 
it's not ideal.

But going back to inode numbers brings us back to:

https://bugzilla.samba.org/show_bug.cgi?id=12715

*scratches head*

-slow

-- 
Ralph Boehme, Samba Team                 https://samba.org/
SerNet Samba Team Lead      https://sernet.de/en/team-samba
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20211210/3a10ecc5/OpenPGP_signature.sig>