Skip to content

Steps to a stable 7.0.0 #290

Closed
Closed
@ionut-arm

Description

@ionut-arm

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):

Another type that currently uses other FFI types in its interface is CapabilityData. The types:

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 example Sm4KeyBits 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
  • For structures that can be built using ...Builder structures, we should either document this or create a method on the type to get a new builder, something like pub fn builder() -> ... ( Add builder methods and move NvPublic #316 )

Metadata

Metadata

Assignees

No one assigned

    Labels

    largeEffort label

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions