We could: - Make ClientPut of a file insert a one-file manifest by default including the given filename (rather than just the file), if it's told to insert a CHK@ - Enforce the number of metastrings. I.e. if a file is inserted as CHK at blah,blah,blah/ it can no longer be accessed as CHK at blah,blah,blah/something-i-just-made-up.jpeg
Advantages: - Keys cannot be modified; there is a definitive CHK, and if you change it it doesn't work - Therefore CHK at .../chicken-porn.jpeg cannot be renamed maliciously to CHK at .../free-music.mp3 - Makes caching schemes easier; two keys are equal only if they are equal, rather than having to progressively delete meta-strings from the end - Fairly easy to implement Disadvantages: - Phase 2 is disruptive Any objections? -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20060818/800c4b99/attachment.pgp>
