Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Safety against recovery mode? #7

Open
refi64 opened this issue Mar 19, 2020 · 3 comments
Open

Safety against recovery mode? #7

refi64 opened this issue Mar 19, 2020 · 3 comments
Labels
confirmation needed enhancement New feature or request question Further information is requested

Comments

@refi64
Copy link

refi64 commented Mar 19, 2020

I stumbled upon this repo as was quite exited, as I've always enjoyed using Chrome OS. However, there was a major issue I ran into last time I dual booted: I messed with the rootfs, boot broke, and then the recovery process wiped my entire hard drive. Now, I asked on the chromefy repo, and they said there there wasn't anything done in defense, which is understandable since it's a pure Chrome OS USB maker. However, given the multiboot focus of this repo, what would be the chances of it handling this case more safely?

@MuntashirAkon
Copy link
Owner

However, there was a major issue I ran into last time I dual booted

So, you dual booted using the tools available on the Chromefy repo?

the recovery process wiped my entire hard drive.

How/what recovery process did you follow? Powerwash doesn't have the ability to wipe your entire drive.

However, given the multiboot focus of this repo, what would be the chances of it handling this case more safely?

I can definitely improve things once I understand what to do.

@MuntashirAkon MuntashirAkon added confirmation needed enhancement New feature or request question Further information is requested labels Apr 12, 2020
@refi64
Copy link
Author

refi64 commented Jun 26, 2020

(Sorry for the delayed reply)

So I looked into this a bit more, I found that recovery_install.sh is what calls into a Chrome OS reinstall script, and chromeos-install wipes the GPT. I can't figure out where this is called; however, this file is present on the rootfs, in /usr/sbin.

Thus, if chromeos-recovery could be blocked / removed somehow, I think this would remove any risks.

@MuntashirAkon
Copy link
Owner

Thus, if chromeos-recovery could be blocked / removed somehow, I think this would remove any risks.

Ok, I'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmation needed enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants