I thought we had something like that already. The changes I can think of,
off the top of my head:
- New session protocol with a node PKI with MITM secure key negotiation.
Scott was going to post the specifics on this.
- New procedure for node introduction into the network instead of
inform.php. This will use a ramdom routed query and then a commit/reveal
procedure to establish an initial reference value for new nodes. The
specifics aren't quite worked out yet.
- Integration of an ARK client into the node.
- Changes to some of the application protocol:
- removal of the depth field. HopsToLive only on requests, and randomly
decremented.
- Combining the InsertRequest/DataInsert procedure into a single message
for speed and DOS security. (A pox on me for splitting it up in the
first place.)
I would mark the progress on each point, but that would be depressing...
On Fri, Dec 29, 2000 at 10:56:47AM -0600, Steven Hazel wrote:
> "Mr.Bad" <[EMAIL PROTECTED]> writes:
>
> > Also, I think Oskar and Scott need to have a powwow about
> > features. Scott seems to be totally opposed to 3 lines of
> > unnecessary code, while Oskar doesn't mind throwing in the kitchen
> > sink, as long as it's not used. B-)
>
> Speaking of which, could we get a comprehensive list of planned 0.4
> features? It would be useful to client and alternate node authors if
> we could start implementing those features before they're released in
> Fred.
>
> -S
>
> _______________________________________________
> Freenet-dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/freenet-dev
--
'DeCSS would be fine. Where is it?'
'Here,' Montag touched his head.
'Ah,' Granger smiled and nodded.
Oskar Sandberg
[EMAIL PROTECTED]
_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
