search for: zarq

...in userspace... Be afraid. Be very afraid. ;) [mod: And be aware that for demonstration purposes, the "cloaking" is not perfect in this case. The access to /proc/223 demonstrated to still work above, could also be disallowed. -- REW] .../ru ----- /* * heroin.c * * Runar Jensen <zarq@opaque.org> * * This Linux kernel module patches the getdents(), kill(), read() * and query_module() system calls to demonstrate the potential * dangers of the way modules have full access to the entire kernel. * * Once loaded, the module becomes invisible and can not be removed * with rm...

Hi tinc list members, There were some problems with Ivo's email adresses (both zarq@iname.com and zarq@spark.icicle.dhs.org) so I resent the stuff to the mailling list. ============================================= Hi Ivo, Hier is een oplossing voor een bugje in flush_queue(), en ook wat andere troepjes zoals een tincd scheduler. Dit werkt wat beter, omd...

...do with cabal. > > Bugs left: > > - don't send structs directly (you never know when gcc will rearrange > > them). Best would to sprintf() the structs and then write the string > > to the socket. That also immediately fixes the host byte order > > problem. zarq: unless we break the protocol fixing this is going to be really tough! Okay so another bug to add to the list: - key regeneration segfaults after a few times. Met vriendelijke groet, Guus Sliepen. --- TINC development list, tinc-devel@nl.linux.org Archive: http://mail.nl.linux.org/tinc-devel/

...ross it <mikef> anybody have any ideas? It's probably something with wrong settings for Virtual IP's and/or routing. Could you please send us the complete tinc.conf for both sites, and the output of "route" and "ifconfig" for both sites? Email addresses include: zarq@nl.linux.org (Timmermans, Ivo) guus@nl.linux.org (Sliepen, Guus) tinc@nl.linux.org (List, Mailing) Met vriendelijke groet, Guus Sliepen. - 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 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...

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

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

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

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

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:

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:

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 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

I've played around with the config some more after finding and reading through the mailing list archives. I think I'm being tripped up by my ipchains ruleset, so I'm going to play with it when I get home tonight and can set up a private network. If I have any further problems, I'll subscribe to, then send a message to the mailing list. Thanks for your patience and a VPN that's

root wrote: > Hi, > > is tinc a better solution for my problem described thereafter? > > I have studied your docs but did not find an answer. > > So I decided first to ask before I begin my lengthy trials. > > I your tinc should be a good solution for tunneling port 139 > (and perhaps printing) it should be included in your docs, > because would be interesting

Albert Gonzalez wrote: > I apologize any inconvenience this mail may cause to you. > If so, please, subbmit me to where I can find some advice. The proper place to ask such questions would be tinc@nl.linux.org (Cc'd). > The problem is: > > I've built a vpn using tinc, and, to my best knowledge, > I can see a ping from the other side on tap0 using tcpdump. > ( on