ohhhhh, the reason i couldn't find any device-specific code in the binary i was reverse-engineering is because it was all living in encrypted lisp blobs
@gsuberland yeah I'm currently looking at it... both binaries have the same mouthfeel but I can't tell yet if it's really the same ISA or just a variation
@gsuberland i don't think it is the same ISA and also the plugin fails to load in IDA. i don't know IDA and don't have a copy of it anyways, but i can give you the unpacked binaries
dearmor the blob, put it all in openpgp.ReadMessage, you can now enjoy the lisp blobs that have the programming algorithms for firmware updates and other "trade secrets" of Avnera
(I don't think Frederick G. Weiss cares anymore; I can imagine he's enjoying his comfortable retirement on some of the $400m that Skyworks bought Avnera for)
(I have no issue with SteelSeries who almost certainly did not implement this out of a desire for secrecy but rather were forced to by their agreements with their suppliers. fortunately I'm not bound by those so I can do whatever. it's for interoperability!)
@hughsie heh, that could potentially be useful, but my headset for example has only ever had a single firmware released... as far as i know anyway. it's the same one they ship from factory
@whitequark bc fuck blobs? NVIDIA alone can do some actions I won't describe here. Most of these companies sell firmware updates as part of a support contract, I mean look at HPE. they're notorious for that. It's always based to drop blobs and give back access to the hardware. i don't own a steelseries but to anyone who needs that at least now they have it. there's been times I've been stumped and could not do anything with hardware i had due to stupid shit like this.
Add comment