search for: err404

...e spoofed subnets, and apeliote will become unreachable while miou intercepts all communications. This is the primary reason why it's a very bad idea to let untrusted nodes join a tinc network. The only way to defend against this type of attack is to use StrictSubnets. On 4 May 2015 at 21:13, err404 <err404 at free.fr> wrote: > On 05/04/2015 10:01 PM, Etienne Dechamps wrote: >> On 4 May 2015 at 20:53, Anne-Gwenn Kettunen <anwen at asphodelium.eu> wrote: >>> We started to take a look about that, and apparently, it seems that the IP >>> in the public key is...

On 4 May 2015 at 20:53, Anne-Gwenn Kettunen <anwen at asphodelium.eu> wrote: > We started to take a look about that, and apparently, it seems that the IP > in the public key is taken into account when a client connects to a gateway. > Spoofing at that level doesn't seem easy, because the IP address seems to be > part of the authentication process. I'm having trouble

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello I have an issue with tinc 1.0.34 on Debian, but same tinc version in OpenWRT work well. I have a tinc with config file like this: /etc/tinc/err404/hosts/lime-up -rwxr-x--- 1 root root but it's not **executed every time** when tinc become up (yes I can use tinc-up directly, and tinc-up work well) uname: Linux lime2 4.14.70-sunxi #265 SMP armv7l GNU/Linux (lime2 is a small board from Olimex: https://www.olimex.com/Products/OLinuXino/A20/...

On 05/04/2015 10:01 PM, Etienne Dechamps wrote: > On 4 May 2015 at 20:53, Anne-Gwenn Kettunen <anwen at asphodelium.eu> wrote: >> We started to take a look about that, and apparently, it seems that the IP >> in the public key is taken into account when a client connects to a gateway. >> Spoofing at that level doesn't seem easy, because the IP address seems to be