On Wed Sep 11 00:09:40 2024 +0000, Alfred Agrell wrote:
Registry or file both sound good to me. Small binary pieces usually go in registry, but I have no strong preference. The registry is just a file, anyways. I do, however, question why you're proposing (1) appending a hash (I can't see what that would accomplish) (2) storing something other than a DLL in a file named .dll (I'd use something generic, like .bin or .dat) (3) using a TPM (unlike some win32 implementations, Wine doesn't require TPM - and there's no public key cryptography or boot measurement involved here, so TPM accomplishes nothing even if available) (4) going via wineserver (I can't see what that would accomplish either, files and registry are available to everyone). If you want to prevent users from resetting or customizing the boot ID, you're gonna have a bad time. Wine is open source, a dedicated user could simply modify ntdll. You cannot prevent that.
Why would we store it in a file? The point of my suggestion was that the boot identifier isn't stable past a single boot. If that's the case it would make the most sense to put it in a volatile registry key.