radakayot
in my implementation i'm converting tcp/udp packets to i2p messages. i'm creating different local destination for each remote destination that i wanted to communicate. are there any security implications of using same local destination for an extended period of time?
orignal
lol. you approach means zero anonimity
orignal
you need to add tunnels layers
orignal
futhermore ideally each transport link should maintain few tunnels
orignal
otherwise you traffic pattern could be recognized easily by packets sizes
radakayot
sure, i'm using outbound tunnels to send data.
radakayot
but how long should i keep same leaseset for each destination? until the tunnel expires?
dr|z3d
10m with 1m grace period for existing connections is the current standard.
radakayot
thank you dr|z3d.
orignal
you should keep updating and destributing
zzz
found and resurrecting my 5 year old ratchet unit test to debug a PQ handshake, because it didn't magically work first time on live net ((
eyedeekay
reseed-tools will get an 0.3.4 release today, nothing too special in it that wasn't on 0.3.3 but it will be the first CI/container build and some of the initscripts/systemd unit files have been revised and improved
zzz
got msg 1 working in unit test
eyedeekay
excellent
zzz
it helps being our 5th noise protocol in 10 years, relatively straigthforward now that I have my head in it
zzz
unit test is key, I'm fixing a bug every 10 minutes
zzz
me with my big mouth, I'm stuck again, on msg 2, giving up for today