-
Notifications
You must be signed in to change notification settings - Fork 4
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
Enable undoing everything on uninstall #27
Comments
Perhaps a good place to start is to see how the "Refresh Firefox" button works to reset the root store. May be related: I have also sent email to a developer who should be able to provide some suggestions. Will let you know what I find out. |
Question for the add-on folks: Can the user make the choice whether to revert to Firefox's default root store or not? Or does uninstall necessarily mean that the root store must be reverted? (i.e. user does not have a choice) My thoughts on approaches... Keeping a log and rolling back the changes sounds complicated and error prone, especially when you consider that the user could use both the built-in Certificate Manager and the Add-on -- rolling back the changes via the Add-on could undo changes made in the Certificate Manager, and could also undo changes made during Firefox release updates or security patches. Another option is to take a snapshot of the user8.db file when the Add-on is installed, then switch back to that version with the Add-on is uninstalled. But that seems risky too, because in the meantime the user might have made a change to the root store for security reasons, and that would get lost. Similarly there might have been Firefox releases or security patches that changed the root store, and those changes would get lost. I think the safest approach would be to do whatever the Firefox Refresh button does with the root store. |
From my email exchange with the developer:
This sounds like a good approach. I recommend saving the triple |
"Any certificate changes made by the add-on must be reverted. You can decide how exactly you are going to implement that as long as that policy is not violated."
The text was updated successfully, but these errors were encountered: