Ian Clarke writes: > > --6TrnltStXW4iwmi0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Thu, Jul 25, 2002 at 06:43:06PM -0400, Dan Merillat wrote: > > Correct answer is to use the same primatives to digitally sign each messa= > ge so > > when someone rebroadcasts they send your signature as well. > > Perhaps the solution is to support a FCP feature which allows you to=20 > obtain a SSK signature, which you can retransmit with a message, and=20 > which can be used to verify (using another FCP command) that a message=20 > is permitted under a given SSK without actually requesting it from that=20 > SSK.
That's not a bad idea. A FCP "Sign This" and "Verify This" would be useful for a number of apps. For instance, we could wire it into fproxy and have signed (optional) Nearly Instant Messaging without the recipient having to listen on every possible channel. Along with that, an "Encrypt This" and "Decrypt this" so only the recipient can read it and you've got the basis for secure email over freenet. > A temporary solution would be to disable rebroadcasting for the moment. Well, FMB only rebroadcasts messages that came from the original source, so you don't have too much of a problem with it. Also, if someone modifies a message and you recieve it from a second (non-original) source, it detects the forgery and requests you retrieve it from the source. Turning off rebroadcasting would probably make it unusable. I'm quite often unable to retrieve the original message, but I do get them via archives or rebroadcasts. --Dan _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
