jeff
jeff
Making more than 1 destination could spread the attack surface out AND increase network load. I see very little reason for it but I digress. I will release the next...
i2p.socket is a simple implementation, the only changes required (ideally) is import socket to from i2p import socket
i2pd's sam code is still a bit crashy, idk how well it'll work, otherwise i2pd should be stable by now. another alternative is i2pcontrol and socks5 but that may require...
@DaniellMesquita that's actually not enough to hire a developer.
i happen to run an opentracker on i2p as well, http://uajd4nctepxpac4c4bdyrdw7qvja2a5u3x25otfhkptcjgd53ioq.b32.i2p/a
once ElGamal is removed fully it will use less CPU there so in the future it MAY be tolerable.
something to think about: if a client tunnel reuses tunnel encryption keys but uses different signing keys is there really much of an anonymity boost?
working on it over in my branch at https://github.com/majestrate/i2pd/tree/i2cp-session-reconfig
yeah LogPrint's logger starts after the pidfile is initialized for some reason. On Sat, Mar 31, 2018 at 10:05:15AM +0000, LLE8 wrote: > It seems LogPrint() in UnixDaemon.cpp sometimes doesn't...
does not seem to be implemented fully yet, but okay. On Fri, Jul 29, 2016 at 11:53 AM, orignal [email protected] wrote: > There is local.csv in ~/addressbook implementing similar thing...