Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use OpenSSL as an optional crypto provider #1529

Closed
syedriko opened this issue Jul 5, 2022 · 2 comments
Closed

Use OpenSSL as an optional crypto provider #1529

syedriko opened this issue Jul 5, 2022 · 2 comments

Comments

@syedriko
Copy link

syedriko commented Jul 5, 2022

In a FIPS environment, there is a requirement that all crypto operations are delegated to a FIPS-certified crypto module. Some Linux distributions, such as RHEL, ship FIPS-certified OpenSSL. In order for the SDK to be usable in such environment, it should be possible to rely on OpenSSL for all crypto needs.
#261 seems to be related.
@syedriko syedriko changed the title Use OpenSSL as an optional crypto provider, for use with FIPS. Use OpenSSL as an optional crypto provider Jul 5, 2022
syedriko added a commit to syedriko/smithy-rs that referenced this issue Jul 5, 2022
@syedriko
Use OpenSSL as an optional crypto provider (smithy-lang#1529)
90097f3 
A first stab at making OpenSSL an alternative crypto provider in aws-sigv4 and
aws-config, so the SDK can be consumed in a FIPS environment.
syedriko added a commit to syedriko/smithy-rs that referenced this issue Jul 5, 2022
@syedriko
Use OpenSSL as an optional crypto provider (smithy-lang#1529)
96aadef 
A first stab at making OpenSSL an alternative crypto provider in aws-sigv4 and
aws-config, so the SDK can be consumed in a FIPS environment.
@syedriko syedriko mentioned this issue Jul 5, 2022
Closed
syedriko added a commit to syedriko/smithy-rs that referenced this issue Jul 5, 2022
@syedriko
Use OpenSSL as an optional crypto provider (smithy-lang#1529)
3983cc8 
A first stab at making OpenSSL an alternative crypto provider in aws-sigv4 and
aws-config, so the SDK can be consumed in a FIPS environment.
@syedriko syedriko mentioned this issue Jul 5, 2022
Open
@syedriko
Copy link
Author

syedriko commented Jul 5, 2022

For the sake of cross-referencing, here is the corresponding issue for Vector the observability data pipeline tool: vectordotdev/vector#8435

syedriko added a commit to syedriko/smithy-rs that referenced this issue Jul 6, 2022
@syedriko
Use OpenSSL as an optional crypto provider (smithy-lang#1529)
c2f972b 
A first stab at making OpenSSL an alternative crypto provider in aws-sigv4 and
aws-config, so the SDK can be consumed in a FIPS environment.
syedriko added a commit to syedriko/smithy-rs that referenced this issue Sep 20, 2022
@syedriko
Use OpenSSL as an optional crypto provider (smithy-lang#1529)
755ad43 
A first stab at making OpenSSL an alternative crypto provider in aws-sigv4 and
aws-config, so the SDK can be consumed in a FIPS environment.
@jdisanti
Copy link
Collaborator

jdisanti commented Apr 5, 2024

Closing in favor of tracking issue #3563.

@jdisanti jdisanti closed this as completed Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jdisanti @syedriko