tinc

The project has its own git repositories available via https://www.tinc-vpn.org/git/, and a copy on GitHub which is always kept in sync: https://github.com/gsliepen/tinc/

SIgned git tags are used.

A NEWS file is provided with a human-readable summary of end-user visible changes: https://www.tinc-vpn.org/git/browse?p=tinc;a=blob;f=NEWS;hb=HEAD. Furthermore, a CHANGELOG file is provided with a summary of the git commits leading up to each release in the release tarballs.

Fixed vulnerabilites are mentioned in the NEWS file, along with their CVE number.

Users can submit bugs either via the mailing list or via (encrypted) private email: https://www.tinc-vpn.org/contact/. Furthermore, bugs submitted via the GitHub issue tracker are also accepted: https://github.com/gsliepen/tinc/issues

Issues are tracked via GitHub.

Reports submitted via the mailing list are available at https://www.tinc-vpn.org/mail/, those submitted via GitHub at https://github.com/gsliepen/tinc/issues

https://www.tinc-vpn.org/security/ and https://www.tinc-vpn.org/contact/

The contact information mentions that private, PGP-encrypted emails can be sent to the main author: https://www.tinc-vpn.org/contact/

No such vulnerabilities have been received in the last 6 months, but last time a vulnerability was reported the fix was coordinated and uploaded within 14 days.

The autoconf system is used.

A test suite is available since version 1.1pre.

The test suite is made using the standard autoconf testing harness.

Commits to GitHub trigger a continuous integration pipeline that compiles tinc for a variety of platforms, runs the test suite included in the source code, and runs static analysis on the source code.

By default, -Wall, some extra warning flags and code hardening flags are enabled by default if supported by the compiler.

The project compiles cleanly on most platforms with -Wall enabled. The continuous integration pipeline runs clang-tidy and any warnings are reported as errors.

-Wall and a number of other warning options are enabled by default if the compiler supports it.

The project has explicitly chosen not to use standard cryptographic protocols like TLS or SSH, because they do not fulfill the needs of the project (in particular, peer-to-peer mesh networking via both TCP and UDP). Therefore, it is implementing its own.

For version 1.0.x, by default it uses 128 bit symmetric keys and 2048 bit RSA keys. For version 1.1.x, it uses 256 bit symmetric keys and 255 bit elliptic curve keys.

Since 1.0.30, SHA-1 is no longer a dependency, and SHA-256 is used by default.

Version 1.1 implements PFS.

The code is checked before each release with cppcheck, Valgrind, and the Clang static analyzer. All errors and warnings (except for false positives) are fixed.

Address, thread and undefined behavior sanitizers are enabled while running the test suite in the continuous integration pipeline.