On Mon, Dec 25, 2000 at 11:21:44PM -0600, Mark J. Roberts wrote:
> On Mon, 25 Dec 2000, Brandon wrote:
>
> > Last time we talked about this, my solution was to create a new
> > psuedo-keytype. With a new keytype you can disambiguate between mapped and
> > non-mapped keys and you can store information about the mapfile in the key
> > without limiting what normal keys can look like. What do you think of this
> > idea? I didn't think all that much about it so it may have some problems.
>
> That was my original proposal. Break the key into two parts: the location
> of the map file, and the filename to look up in the map file. I used a
> colon. For example,
>
> freenet:KSK@blah:/index.html
>
> where freenet:KSK@blah is the mapfile and /index.html is the filename. The
> slash after the colon is superfluous, but it satisfies the browser.
>
> I'll check this in when I'm done in a few hours, if you'd like.
No. Overloading the key is bad. Create a new client-side keytype (SSKs
aren't real keytypes, their client-side specialized SVKs, same with
KSK). Create a new one, MSK (Mapped Subspace Key), with the right fields:
freenet:MSK@[subspace pubkey]/[mapkey]/[document name]
Mandate that mapkey never contain a slash and you've got it.
Scott
PGP signature