On 02/14/2013 08:00 PM, Stephen Farrell wrote:
>
> On 02/14/2013 06:52 PM, Leif Johansson wrote:
>> On 02/14/2013 07:42 PM, Stephen Farrell wrote:
>>> Ok, so that needs Brian's browser to know about all possible
>>> search engines Brian might use, that all of those scrape the JPF
>>> site (and not the Roman fake:-) for keys and that Brian does go
>>> to the JPF site for the first time by clicking on a search
>>> result.
>> I don't get that. Isn't it enough if Brians browser processes
>> s-link attributes as he is clicking away, populating his pinning
>> database as he goes?
> I don't know but didn't get the concept that Brian is
> populating as he goes when I looked at the description.
>
> I thought he'd only believe pins on the href he's about
> to follow when those had just been delivered direct from
> one of a browser-chosen list of sources that are
> explicitly trusted (by the browser, not Brian) for this.
I guess there could be some policy setting that allows
Brian to decide if he trusts the page to transit trust
for him or just to update the pin db for that URL.
I must say I am attracted to the notion as such because
it affords a way to tie trust with branding (which is what
social trust is mostly about anyway).
>
> But I guess it might be that if he searched for "front
> for the liberation of..." on Thursday and then on Friday
> typed in the JPF URL that could work if the browser has
> kept the info. ('course those paranoid JPF guys might
> change their key late on Thursday which'd be bad) so
> maybe not.
>
> Not sure it changes the overall effectiveness much though,
> does it?
>
> S
_______________________________________________
therightkey mailing list
therightkey@ietf.org
https://www.ietf.org/mailman/listinfo/therightkey
