On Thu, Oct 04, 2001 at 12:17:42AM +0200, Oskar Sandberg wrote: > > >From their statements on the p2p-hackers list, it is my understanding > that the Bitzi authors plan to support multiple records for any piece of > data, so that beyond there own "SHA1 hash" format, they would also be > able to provide Freenet keys and other forms of UIDs. They seemed > unconcerned by and understanding of the proliferation of different > identifiers. > > Because the data is encrypted, the only way to provide lookups of data > on Freenet using any plaintext hash as the key would be to use the hash > as a insecure KSK. This would mean that you could not verify the data > until you had downloaded and decrypted all of it, and that the network > would not be able react to the bad data. Why can't you use a CHK? You might need several different CHKs, one for 0.3, one for 0.4 as a single file, one as a splitfile...? > > On Wed, Oct 03, 2001 at 02:30:48PM -0700, Patrick Oscar Boykin wrote: > > This is shame that there can't be some bridging. See: > > http://bitzi.com/developer/code > > > > I don't know if this has been discussed before, but bitzi provides > > metadata lookup on files, including SHA1 hash. > > > > It would be really nice to be able to use bitzi to search for files, and > > then locate them on freenet. > > > > There are already over 1 million files indexed on bitzi. > > > > From what I have seen here, interoperability in freenet has always been > > a major concern. Why not with this issue? > > > > Okay, sorry, that last bit was a joke. Seriously, I am interested in > > what people think about this approach for searching. I know there is > > freegle, but since that is freenet specific, it seems like something > > like bitzi (which will be useful also to the gnutella community who are > > working on support for it) could be great. > > > > Oscar (not Oskar). > > > > On Tue, Oct 02, 2001 at 01:09:18PM +0200, Oskar Sandberg wrote: > > > No, it's not that simple. All SHA1s are not equal. For two identical > > > pieces of data two end up with the same SHA1 based keys, then the entire > > > format for the data must be exactly the same - all splitting, padding, > > > encrypting, formatting, error checking, metadata etc etc must be > > > strictly defined. Freenet CHKs will not match with SHA1 indentifiers > > > generated by any other program. > > > > -- > > boykin at pobox.com http://pobox.com/~boykin ICQ: 5118680 > > Key fingerprint = 159A FA02 DF12 E72F B68F 5B2D C368 3BCA 36D7 CF28 > > > > -- > Though here at journey's end I lie > In darkness buried deep, above all shadows rides the Sun > beyond all towers strong and high, and the Stars forever dwell: > beyond all mountains steep, I will not say the Day is done, > nor bid the Stars farewell. > (JRRT) > > Oskar Sandberg > oskar at freenetproject.org > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://lists.freenetproject.org/mailman/listinfo/devl
-- The road to Tycho is paved with good intentions _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
