similar to: [Announcement] Tinc version 1.0.23 released

Hello Guus. I've reading mailing list archives threads about it at http://www.tinc-vpn.org/pipermail/tinc/2011-July/thread.html#2757 and http://rutschle.net/pipermail/sslh/2011-July/thread.html and now trying to hide tinc server behind sslh multiplexer but without luck. First of all directly it works fine. Initiator (instance of tincd with ConnectTo statement) successfully establishes

With pleasure we announce the release of tinc version 1.0.20. Here is a summary of the changes: * Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode. * Minor improvements and clarifications in the documentation. * Allow tinc to be cross-compiled with Android's NDK. * The discovered PMTU is now also applied to VLAN tagged traffic. * The LocalDiscovery option now

With pleasure we announce the release of tinc version 1.0.20. Here is a summary of the changes: * Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode. * Minor improvements and clarifications in the documentation. * Allow tinc to be cross-compiled with Android's NDK. * The discovered PMTU is now also applied to VLAN tagged traffic. * The LocalDiscovery option now

Hi all, few days ago I have installed sslh on my server and I discover that recently OpenVPN support was added. Reading the code I found that sslh use the first few bytes of the new connection to decide what kind of connection it is, than it muxes the connection on the appropriate deamon. There is a "sign" for the tinc connection?

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

With pleasure we announce the release of version 1.0.17. Here is a summary of the changes: * The DeviceType option can now be used to select dummy, raw socket, UML and VDE devices without needing to recompile tinc. * Allow multiple BindToAddress statements. * Decrement TTL value of IPv4 and IPv6 packets. * Add LocalDiscovery option allowing tinc to detect peers that are behind the

With pleasure we announce the release of version 1.0.17. Here is a summary of the changes: * The DeviceType option can now be used to select dummy, raw socket, UML and VDE devices without needing to recompile tinc. * Allow multiple BindToAddress statements. * Decrement TTL value of IPv4 and IPv6 packets. * Add LocalDiscovery option allowing tinc to detect peers that are behind the

With pleasure we announce the release of version 1.0.18. Here is a summary of the changes: * Fixed IPv6 in switch mode by turning off DecrementTTL by default. * Allow a port number to be specified in BindToAddress, which also allows tinc to listen on multiple ports. * Add support for multicast communication with UML/QEMU/KVM. This version of tinc is compatible with 1.0pre8, 1.0 and

With pleasure we announce the release of version 1.0.18. Here is a summary of the changes: * Fixed IPv6 in switch mode by turning off DecrementTTL by default. * Allow a port number to be specified in BindToAddress, which also allows tinc to listen on multiple ports. * Add support for multicast communication with UML/QEMU/KVM. This version of tinc is compatible with 1.0pre8, 1.0 and

With pleasure we announce the release of version 1.0.19. Here is a summary of the changes: * Allow :: notation in IPv6 Subnets. * Add support for systemd style socket activation. * Allow environment variables to be used for the Name option. * Add basic support for SOCKS proxies, HTTP proxies, and proxying through an external command. This version of tinc is compatible with 1.0pre8, 1.0

With pleasure we announce the release of version 1.0.19. Here is a summary of the changes: * Allow :: notation in IPv6 Subnets. * Add support for systemd style socket activation. * Allow environment variables to be used for the Name option. * Add basic support for SOCKS proxies, HTTP proxies, and proxying through an external command. This version of tinc is compatible with 1.0pre8, 1.0

Saverio, it looks I'm using tinc on OpenWRT packaged by you) Thank you for it Is something there in that task, what is harder than https://wiki.openwrt.org/doc/devel/packages ? Anyway, I want to try On Thu, Nov 3, 2016 at 5:57 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu, Nov 03, 2016 at 03:43:42PM +0100, Saverio Proto wrote: > > > I am not using OpenWrt a

Hello! I am not using OpenWrt a lot anymore, and it is becoming difficult to me to test quickly the tinc package and update OpenWrt when a new tinc release is out. does anyone wants to step in as the new package Maintainer ? thanks ! Saverio

Hello Maxim, did you send the pull request ? Please send an email to the list when you do thank you Saverio 2016-11-05 10:09 GMT+01:00 Saverio Proto <zioproto at gmail.com>: > Hello Maxim, > thanks for stepping in ! > > so, I am not even sure how it works for commit rights, because the > people I was in touch with now forked the project to LEDE. > > Also, I always

Hello, I received this pull request. https://github.com/openwrt/packages/pull/2757/files As I wrote in the comments I am not sure that is the way to go. Packaging a software for a distribution is not just about software development. There are operational issues to be addressed. A lot of people use the tinc package and they expect they configs to survive a package update. Also they expect the

I received this PR for the tinc package on OpenWrt. https://github.com/openwrt/packages/pull/7646/files Not sure if this is something that is better going upstream instead. Moreover, from a security point of view, is it okay to merge this patch ? thank you Saverio

With pleasure we announce the release of tinc versions 1.0.33. Here is a summary of the changes in tinc 1.0.33: * Allow compilation from a build directory. * Source code cleanups. * Fix some options specified on the command line not surviving a HUP signal. * Handle tun/tap device returning EPERM or EBUSY. * Disable PMTUDiscovery when TCPOnly is used. * Support the --runstatedir option of

With pleasure we announce the release of tinc versions 1.0.33. Here is a summary of the changes in tinc 1.0.33: * Allow compilation from a build directory. * Source code cleanups. * Fix some options specified on the command line not surviving a HUP signal. * Handle tun/tap device returning EPERM or EBUSY. * Disable PMTUDiscovery when TCPOnly is used. * Support the --runstatedir option of

For tinc users on OpenWRT: https://dev.openwrt.org/changeset/29137 ciao :) Saverio