[GH-ISSUE #465] Request: leverage another crypto library that would allow for FIPS validation #857

Closed
opened 2026-08-05 00:40:10 -04:00 by saavagebueno · 5 comments
Owner

Originally created by @finnje on GitHub (Sep 12, 2022).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/465

Wireguard itself won't be FIPS validated as the encryption algorithms aren't approved for FIPs validation, but other crypto in use, for example the netbird ssh connections could be FIPS validated if something like https://github.com/golang-fips/go was used instead of the default go crypto library.

Originally created by @finnje on GitHub (Sep 12, 2022). Original GitHub issue: https://github.com/netbirdio/netbird/issues/465 Wireguard itself won't be FIPS validated as the encryption algorithms aren't approved for FIPs validation, but other crypto in use, for example the netbird ssh connections could be FIPS validated if something like https://github.com/golang-fips/go was used instead of the default go crypto library.
saavagebueno added the enhancementfeature-requestagent labels 2026-08-05 00:40:10 -04:00
Author
Owner

@braginini commented on GitHub (Sep 14, 2022):

hey @finnje
Do you have an idea how to combine this lib with Golang's SSH server? I haven't looked into that yet.

<!-- gh-comment-id:1246379228 --> @braginini commented on GitHub (Sep 14, 2022): hey @finnje Do you have an idea how to combine this lib with Golang's SSH server? I haven't looked into that yet.
Author
Owner

@laserguy2020 commented on GitHub (Nov 3, 2022):

This would be awesome... +1 from me.

<!-- gh-comment-id:1302409713 --> @laserguy2020 commented on GitHub (Nov 3, 2022): This would be awesome... +1 from me.
Author
Owner

@nazarewk commented on GitHub (Apr 17, 2025):

@finnje Does it still make sense if the context of the plans to replace internal SSH implementation with the reuse of the existing OpenSSH infrastructure?

<!-- gh-comment-id:2813216812 --> @nazarewk commented on GitHub (Apr 17, 2025): @finnje Does it still make sense if the context of the plans to replace internal SSH implementation with the reuse of the existing OpenSSH infrastructure?
Author
Owner

@finnje commented on GitHub (Apr 17, 2025):

@nazarewk if the goal is to switch to the underlying systems ssh package like OpenSSH then no this wouldn't be required as you could ensure your system SSH package is FIPS validated if required by your environment.

<!-- gh-comment-id:2813624465 --> @finnje commented on GitHub (Apr 17, 2025): @nazarewk if the goal is to switch to the underlying systems ssh package like OpenSSH then no this wouldn't be required as you could ensure your system SSH package is FIPS validated if required by your environment.
Author
Owner

@PizzaLovingNerd commented on GitHub (May 28, 2026):

Closing as part of issue consolidation. This is not implemented as originally requested (FIPS-capable crypto for NetBird’s embedded SSH via e.g. golang-fips). Since v0.60+, NetBird supports native OpenSSH clients against the embedded SSH server (port 22022), not replacing that server with system sshd. For FIPS SSH requirements, use your platform’s FIPS-validated OpenSSH/sshd and NetBird TCP access policies on port 22, rather than --allow-server-ssh. Note that WireGuard remains non-FIPS, so full NetBird VPN crypto cannot meet FIPS tunnel requirements regardless of SSH.

<!-- gh-comment-id:4567707426 --> @PizzaLovingNerd commented on GitHub (May 28, 2026): Closing as part of issue consolidation. This is not implemented as originally requested (FIPS-capable crypto for NetBird’s embedded SSH via e.g. golang-fips). Since v0.60+, NetBird supports native OpenSSH clients against the embedded SSH server (port 22022), not replacing that server with system sshd. For FIPS SSH requirements, use your platform’s FIPS-validated OpenSSH/sshd and NetBird TCP access policies on port 22, rather than --allow-server-ssh. Note that WireGuard remains non-FIPS, so full NetBird VPN crypto cannot meet FIPS tunnel requirements regardless of SSH.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#857