4 ms·
Aren't there concerns around the encryption used by Tinc? (https://www.tinc-vpn.org/documentation/Security.html#Security https://www.tinc-vpn.org/documentation/
by mgbmtl 3y ago
Aren't there concerns around the encryption used by Tinc? (https://www.tinc-vpn.org/documentation/Security.html#Security https://www.tinc-vpn.org/documentation/Security.html#Securit...)
It's probably fine for personal projects though, and indeed simple and very flexible (maybe too much), well suited for connecting IoT devices.
- alyandon 3y agoSee https://tinc-vpn.org/documentation-1.1/Simple-Peer_002dto_002dPeer-Security.html https://tinc-vpn.org/documentation-1.1/Simple-Peer_002dto_00... if you are using 1.1.
- yjftsjthsd-h 3y agoThat's exactly why I ended up not using tinc, in spite of really liking everything else about it:\ It might well be fine, but there seemed to be some doubt about the crypto, AFAIK it's never been properly audited, and I'm not personally qualified to asses its security properties. In contrast, wireguard is harder to set up and use, and has fewer features (intentionally), but it was specifically designed to use the best crypto primitives available and it's had a lot more eyes on it.
- scottlamb 3y agoYes. The version 1.0 protocol is bad. [1] Don't use it. Every time tinc comes up I'm annoyed that 1.1 (which supports an improved protocol iirc and according to the doc you linked; it also has some quality-of-life improvements I put work into) hasn't been officially released, 15 years later. [1] https://www.tinc-vpn.org/pipermail/tinc-devel/2006-January/000277.html https://www.tinc-vpn.org/pipermail/tinc-devel/2006-January/0...