Skip to content

Let's not have ex_data within the FIPS provider module #10835

@levitte

Description

@levitte

Recent changes in crypto/dsa/ showed some key creating functions that take an OPENSSL_CTX as argument... for the sole reason of supporting ex_data in the DSA structure. Interestingly enough, the functions to get or set ex_data are not included in the compilation of the FIPS module, making that DSA field useless.

I would like to suggest that ex_data fields in diverse structures (such as low level key-pairs) are simply unsupported. They exist purely for the sake of the application, which will never reach that deeply into the entrails of any provider, making ex_data support of that sort pretty moot.

Note There are still CRYPTO_EX_DATA items that need to remain supported, as the whole OPENSSL_CTX construct relies on that. That's not what I'm talking about here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triaged: refactorThe issue/pr requests/implements refactoring

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions