Blizzard Exempt from iOS and MacOS Security Sandbox

Re:Blizzard Exempt from iOS and MacOS Security Sandbox by JoachimSchipper on Thursday June 02, 2016 @11:58AM (#11823566)

You're looking at the output of a disassembler, not at the original source code. It probably reads something boring like sizeof(Identifier) in the original.

[ Parent | on HN ]

Re:Blizzard Exempt from iOS and MacOS Security Sandbox by LeifCarrotson on Thursday June 02, 2016 @12:52PM (#11824053)

That's exactly what it is. The third parameter to memcmp is the length of the buffers to be compared - "G847MC6JZ5", the string being compared, has a length of 11 characters (including the null terminator, which is a little odd). 11 is B in hex, and is stored as an unsigned Long Long, so the representation in the disassembler is 0xBuLL.

And that string is the Blizzard identifier: https://www.virustotal.com/en/file/bdfd2017fb776b52a4604928e...

[ Parent | on HN ]

Re:Blizzard Exempt from iOS and MacOS Security Sandbox by tomlogic on Thursday June 02, 2016 @01:32PM (#11824413)

Not odd to include the null terminator if you want to ensure another string is "equal to", not just "starts with" the string you're comparing it to.

[ Parent | on HN ]

Re:Blizzard Exempt from iOS and MacOS Security Sandbox by mzs on Thursday June 02, 2016 @02:48PM (#11825048)

Dang it, I counted the \0 but miscounted the characters in the string.

[ Parent | on HN ]