[tor-dev] Interoperation with libp2p

Ismail Khoffi ismail.khoffi at gmail.com
Wed Dec 8 01:49:41 UTC 2021

FWIW, I don't think libp2p supports SECIO anymore. In fact the (go)
repository has been archived: https://github.com/libp2p/go-libp2p-secio and
there is no trace of SECIO in the current (go) implementation of libp2p.

On Tue, 7 Dec 2021 at 19:33, Jeff Burdges <burdges at gnunet.org> wrote:

> > On 7 Dec 2021, at 19:26, Jeff Burdges <burdges at gnunet.org> wrote:
> > I advise against allowing any libp2p cruft into tor itself though.
> Among the many reasons. I’d expect libp2p to be a nightmare of downgrade
> attacks, given the amount of badly rolled stuff they must still support,
> like their dangerous key exchange SECIO built on the legacy curve sep256k1,
> but it’ll go deep than that.
> Jeff
> _______________________________________________
> tor-dev mailing list
> tor-dev at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20211208/7fd3b27e/attachment.htm>

More information about the tor-dev mailing list