View Single Post
Old 11-13-2012, 08:04 PM   #133
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Quote:
Originally Posted by knc1 View Post
There is no partition 0 (mmcblk0p0) .
There is data stored outside of the partition table, in the frontmost part of mmcblk0.
That part of the storage contains, among other things, the machine specific data.
Share that between two (or more) Kindles will get them both (all) blacklisted.
But on a K4 or newer model, any dump made with "dd" will show zeroes on the idme vars (serial number and such), so even that should be safe. You can only read those vars via kernel /proc files, which is what "idme" uses for reading. Interestingly, you can WRITE to that storage location yourself, so it is easy enough to write the values that you cannot read.

It is the K3 and earlier that expose the idme vars for reading by use apps.

It would be good to replace the root password hash in /etc/shadow with the known mario DES hash (copied from a known mario shadow file). Otherwise the root password will not be computable for any serial number but yours...
geekmaster is offline   Reply With Quote