Niklas Ulvinge wrote: > > I think I've read on multiple locations that on the older models, the > aupd was encrypted, but osos wasn't. It was on the new one's that osos > got encrypted too, and thus leaving us no entry to run our own code. > Isn't this true?
No, it's wrong. :) > And, someone with authorization could maybe put this todo list on the > website if it's good enough? > > === TODO LIST === > * Decrypt the firmware files > __* Get hold of decrypted data or the decryption algorithm on the flash > ____* Get to the data of the flash > ______* Run some code on the flash that extracts it > ________* Find some bug in the hardware/software > ________* Write your own memmory dumping game > ______* Find the JTAG pin and use it > ______* Extract the flash chip and read it manualy > __ * Crypto attacks We got the following one already: http://home.gna.org/linux4nano/ongoing.html This is still more or less up-to-date. >> By the way: Why wasn't pdfLaTeX used for the blackbox and crypto >> synthesis? The pdfLaTeX-generated links and bookmarks in the hardware >> synthesis help navigating a lot. I agree. Regards -- Emmanuel Fleury Anyone who has never made a mistake has never tried anything new. -- Albert Einstein _______________________________________________ Linux4nano-dev mailing list [email protected] https://mail.gna.org/listinfo/linux4nano-dev http://www.linux4nano.org
