So it's an advanced version of Justin Frankel's WASTE. It is link-level encrypted, not end-to-end encrypted, so the data is open to anyone who's on the network and has it routed through them.
It doesn't do what I want it to. However, WASTE's code is so FUBAR that it's a wonder it works at all. (seriously. Hard-coded values in many places, bitflags written in decimal, it's written in C++ and uses malloc() in one of its main classes -- and then provides the pointer to the caller directly?)
Haven't seen WASTE, nor looked into GNUnet's code (yet). But it's clear that the files being shared are stored in their encrypted form (that's what provides deniability), and only decrypted by the client. As in Freenet and DDSS (which I've been working on and hope to release pretty soon), it looks as though a file in GNUnet has two identifiers: a secret one from which a symmetric key is derived, and a public one that's used for retrieval.
There's a link-level protocol as well, but I don't think it reveals anything about file content (i.e. it deals in public identifiers, not secret ones). I could be wrong about that, but I don't think so.
no subject
Date: 2005-12-03 03:32 pm (UTC)It doesn't do what I want it to. However, WASTE's code is so FUBAR that it's a wonder it works at all. (seriously. Hard-coded values in many places, bitflags written in decimal, it's written in C++ and uses malloc() in one of its main classes -- and then provides the pointer to the caller directly?)
Guh.
no subject
Date: 2005-12-03 05:05 pm (UTC)There's a link-level protocol as well, but I don't think it reveals anything about file content (i.e. it deals in public identifiers, not secret ones). I could be wrong about that, but I don't think so.