Re:Valve permabans 40,000+ dota2 accounts using honeypot patch
by mabbo on Thursday February 23, 2023 @08:51PM
(#34919670)
World of Warcraft did something that I've always found delightful: hidden stenographic watermarking on all screenshots.
It took like a decade before anyone noticed, but all screenshots were very very very slightly modified to hide (in plain sight) a blob of data that gave the account name, date, time, server, etc.
Just in case a screenshot ever got posted and they really needed to know who took it and when.
Re:Valve permabans 40,000+ dota2 accounts using honeypot patch
by d110af5ccf on Thursday February 23, 2023 @09:10PM
(#34919814)
> that I've always found delightful
Leaking user data to me is a betrayal of trust, incredibly distasteful, and probably borders on illegal (it ought to be imo). Note that this is fundamentally different than watermarking streaming content or other material that the user is not legally permitted to copy. Watermarking the game binaries themselves, for example, would be entirely different and perfectly acceptable from my perspective.
Re:Valve permabans 40,000+ dota2 accounts using honeypot patch
by FateOfNations on Friday February 24, 2023 @03:08AM
(#34922164)
While WoW didn't do this, one could avoid disclosing user data to third parties by encrypting the watermark payload.
Re:Valve permabans 40,000+ dota2 accounts using honeypot patch
by rany_ on Friday February 24, 2023 @06:42AM
(#34923511)
This works until the encryption key is leaked.
Re:Valve permabans 40,000+ dota2 accounts using honeypot patch
by ironick09 on Thursday February 23, 2023 @09:17PM
(#34919882)
Do you have any resources/information you can share on this? I’d be curious to read more.
Re:Valve permabans 40,000+ dota2 accounts using honeypot patch
by lights0123 on Thursday February 23, 2023 @09:45PM
(#34920109)
Obfuscation and deobfuscation is also super interesting. I think overall reverse engineering and figuring out how things work is one of the most interesting things in computer science.
https://github.com/obfuscator-llvm/obfuscator/tree/llvm-4.0/...
https://blog.quarkslab.com/deobfuscation-recovering-an-ollvm...