gecko-dev/dom/media/gmp/rlz
James Cheng 8107c910bc Bug 1422669 - Part4 - Kill string16 and replace with our SHA1 implementation. r=gerald
The reason explained in patch Part1 of Bug 1214018 and I just copy the reason below.

GetRawMachineId was returning its generated data through a 'string16', which on
Windows was conveniently equivalent to a std::wstring.

However on Mac, wstring uses 32-bit characters, so in order to comply with the
string16 interface, a lot of non-trivial code would have to be imported and
vetted.

Also, in the end GMPLoader::Load passes this string16 to SHA256_Update() as a
sequence of bytes, the actual type of the data is lost!

So to simplify this work, GetRawMachineId will now return its data through a
vector of bytes, and the platform-dependent implementations may use whatever
data type they want internally.

The Windows GetRawMachineId actually returns the same data in this vector, so
it stays compatible with the previous code.

MozReview-Commit-ID: 7xYgjndXWDX

--HG--
extra : rebase_source : 6a46bd7f06d6e4bc10bb98b600e7e5bc14c136ce
2017-12-06 16:52:31 +08:00
..
lib Bug 1422669 - Part4 - Kill string16 and replace with our SHA1 implementation. r=gerald 2017-12-06 16:52:31 +08:00
mac/lib Bug 1422669 - Part2 - Fix compiling error [-Werror,-Wcomma] by Part1 on OSX. r=gerald 2017-12-06 06:33:02 +00:00
win/lib
OWNERS
README.mozilla
moz.build Bug 1422669 - Part4 - Kill string16 and replace with our SHA1 implementation. r=gerald 2017-12-06 16:52:31 +08:00

README.mozilla

Code taken from rlz project in Chromium repository: https://chromium.googlesource.com/chromium/src.git/+/6f3478dfd7d29b9872871718bd08493ed0c8bc8e

Note: base/ contains wrappers/dummies to provide implementations of the
Chromium APIs that this code relies upon.