similar to: tinc 1.0pre1

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

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

Hello, regarding the debian init.d script, a perl rewrite of the shell script by Lubomir. The debian-specific (?) start-stop-daemon is used. It uses its own pid-file handling instead of the one build into tinc. Bug or feature? "old" ifconfig and route commands are used instead of iproute commands. Bug or feature? regards, -- Mads Kiilerich Sys.Adm. Cand.Polyt

THis is the modified script that came with tinc 1.0pre2, and it now uses ifconfig in stead of ip-route. I changed the syntax to be correct (may already have been fixedin a newer version), it now checks whether or not there is a '/dev/tapX' or a '/dev/netlink/tapX' and it checks if there is a module or not. I also added the force_connect and the reload options. Force_connect send

Hello, I just want to ask if it has been considered to use OpenSSL for the encryption stuff. I guess they've spent quite some time on the subject and have the cipher routines both debugged and optimized. I know that some of the current cipher code was taken from SSLeay but since OpenSSL is de facto SSLeay successor, it might give tinc more flexibility and allow the user to choose

Hello Mads, In case you never saw any mail from me, I'm tinc's co-author. It would be helpful if you'd subscribe to the tinc developpers mailing list. It's not high volume, but it eases communication. There's a problem with tinc's boot scripts (at least the debian one, but that's fixed now). The netmask of the tap devices should be larger than the one specified with

Quoting Mads Kiilerich <Mads@Kiilerich.com>: > AARGH, > > Ivo, I hope I remember the file this time... ;) Lubomir, thanks for the comments/changes. I'm still busy writing: 1) a debian version of the init script that tries to do the same as the redhat one you and Mads have been working on, and a 2) perl script to create configuration files by asking the user questions. As

Hello, trying to start tinc I get the following at the client: Apr 17 16:34:50 otto tincd[10238]: tincd 0.3.3 starting, debug level 1. Apr 17 16:34:50 otto tincd[10238]: Generating 128 bits keys. Apr 17 16:34:50 otto tincd[10238]: Ready: listening on port 655. Apr 17 16:34:50 otto tincd[10238]: Connected to xxx Apr 17 16:34:50 otto tincd[10238]: Memory exhausted; exiting. - on a machine with 80

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

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:

Hi. configure fails because on my machine, mpz_powm is a macro in gmp.h, so the check doesn't work... Marc - Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://ftp.nl.linux.org/pub/linux/tinc/

Hi, Could somebody points me to some .ogg test files in mono or with more than 2 channels? I am also looking for info on how channels are positionned so than I can remap them for 2 channels only environments. Cheers, André Timmermans --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

Hi Tinc Mailing-Group, Having set up the kernel correctly, and got tinc running successfully, I am now trying to get two VPNs running at once. Hence I need to have two ethertap devices ( /dev/tap0 and /dev/tap1 ). The first tap0 device was created thus: mknod -m 600 /dev/tap0 c 36 16 chown 0.0 /dev/tap0 The second tap1 device was created too: mknod -m 600 /dev/tap1 c 36 17 chown 0.0 /dev/tap1

Hi all, I have used tinc to get a vpn up and running I am almost there but have some problems at the end. My config: Building A Network 10.0.0.0 netmask 255.255.255.0 gateway 10.0.0.30 tap0 device on gateway machine 10.0.0.31 Building B Network 10.2.0.0 netmask 255.255.255.0 gateway 10.2.0.154 tap0 device on gateway machine 10.2.0.155 from network A I can ping 10.2.0.154 but not the other

It seems to me that in this version of the function using float p=.7071067812f; float q=.7071067812f; will just leads after applying all the products and squaring to p and q having a common factor 0.5 which can be extracted from the formulaes. So I propose to replace: float p=.7071067812f; float q=.7071067812f; float w=vorbis_coslook(wdel*k); float *ftmp=lsp; int

Hello all, I've been playing with tinc to setup a wan between two offices of the company that I work for. I'm partially there but having a slight problem. tinc comes up between the 2 machines (both 2.2.14 debian woody machines), and I can ping from the vpn machine at office a, and get a response from office b. However, if I ping any other machine across the wan I can't get a

Chih-Wei Huang wrote: > Hi, > I just install tinc 1.0pre3 by rpm. > When I tried to start tincd by > /etc/rc.d/init.d/tinc start > It complained > **tinc: file with list of VPNs to start (/etc/tinc/nets.boot) not found! > However, I don't know what /etc/tinc/nets.boot is. > It was not mentioned in the manual page. > Could you explain what's the file > or give

And, here''s a fix. -----Original Message----- From: David Zhao <dzhao@LURK.KELLOGG.NWU.EDU> To: BUGTRAQ@NETSPACE.ORG <BUGTRAQ@NETSPACE.ORG> Date: Sunday, May 17, 1998 3:00 PM Subject: simple kde exploit fix >in kdebase/kscreensaver/kscreensave.cpp: > >change: >line 18: strcpy( buffer, getenv("HOME") ); > to >