View Single Post
Old 12-13-2020, 01:14 PM   #11
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
The loophole wasn't actually kept secret at all, because there's no actual loophole.

Someone just happened to get a Kindle that slipped a QA step and knew what do to with that fact . And we got extremely lucky with the way that QA image was packaged (which may, in fact, have been a quick shortcut to make the QA process more streamlined at the time, e.g., release crunch).

It's entirely plausible that this happened to get fixed just because someone at lab126 was in the vicinity of the updater's code for whatever reason, looked at it and went: "well, that's dumb".

Last edited by NiLuJe; 12-13-2020 at 01:20 PM.
NiLuJe is offline   Reply With Quote