GitLab

TODO: do we want to introduce a length option to generateConfig()? This
would be super useful for testing, but the overhead is quite big. Maybe
it's better to just allow 1 or 2 certificates.
For now, we can just leave it as is, since we'll bump the QUIC version

obey the multiaddr's IP version

make the gx build work

use a single packet conn for all outgoing connections

use multiaddr.Encapsulate to create QUIC multiaddrs

use the context for dialing

disable source address validation

The certificate chain used for the handshake is relatively small (it
fits in 2 packets). This reduces the risk that an attacker will use
libp2p nodes for reflection attacks.

close and discard a connection if the client's cert chain is invalid

use the new transport interfaces

Fixes #2.

This also requires dropping support for Go 1.8.

The session context was introduced in
https://github.com/lucas-clemente/quic-go/pull/774.

It was added in
https://github.com/libp2p/go-stream-muxer/commit/be2992bb9

Support for stream deadlines was added in
https://github.com/lucas-clemente/quic-go/pull/579.

Support for Go 1.7 was dropped for quic-go in
https://github.com/lucas-clemente/quic-go/pull/661.

The tls.Config was removed from the quic.Config in
https://github.com/lucas-clemente/quic-go/pull/713.