-
Notifications
You must be signed in to change notification settings - Fork 57
Steps to a stable 7.0.0 #290
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
Comments
@rshearman - Do you require any specific features in the upcoming release (more specifically, |
It would be good to have TPM2_Certify in the upcoming release, but I'm decoupled from the tss-esapi release cycle. In other words, it would also be fine to have this in a future minor release. |
@Superhepper - have you, by any chance, started working on |
Nah I have not started any work on it. I plan to work on the issue with tagged PCR property list |
Cool, I've raised #306 to cover the |
@Superhepper - |
Right now I am working with TPMA_CC. |
Will do the |
No, I usually add stuff if a find things a long the way. |
After #316 is merged are we clear to release a 7.0.0, or is there some other stuff to be done? |
I maybe want to add the compilation bug for PcrSlot. But if people need a released major version rather soon. I think we can make a release without it. |
If we can get that fix in next week that would be nice, but otherwise it's not a breaking change, I think, so we can release it as a bugfix update, not even a minor bump. |
Yeah, just say the release will come on Friday next week. If it makes it, it makes it otherwise it will be added later. |
@puiterwijk @lkatalin @rshearman |
Thanks for the heads up @ionut-arm ! I just ran a test and it seems fine for us with Keylime. |
I've released a |
I've updated our application to use |
I've just released and tagged tss-esapi-7.0.0-beta.2 with the changes requested above by @rshearman |
The 7.0.0 stable version has been released and tagged! 🎉 Please let us know if any issues surface, so we can fix them right away! |
Since we're currently in an alpha release (yet again) it would be good to know what we'd like to achieve before we can tag a stable release. Our focus right now is to remove all not-abstracted FFI types from the
tss-esapi
interface, replacing them with types that we have more control over.FFI types still present in the
Context
interface (not going to link to where they appear, a simple search through the repo should be enough for that):will be lifted from Add TPM2_Certify #221; Adds the attest structures #293 covers this )Another type that currently uses other FFI types in its interface is
CapabilityData
. The types:CapabilityData
with the existing abstraction, Adds TaggedTpmProprtyList #301)Other bits of work:
I was also wondering about changing a few other things, please list any other ideas/concerns below:
Some key-bits types seem redundant, for exampleSm4KeyBits
can only have one value. I wonder if it wouldn't be better to just remove the type completely and have a "default" implementation that produces the correct FFI values wherever they're needed to replace the current conversions...Builder
structures, we should either document this or create a method on the type to get a new builder, something likepub fn builder() -> ...
( Add builder methods and move NvPublic #316 )The text was updated successfully, but these errors were encountered: