Ok, so this media enforcer thing has churned up one issue that we
should address to lay the thing to rest, namely the danger of
identifying whether a node is caching content using a HTL of 1.  The
way to counter this is to introduce some randomness into whether a HTL
is decremented or not.  If this hasn't been done already, we should
perhaps make the change before this release 0.3.6 (which I will do
tonight PST).

Ian.

PGP signature

Reply via email to