Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I2P/Tor White Noise #5793
This adds the "white noise" proposed in part 2 of my CCS. This also moves
Completing Dandelion++ will now require:
The last two should be vastly easier to implement after this patch. The stem portion in particular is basically implemented and unit tested - only plumbing between parts is now needed. Anyone wishing to pick this up, see
The white noise is ignored by the hidden service, do you mean refuse inbound connections that are sending white noise? Not with this patch, but is something I have thought about. Runtime or compile time options can be added for this purpose, but this could make it more difficult on outbound users of the feature.
Probably not. The ISP can monitor the Tor cell count being sent (or the I2P equivalent). In many (all?) cases the shell script would have to stop sending at exactly the moment
The question on the ignoring of white noise was a misunderstanding on my part, but thanks for explaining.
On the shell scripting, the way I understand white noise used here is that it only has to obfuscate outgoing transactions made by the user, everything else can be analysed and need not be masked, like block sync, peer table, etc, those won't affect privacy.
But txs are small and rare, so a stream of random packet, the length of which follows the distribution of other txs is enough to mask it.
It can be disabled on the sender side,
A CLI method for enabling/disabling the noise on a running
I'm not sure what you are saying here. I think you might be referring to the padding feature which pads transactions to the next 1024 byte boundary to make bandwidth analysis harder. If the noise feature is disabled, the padding feature will be enabled (see my own code comment/review). Is that what you mean?
Or do you mean just pumping in noise when you are about to send? See reply above if thats what you meant.