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
Given this is a reimplementation of the tpm2 clevis pin -- which became the default tpm2 pin implementation in Fedora, since then --, I wonder if it makes sense to move this project to the latchset umbrella, where clevis itself and other related projects (e.g. tang, jose) are maintained.
As there is a good chance this implementation might move to the clevis codebase itself sometime in the future, a move like this would make that easier, should it happen. In any case, maintainance-wise, it would still be maintained by the clevis maintainers -- what is kind of the case at the moment.
Given this is a reimplementation of the tpm2 clevis pin -- which became the default tpm2 pin implementation in Fedora, since then --, I wonder if it makes sense to move this project to the latchset umbrella, where clevis itself and other related projects (e.g. tang, jose) are maintained.
As there is a good chance this implementation might move to the clevis codebase itself sometime in the future, a move like this would make that easier, should it happen. In any case, maintainance-wise, it would still be maintained by the clevis maintainers -- what is kind of the case at the moment.
Please let me know your thoughts, @nullr0ute / @puiterwijk
The text was updated successfully, but these errors were encountered: