We're removing support for the SECIO security transport

We're removing support for the SECIO security transport

We're removing support for the SECIO security transport in IPFS and libp2p. You can mitigate impact to your node(s) by updating to the latest versions. Newer nodes should not experience any signficant change when support is removed, but older nodes will start to experience performance degradation. Read on for more details.

# What are security transports?

Security transports are components of libp2p that encrypt data while it is being sent across the network. Libp2p provides the ability to negotiate security transports once a connection is established, giving nodes the ability to support multiple security transports. Once a security transport has been negotiated, all data sent and received is encrypted and only the intended peer can decrypt it.

# A brief history

SECIO is a TLS-like security transport that was developed for IPFS and libp2p in 2014 to alleviate a gap with TLS1.2 requiring Certificate Authorities. SECIO has been the primary security transport for all libp2p implementations as its underlying algorithms are widely supported. In May 2019, go-ipfs 0.4.21 added support for TLS1.3, and in go-ipfs 0.5 in April 2020 it became the default security transport. However, TLS1.3 is still gaining support across libp2p implementations and isn't accessible in browser contexts, so not all libp2p implementations can make it the default security transport. While web browsers have introduced support for TLS1.3, we have no way of attaching the necessary identity information for libp2p.

Go-ipfs 0.6 also added support for the QUIC transport, which internally uses TLS1.3. QUIC is also not yet widely supported, so we still have the same problem as TLS1.3 by itself.

So, how can we successfully deprecate SECIO and move on to more modern and widely-used security transports if we can't support TLS1.3 or QUIC everywhere? The answer is the Noise security transport (opens new window), which was created leveraging the Noise Protocol Framework (opens new window). Noise provides a set of patterns for composing widely supported cryptographic primitives, which allows us to more easily add support across the various libp2p implementations. Support was added for Noise in go-ipfs 0.6, js-ipfs 0.47, and has been updated across major IPFS network infrastructure.

SECIO was never meant to be a permanent security transport. Now that we have Noise for broad support and TLS1.3 for implementations that can support it, it's time for SECIO to be deprecated.

# When is it happening?

SECIO will be removed from go-ipfs in the release of 0.7, which you can track in the Github issue (opens new window). The release is tentatively planned for August 25th. We will also be coordinating a release of js-ipfs around the same time to remove SECIO there as well.

# How does this impact me?


Version Impact
0.5+ Nominal
0.4.21 - 0.4.23 Slower Connection Upgrading
<0.4.21 Connection Failures

Older nodes on the network that only support SECIO will no longer be able to communicate with IPFS nodes after 0.7. If you are running a go-ipfs version older than 0.5, we strongly recommend that you upgrade ASAP. While go-ipfs nodes 0.4.21 and newer have TLS1.3 support, you will experience a latency hit in your connections if you are not on at least IPFS 0.5. This is due to protocol negotiation defaulting to SECIO (which will fail to connect to recent nodes) and needing to be redone with TLS1.3.

If you are running IPFS older than 0.4.21, you are going to start failing to connect to newer nodes at all, which will include the DHT Bootstrap nodes and other critical pieces of IPFS Public Network infrastructure.


Version Impact
0.47+ Nominal
<0.47 Connection Failures*

*We are looking at backporting Noise to js-ipfs 0.46.x.

Noise was added to js-ipfs 0.47, however it is compatible with js-ipfs 0.41.0+ (the async/await refactor (opens new window)) but it needs to be manually configured.

If you are running js-ipfs older than 0.41, you won't be able to connect to nodes who don't support SECIO. You will still be able to leverage the websocket-star server for the time being.

# Updating IPFS