kairos
kairos copied to clipboard
kairos-io
[factory web ui] add trusted boot support
When selecting trusted boot, the user should be able to provide their own keys, or the factory should build new keys for them. If the latter, then it should also allow to download those keys
IMO, we should not do this. Not handling PRIVATE keys in web its nice and we cnanot be held responsible for losing them.
If you want to use trusted keys, we could just have a demo mode that uses our test keys so you can test this stuff, but should redirect users to run trusted boot builds (outputs, because the container need no keys) to do themloally, off the internet if possible
Could you enable this via some flag/var such that trusted boot can be selected via the webui when serving locally (instead of your public internet instance)?
IMO, we should not do this. Not handling PRIVATE keys in web its nice and we cnanot be held responsible for losing them.
Nothing forbids to run the webui locally and let the user handle the keys as they prefer.
IMO, we should not do this. Not handling PRIVATE keys in web its nice and we cnanot be held responsible for losing them.
Nothing forbids to run the webui locally and let the user handle the keys as they prefer.
Sure but what about browser extensions for example? And the more stuff is in a machine the more the surface attack is.
IMHO the only way to work with keys for signing this stuff is in a offline, updated, minimal machine. No desktop or browsers.
Take into account that I'm talking about a public instance here, for example ours if we setup this online. If we want to provide a flag to enable that and let people know the risks then I'm ok with having the option.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
IMO, we should not do this. Not handling PRIVATE keys in web its nice and we cnanot be held responsible for losing them.
Nothing forbids to run the webui locally and let the user handle the keys as they prefer.
Sure but what about browser extensions for example? And the more stuff is in a machine the more the surface attack is.
IMHO the only way to work with keys for signing this stuff is in a offline, updated, minimal machine. No desktop or browsers.
Take into account that I'm talking about a public instance here, for example ours if we setup this online. If we want to provide a flag to enable that and let people know the risks then I'm ok with having the option.
Agreeing here about online use - indeed in my comment I refered to be able to use it locally.
However using the browser to drive the building process is still very much wanted to simplify the UX and streamline usage aside the cli.
