On Wed Sep 11 00:36:31 2024 +0000, Elizabeth Figura wrote:
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.
@Alcaro The file can be encrypted, for example, using TPM, the checksum allows you to prohibit changing the file manually. Slightly better protection against counterfeiting and changing the ID. Will complicate the task a little. TPM can completely solve the problem, but for TPM there must be something like system trust levels, as is done in Windows. TPM is not required, but it can increase the level of trust in the system. The presence of TPM in wine can help game and anti-cheat creators to port games to Linux.
@zfigura In Windows, boot id is a unique bcd entry that does not change, is constant, and can only change after reinstalling the system or bootloader. I assume that anti-cheats can ban cheaters by boot id, so it is advisable to make a unique id that is difficult to simply change. But in fact, they ban most often by the serial number of the disk, the MAC of the network card, the serial number of the motherboard, the TPM module. Even if they ban based on other unique system features, boot id can help catch cheaters who most often change the serial number of the HDD and the MAC address of the network card. Thus, the more unique features a system has, the better.
Reference: https://www.unknowncheats.me/forum/apex-legends/644651-hwid-banned-linux.htm...