View Single Post
Old 06-28-2012, 11:18 PM   #22
geekmaster
Carpe diem, c'est la vie.
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: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by kirokko View Post
After update to 4.1.0 password was changed. /etc/shadow file in diags partition was replaced (maybe it was done another way) with /etc/shadow- in main (mmcblk0p1) partition. Main partition also has /etc/shadow with mario password. What if somebody edit image file and replce /etc/shadow- with /etc/shadow? Will this hack work? It might break the firmware update if it will check the shadow file during update (not only 4.1.0 but future updates).
I think the firmware update uses a calculated (original serial-number based) password, not the one stored in /etc/shadow. Others had changed the root pw with no OTA update breakage.
geekmaster is offline   Reply With Quote