[sent once to tahoe-dev, now copying to cryptography too, sorry for the
duplicate]
At lunch yesterday, Nathan mentioned that he is interested in seeing how
Tahoe's ideas and techniques could trickle outwards and influence the
design of other security systems. And I was complaining about how the
F
Michael Walsh wrote:
> - Adding a HTTP header with this data but requires something like a
> server module or output script. It also doesn't ugly up the URL (but
> then again, we have url shortner services for manual typing).
Ah, but see, that loses the security. If the URL doesn't contain the
r
James A. Donald wrote:
> Nicolas Williams wrote:
> > > One possible problem: streaming [real-time] content.
>
> Brian Warner wrote:
> > Yeah, that's a very different problem space. You need
> > the low-alacrity stuff from Tahoe, but also you don't
Zooko Wilcox-O'Hearn wrote:
> began with him mentioning a specific use case that he cares about and
> sees how to improve: authentication of Mozilla plugins.
To be specific, the itch that I was looking to scratch was the
authentication of Firefox updates. In some slides from the last
BlackHat, I w
