similar to: [CVS] humbolt:/tinc/po es.po

Guus Sliepen wrote: > - Added TCP_NODELAY and IPTOS_LOWDELAY options for meta sockets. Maybe it's better to make these optional? -- Ivo Timmermans --- TINC development list, tinc-devel@nl.linux.org Archive: http://mail.nl.linux.org/tinc-devel/

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

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:

> - Indirectdata finally REALLY REALLY works now! > - More precise debug messages Hmmm ... I can't prove that using the CVS code I checked out this morning. Everything works like yesterday: I can ping the peer but I canot go beyond: *** SERVER *** Jun 27 09:04:56 lemon tinc.9[10186]: tincd 1.0pre3 (Jun 27 2000 08:53:56) startin g, debug level 4 Jun 27 09:04:56 lemon tinc.9[10186]:

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

Hi ! I want to setup tinc 1.0 pre4 with kernel 2.4.5 I didn't find information about settings of tun/tap device I did in kernel - [*] Prompt for development and/or incomplete code/drivers Network device support <M> Universal TUN/TAP device driver support in /etc/modules.conf - alias char-major-10-200 tun mknod -m 600 /dev/tun c 10 200 chown 0.0 /dev/tun In mailing list archive I

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

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

Can anyone tell me what the absolute minimally permissive ipchains rule would be to allow tinc to operate correctly between two hosts. If we were to presume each tinc host had a default-deny policy, what ipchains command(s) would allow tinc to do its thing? I've scanned the docs on the tinc site and not found the answer- sorry if I'm blind or dumb. Thanks, Patrick - Tinc:

Update of /home/CVS/tinc/cipher/blowfish In directory humbolt:/tmp/cvs-serv2778/cipher/blowfish Modified Files: Makefile.am Makefile.in Log Message: Include system.h and cipher/hmac/hmac.h in the distribution; the blowfish cipher is now in PKGDIR/libcipher_blowfish.so.0. - Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site:

Update of /home/CVS/tinc/cipher In directory humbolt:/tmp/cvs-serv32617/cipher Modified Files: Makefile.in Log Message: - 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/

Update of /home/CVS/tinc/cipher/hmac In directory humbolt:/tmp/cvs-serv2778/cipher/hmac Modified Files: Makefile.am Makefile.in Log Message: Include system.h and cipher/hmac/hmac.h in the distribution; the blowfish cipher is now in PKGDIR/libcipher_blowfish.so.0. - Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site:

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.

Hi, I'm trying to set-up a VPN using Tinc 1.0pre3. When I start tincd I get the following in /var/log/messages. On the machine that listens for incomming connections: > Mar 16 17:23:24 vpn tinc[1168]: tincd 1.0pre3 starting > Mar 16 17:23:24 vpn tinc[1168]: Ready: listening on port 655 On the machine making the connection: > Mar 16 17:16:51 mail tinc[802]: tincd 1.0pre3 starting

I gave tinc1.0pre3 a test after the modifications you have done today. It insists that it is still 1.0pre2 but this is due to the fact the you used "1" as tag for configure.in rather than "CABAL". Anyway - results were not much more successful than yesterday: *** SERVER side log file from startup until sone seconds after connection was established *** Jun 25 21:14:30 lemon

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

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

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,