Skip to content

AesGcm.IsSupported and AesCcm.IsSupported should not unconditionally return true for MacOS #52598

Closed
@vcsjones

Description

@vcsjones

In #52030, AesGcm.IsSupported and AesCcm.IsSupported were introduced.

For macOS, these properties unconditionally return true even if there is no usable version of OpenSSL found on the system.

This leads to a somewhat bad experience. IsSupported will return true, but attempting to use AesGcm or AesCcm will result in a SIGABRT of the whole process, with the message "No usable version of libssl was found".

Ideally these properties would correctly handle OpenSSL not being available.

With ChaCha20Poly1305 the situation is slightly worse: The IsSupported property itself trigger the faulting behavior when it calls into the shim to ask if the current version of OpenSSL supports the algorithm.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions