Skip to content
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

Extensible seal mechanism #16

Open
bnevis-i opened this issue Dec 10, 2023 · 3 comments
Open

Extensible seal mechanism #16

bnevis-i opened this issue Dec 10, 2023 · 3 comments
Labels

Comments

@bnevis-i
Copy link

bnevis-i commented Dec 10, 2023

I could be mistaken, but I do not think that the current seal mechanism is extensible. It would be useful, in IoT scenarios for example, to be able to support hardware seals that aren't enterprise HSM's (for example, a TPM 2.0 seal).

@joewxboy
Copy link
Contributor

@bnevis-i This sounds like an interesting and potentially valuable feature, but also one that will take a non-trivial amount of work to implement. If so, do we have a "Sponsor User" in mind who is looking to use this who can help inform requirements and facilitate acceptance testing?

@joewxboy joewxboy added the rfc label Dec 10, 2023
@jbutlerdev
Copy link
Contributor

I can't really meet the needs of what @joewxboy is looking for, however I'm definitely interested in helping make this happen. This is a feature I've been looking for in the past.

@cipherboy
Copy link
Member

I think these are two separate discussion topics, do you mind splitting them into two?

@bnevis-i bnevis-i changed the title Extensible seal mechanism, ability to seal own TLS certificate Extensible seal mechanism Dec 11, 2023
cipherboy pushed a commit to cipherboy/openbao that referenced this issue Jan 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants