similar to: tinc_for_tunneling_port_139

Hi all, I just uploaded tinc 1.0pre1 to the server. I included and rpm, which has been made possible by the work of Lubom?r Bulej and Mads Kiilerich. Please test this version, so that any bugs left can be squished before 1.0 gets final. Also be aware that this version includes a new version of the protocol, and is thus NOT compatible with the protocol that 0.3 uses. Thanks for flying tinc.

Hi all, I just uploaded tinc 1.0pre1 to the server. I included and rpm, which has been made possible by the work of Lubom?r Bulej and Mads Kiilerich. Please test this version, so that any bugs left can be squished before 1.0 gets final. Also be aware that this version includes a new version of the protocol, and is thus NOT compatible with the protocol that 0.3 uses. Thanks for flying tinc.

Sending your passphrase encrypted is all fine, but tinc sends the key with which it was encrypted about a second later... Anyone being able to intercept these two requests is authorized on the VPN. We need asymmetric authentication _now_. -- Ivo Timmermans -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size:

On Mon Apr 24 2000, Mike MacNeill <mikem@accesscomm.ca> wrote: > I downloaded the cabal version as well and I seem to have discovered a > problem. > > Whenever the regenerate key goes off it manages to eat memory somewhere. > > I set the regen time from 90 minutes to basically all day. > > Have you tried running this under efence? efence didn't show anything

Hi all, It seemed like a good idea to post updates here every now and then about the progress of the development of tinc. Right now, we're mainly hunting bugs. While doing this, we stumbled upon some shortcomings of the meta protocol, possibly dangerous. So Guus and I are now working on a new protocol, which will be incompatible with the standing 0.3 protocol (version 4). Whether or not

Mads Kiilerich wrote: > Right now at this moment we have reached a level where I have > no further patches! :-) great! :) Guus is now doing a last protocol change, after that is tested, I'm going to make 1.0pre1 official, including an rpm (deb will have to wait due to some difficulties). > I don't think a configuration program will be needed. VPN is not > for

Viraj Alankar wrote: > I've successfully setup tinc-1.0pre1 but I notice on my firewall > that it requires fragmented UDP packets to be let in in order to work > properly. Is there any way to avoid this? [ This is true. We don't inherit the DF (Don't Fragment) flag onto the UDP data, so path MTU discovery doesn't work. We have to fix this. ] Yes, you can avoid this

Hi all, 1.0pre2 is there. [ I just noticed the included ChangeLog is empty -- oh well. ] * This version has been internationalized; and a Dutch translation has been included. * Two configuration variables have been added: * VpnMask - the IP network mask for the entire VPN, not just our subnet (as given by MyVirtualIP). The Redhat and Debian packages use this variable in their

Hi all, 1.0pre2 is there. [ I just noticed the included ChangeLog is empty -- oh well. ] * This version has been internationalized; and a Dutch translation has been included. * Two configuration variables have been added: * VpnMask - the IP network mask for the entire VPN, not just our subnet (as given by MyVirtualIP). The Redhat and Debian packages use this variable in their

Matias Carrasco wrote: > I traslated a part of the manual of tinc to Spanish to give a class of Virtual Private Network, upon ending the traslated nearly all the document was translated, was asking me if you are interested in the manual of tinc translated to the Spanish, send an email to mdcarrasco@mendoza.com.ar or to mdcarrasco@infovia.com.ar. > Yes! :) This is a Good Thing (tm). Please

After many months of work, it's finally there: tinc 1.0pre3. Here is a summary of the changes: * The protocol has been redesigned, and although some details are still under discussion, this is secure. Care has been taken to resist most, if not all, attacks. * Unfortunately this protocol is not compatible with earlier versions, nor are earlier versions compatible with this version.

After many months of work, it's finally there: tinc 1.0pre3. Here is a summary of the changes: * The protocol has been redesigned, and although some details are still under discussion, this is secure. Care has been taken to resist most, if not all, attacks. * Unfortunately this protocol is not compatible with earlier versions, nor are earlier versions compatible with this version.

Hi all, There is a new list for all the CVS messages, so this list doesn't get flooded like it did today. And I didn't even do anything big :) For those of you who still want to get these messages, you can subscribe to tinc-cvs@nl.linux.org, send a message to majordomo@nl.linux.org with `subscribe tinc-cvs' in the body of the message. -- Ivo Timmermans You are just jealous

Hi, here's a small list of things that need to be done, and the version when it should be ready. smartcard support 1.1 LDAP support 1.1 public/private keys for authentication 1.1 don't store passphrases in files that are called after IP addresses 1.0 use names to identify

Although we (the authors of tinc) have done our best to make tinc as secure as possible, an unfortunate combination of encryption and key exchange techniques has created a hole in at least all versions of tinc >= 0.3, including the current CVS version. Exploit: If somebody can intercept the meta protocol to a host that is running a tinc daemon, it is possible to decrypt the passphrase, which

Although we (the authors of tinc) have done our best to make tinc as secure as possible, an unfortunate combination of encryption and key exchange techniques has created a hole in at least all versions of tinc >= 0.3, including the current CVS version. Exploit: If somebody can intercept the meta protocol to a host that is running a tinc daemon, it is possible to decrypt the passphrase, which

Hello Mike, <mikef> hi. I installed tinc.rpm to two servers (both of which are acting as firewalls) <mikef> they can connect to each other successfully according to /var/log/messages, but I can't get traffic to move across it <mikef> anybody have any ideas? It's probably something with wrong settings for Virtual IP's and/or routing. Could you please

Hi Ivo, --On Freitag, 23. Juni 2000 01:15 +0200 Ivo Timmermans <zarq@icicle.yi.org> wrote: > I'm not sure I fully understand your patch. This is not so important since I'm trying to get 1.0pre2 running. Although I had no luck so far, I'll point out what's going wrong at the end of this mail. > For instance, you force a > key exchange when the connection is made,

Attached you'll find the spanish messages for tinc (up-to-date CVS version). I'm eager to try tinc 1.0! :-) Thanks, -- Enrique Zanardi ezanardi@id-agora.com -------------- next part -------------- A non-text attachment was scrubbed... Name: es.po.gz Type: application/octet-stream Size: 5338 bytes Desc: not available Url :

Dear, I need to use VPN on Linux, slackware 7 kernel 2.2.13 and Redhat 6.2 kernel 2.2.16. And I found Tinc. Before I decide to install Tinc, could you answer my questions? 1. Can Tinc work on those platforms, slackware and redhat? 2. Can Tinc be installed on both sides, VPN server and VPN client? or only use for server. 3. I need to modify some code. If I have some