Comment by keepamovin 3 days ago Does this mean TS is not FIPS 140-3 now? 3 comments keepamovin Reply tatersolid 2 days ago It never was FIPS-approved and likely will never be. The wireguard protocol used by Tailscale uses ChaCha20 for encryption which is not FIPS approved. keepamovin 2 days ago Interesting. What is the FIPS version of wireguard? cronos 2 days ago There are some forks that are not compatible with regular wireguard, for example from wolfssl. Or just classic mTLS.
tatersolid 2 days ago It never was FIPS-approved and likely will never be. The wireguard protocol used by Tailscale uses ChaCha20 for encryption which is not FIPS approved. keepamovin 2 days ago Interesting. What is the FIPS version of wireguard? cronos 2 days ago There are some forks that are not compatible with regular wireguard, for example from wolfssl. Or just classic mTLS.
keepamovin 2 days ago Interesting. What is the FIPS version of wireguard? cronos 2 days ago There are some forks that are not compatible with regular wireguard, for example from wolfssl. Or just classic mTLS.
cronos 2 days ago There are some forks that are not compatible with regular wireguard, for example from wolfssl. Or just classic mTLS.
It never was FIPS-approved and likely will never be. The wireguard protocol used by Tailscale uses ChaCha20 for encryption which is not FIPS approved.
Interesting. What is the FIPS version of wireguard?
There are some forks that are not compatible with regular wireguard, for example from wolfssl. Or just classic mTLS.