> On 6 Nov 2018, at 03:38, Michael Rogers <mich...@briarproject.org> wrote: > > One of the difficulties with this option is that under some conditions, > the controller can only schedule one alarm every 15 minutes. Traffic > from the guard would also wake the CPU, so if we could ask the guard for > regular keepalives, we might be able to promise that the CPU will wake > once every keepalive interval, unless the guard connection's lost, in > which case it will wake once every 15 minutes. But keepalives from the > guard would require a protocol change, which would take time to roll > out, and would let the guard know (if it doesn't already) that the > client's running on Android.
Tor implemented netflow padding in 0.3.1.1-alpha (May 2017): https://gitweb.torproject.org/torspec.git/tree/padding-spec.txt Connection padding may act like a keepalive, we should consider this use case as we improve our padding designs. T
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
