You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I understand it, the updater runs before every startup. However, I learned from @zenmonkeykstop that only in certain occasions does it run the full salt deployment (I think this is happening here).
This makes sense as otherwise this would take too much time. But I wonder if it would be worth adding some sort of smoke test before startup just to make sure all the expected qubes are there and the proper policies in place to protect against the threat of user user mistake.
As it stands Qubes hardly has any foot-shooting protection. So it could be good to explore this extra guard rail. Furthermore, the results of this smoke test could be logged so in case of troubleshooting we could understand if there was some architecture deviation.
The text was updated successfully, but these errors were encountered:
Just came across this test, which I think is exactly what we're looking for. What we want to do here is basically the same thing as running development smoke tests on the state of the machine, no?
As I understand it, the updater runs before every startup. However, I learned from @zenmonkeykstop that only in certain occasions does it run the full salt deployment (I think this is happening here).
This makes sense as otherwise this would take too much time. But I wonder if it would be worth adding some sort of smoke test before startup just to make sure all the expected qubes are there and the proper policies in place to protect against the threat of user user mistake.
As it stands Qubes hardly has any foot-shooting protection. So it could be good to explore this extra guard rail. Furthermore, the results of this smoke test could be logged so in case of troubleshooting we could understand if there was some architecture deviation.
The text was updated successfully, but these errors were encountered: