Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move go-libp2p-tls here #1466

Merged
merged 76 commits into from
May 3, 2022
Merged

move go-libp2p-tls here #1466

merged 76 commits into from
May 3, 2022

Conversation

marten-seemann
Copy link
Contributor

Part of #1187.

marten-seemann and others added 30 commits November 24, 2018 15:33
close the underlying connection when the context is canceled
add support for ECDSA keys
avoid using interface{} when generating certificates
remove unneeded marshaling / unmarshaling when generating cert chain
TLS 1.3 will require Go >= 1.12, so we don't need any fixes that were
specific to Go 1.10 any more.
TLS 1.3 support was recently made opt-in in Go 1.12, so we need to
explicitly enable it.
add an example (mainly for development)
Co-Authored-By: marten-seemann <martenseemann@gmail.com>
marten-seemann and others added 22 commits July 30, 2020 12:25
remove setting of the TLS 1.3 GODEBUG flag
fix: don't fail the handshake when the libp2p extension is critical
sync: update CI config files
According to RFC3280, the issuer field must not be empty.
migrate to standard Go tests, stop using Ginkgo
* use tls.Conn.HandshakeContext instead of tls.Conn.Handshake

* make sure that crypto/tls picks up the handshake ctx cancelation in tests
feat: catch panics in TLS negotiation
@marten-seemann marten-seemann mentioned this pull request Apr 27, 2022
65 tasks
Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As with the other cases, I'd consider renaming. But we can do that later.

@MarcoPolo
Copy link
Collaborator

We should retarget this PR libp2p/go-libp2p-tls#99 after this merges. Note to ourselves, we should comment on that PR after this merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants