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
It seems it's rather easy to create an insecure environment with the default configs where AS token signer material and/or KBS tokenverifier trusted_certs_paths are not set.
The proposal is to add an "insecure" opt-in similar to how the existing insecure_* switches work to at least in the tokenverifier to fail tokens if the opt-in is not enabled.
How to reproduce
Run Trustee KBS with one of the default kbs/config/*.toml without trusted_certs_paths. With that, the following takes place
Describe the bug
Triggered by #483.
It seems it's rather easy to create an insecure environment with the default configs where AS token signer material and/or KBS tokenverifier
trusted_certs_paths
are not set.The proposal is to add an "insecure" opt-in similar to how the existing
insecure_*
switches work to at least in the tokenverifier to fail tokens if the opt-in is not enabled.How to reproduce
Run Trustee KBS with one of the default
kbs/config/*.toml
withouttrusted_certs_paths
. With that, the following takes placetrustee/kbs/src/token/coco.rs
Lines 93 to 96 in 5c973bd
CoCo version information
trustee v0.9.0
What TEE are you seeing the problem on
None
Failing command and relevant log output
The text was updated successfully, but these errors were encountered: