View Single Post
Old 12-11-2023, 03:31 PM   #8
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,514
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
Quote:
Originally Posted by NiLuJe View Post
I'd wager this just grays out the menu entries, as a factory reset, while probably done for privacy reasons in that case, also happens, to, as a byproduct, remove the pin lock .

(i.e., I doubt there's a specific "let me just kill the pincode" codepath for that convoluted setup).
Yes, I found out that this code works even when trying to "remember" parental passcode, so it is uselless beyong GUI "restrictions.

Ultimately, I can just nuke the "factory_reset" binary (by replacing it with a /dev/null link), but it sits in /bin/ , and I am hesitant to touch it (in contrast to logging things, that sit in /usr/bin/ and /usr/sbin).

Last edited by mergen3107; 12-11-2023 at 05:26 PM.
mergen3107 is offline   Reply With Quote