-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Add an motd warning when ublue's keys are not enrolled #1651
Comments
So there would need to be a script that does the following pseudo code:
I'm new here so I don't know all the constraints with the ublue stack, but I'm assuming writing to I'm just spitballin` |
@jardon For development you can do There's an existing check for the image being out of date that throws a "check engine light", that can be found here: I would add another check like this and make the existing one an elif, use |
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
- Add logic to check for SB enrollment and keys - Update motd template
The script's "good" state is reported to systemd as a failure:
|
We need to run this for a while in the MOTD and do a corresponding announcement on the forums. Let's block bringing fsync to stable. It'd help avoid situations like this: #1636
The text was updated successfully, but these errors were encountered: