Freenet 0.7 build 1021 is now available. Please upgrade. The auto-update
system should pick this build up in coming hours, if not, please tell
me.

1021 has rather more changes than most recent freenet builds, so there
may be some rough edges. Nevertheless it will be mandatory in 1 month's
time, and many of the changes are really interesting. Highlights:
- New (long overdue) link encryption setup mechanism which is immune to
  Man-in-the-Middle and impersonation attacks.
- Significant work on pre-emptive request rejection and timeouts: No
  hard limit on # requests, but limit # threads, memory, ensure that if
  all running requests succeed we won't be forced into timeouts, and
  increase the bwlimitDelay thresholds (they were too restrictive given
  the above).
- Use significantly fewer threads, and don't leak the memory used by old
  queued requests.
- Add FUQID-like code to try requesting more blocks from queued requests
  which we have recently had successes on.
- Some work on local security: The node is now immune to symlink attacks
  on downloads to disk, there are optional settings for where downloads
  are allowed to and uploads are allowed from, and it is possible to set
  a list of IPs which are allowed full access to the node (full access
  includes e.g. reconfiguring the above limits, restarting the node;
  limited access at the moment still includes downloading within those
  dirs).
- Lots of refactoring, new node.load config subsection, will eventually
  include everything to do with stats and limiting.
- Fix a wierd bug with hash verification.
- Do the hard part of starting a splitfile request on a separate thread.
  Speeds up startup significantly when you have lots of queued requests.
- Lots of other improvements.

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]

Reply via email to