GitLab

Bump github.com/onsi/gomega from 1.4.3 to 1.7.1

Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.4.3 to 1.7.1.
- [Release notes](https://github.com/onsi/gomega/releases)
- [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md)
- [Commits](https://github.com/onsi/gomega/compare/v1.4.3...v1.7.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bump github.com/onsi/ginkgo from 1.7.0 to 1.10.3

Bumps [github.com/onsi/ginkgo](https://github.com/onsi/ginkgo) from 1.7.0 to 1.10.3.
- [Release notes](https://github.com/onsi/ginkgo/releases)
- [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md)
- [Commits](https://github.com/onsi/ginkgo/compare/v1.7.0...v1.10.3)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

close the underlying connection when the handshake fails

make the error check for not receiving a public key more explicit

Fix: Connection Closed after handshake

The context-cancelled watchdog goroutine may start running way after the
handshake has finished and the associated context has been cancelled (by the
executeDial() function in go-libp2p-swarm usuaully).

This results in the connection being closed right after being stablished.

Readme: link to the libp2p-core docs

Current link points to a deprecated repository

expose the function to derive the peer's public key from the cert chain

set an ALPN value in the tls.Config

fix CI after deprecating gx

replace gx instructions with note about gomod

implement the new handshake

When resuming a session using session tickets, no certificate chain is
presented, and the callbacks needed to verify the peer identity would
not be called.

use a prefix when signing the public key

use ChaCha if one of the peers doesn't have AES hardware support

Co-Authored-By: marten-seemann <martenseemann@gmail.com>

improve peer verification

add an example (mainly for development)