-
Notifications
You must be signed in to change notification settings - Fork 60
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
[agent] Define schemas for capabilities negotiation during PoP authentication #933
Labels
rust
Pull requests that update Rust code
Comments
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 24, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 25, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/rust-keylime
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: keylime#933 Signed-off-by: Sergio Arroutbi <[email protected]>
ansasaki
pushed a commit
that referenced
this issue
Feb 26, 2025
This change aims to include those structures that will be required to communicate capabilities negotiation information for Keylime Push model Resolves: #933 Signed-off-by: Sergio Arroutbi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
The first step in the new authentication mechanism based on Proof of Possesion (PoP) is the negotiation of capabilities from the agent. The agent needs to provide:
For each supported authentication method type (currently, only AK PoP) a new type should be added. The added types should all be serializable using the serde crate to JSON format.
This is about defining the schema for each evidence type to be used during the capabilities negotiation.
Checklist:
The text was updated successfully, but these errors were encountered: