-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/crypto/ssh: add fipsonly mode #64769
Comments
Change https://go.dev/cl/550515 mentions this issue: |
This proposal has been added to the active column of the proposals project |
…hanges `x/crypto/ssh` is adding a `fipsonly` mode (similar to `crypto/tls/fipsonly`) in golang/go#64769. Once this has landed and been released, we'll swap to using it. In the meantime, update our hardcoded algorithm set to match the algorithms listed in https://go-review.googlesource.com/c/crypto/+/550515. The only difference is that `aes192-ctr` is kept in `FIPSCiphers`, as it seems to be approved by NIST SP 800-131A rev 2 (page 17). Additionally, we now define a list of approved public key authentication algorithms for SSH server connections. This isn't configurable for normal use case (yet), only handled for FIPS builds.
…hanges (#36685) `x/crypto/ssh` is adding a `fipsonly` mode (similar to `crypto/tls/fipsonly`) in golang/go#64769. Once this has landed and been released, we'll swap to using it. In the meantime, update our hardcoded algorithm set to match the algorithms listed in https://go-review.googlesource.com/c/crypto/+/550515. The only difference is that `aes192-ctr` is kept in `FIPSCiphers`, as it seems to be approved by NIST SP 800-131A rev 2 (page 17). Additionally, we now define a list of approved public key authentication algorithms for SSH server connections. This isn't configurable for normal use case (yet), only handled for FIPS builds.
…hanges `x/crypto/ssh` is adding a `fipsonly` mode (similar to `crypto/tls/fipsonly`) in golang/go#64769. Once this has landed and been released, we'll swap to using it. In the meantime, update our hardcoded algorithm set to match the algorithms listed in https://go-review.googlesource.com/c/crypto/+/550515. The only difference is that `aes192-ctr` is kept in `FIPSCiphers`, as it seems to be approved by NIST SP 800-131A rev 2 (page 17). Additionally, we now define a list of approved public key authentication algorithms for SSH server connections. This isn't configurable for normal use case (yet), only handled for FIPS builds.
…hanges (#36709) `x/crypto/ssh` is adding a `fipsonly` mode (similar to `crypto/tls/fipsonly`) in golang/go#64769. Once this has landed and been released, we'll swap to using it. In the meantime, update our hardcoded algorithm set to match the algorithms listed in https://go-review.googlesource.com/c/crypto/+/550515. The only difference is that `aes192-ctr` is kept in `FIPSCiphers`, as it seems to be approved by NIST SP 800-131A rev 2 (page 17). Additionally, we now define a list of approved public key authentication algorithms for SSH server connections. This isn't configurable for normal use case (yet), only handled for FIPS builds.
No change in consensus, so accepted. 🎉 Proposal is to add a new x/crypto/ssh/fipsonly package that is _ imported for the side effect of changing SSH configuration to FIPS-approved settings. The package only exists with GOEXPERIMENT=boringcrypto. |
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
@drakkan - Can you please let us know when would the change request |
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Fixes golang/go#64769 Change-Id: I4132438bc5586215661c2c1872b5a6c7464badf4
Proposal Details
Similar to
crypto/tls/fipsonly
addgolang.org/x/crypto/ssh/fipsonly
The text was updated successfully, but these errors were encountered: