>> That is definitely a good approach. But maybe there is research to be
>> done here as well. Just a rough (and in part research) idea that I had
>> in mind while asking you the question above: What about if we first
>> started looking at different services offered in the web whether they
>> can b
> I'm confused now. You're basically just talking about cookies, cache,
> and other stored identifiers at this point, right?
Yes.
> Single-site linkability due to information the user has provided to
> the website is outside of Tor's threat model. That is what https is
> for (and also why we ship
Thus spake Georg Koppen (g.kop...@jondos.de):
> > Hence, I tend to make decisions in favor of the usability direction
> > over minor details, especially ones that don't really prevent bad
> > actors/adversaries from accomplishing their goals.
>
> That is definitely a good approach. But maybe ther
Thus spake Georg Koppen (g.kop...@jondos.de):
> > However, when performed by the exits, this linkability is a real
> > concern. Let's think about that. That sounds more like our
> > responsibility than the browser makers. Now I think I see what Georg
> > was getting at. We didn't mention this beca
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===7169121415546917615==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="enig3F72C2734FABE1CB4A827A42"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===2411481729548231614==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="enigC109D701B963D257C02E88A3"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===7169121415546917615==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="enig3F72C2734FABE1CB4A827A42"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===2411481729548231614==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="enigC109D701B963D257C02E88A3"
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
