Freenet 0.7 build 1225 is now available (1224 originally, 1225 and 1226 fix regressions, sorry). Many changes, the most important ones being: - Finally fix the attack identified by The Register *four years* ago, by not caching data requested either locally or nearby. This is also necessary in preparation for Bloom filter sharing. This had a number of knock-on effects including changes to HTL and new caches to minimise performance losses. - Two new stores, the client cache and the slashdot cache. The client cache stores mostly freesites visited through fproxy, and persists but can be encrypted. The slashdot cache stores anything that doesn't go into the other caches, but only for 30 minutes. - Encrypt the client cache and downloads/uploads database (node.db4o), according to the physical security level. - Physical security levels now: LOW (don't encrypt anything), NORMAL (encrypt and keep the keys in master.keys), HIGH (need a password to unlock master keys), or MAXIMUM (no persistence). - Fix the panic button, this now works. - Set the datastore initially to a 10MB RAM-only store, set it to salted-hash in the post-install wizard when the size is chosen, automatically migrate the data. Avoids a lot of unnecessary disk accesses on new installs. - Support defragmenting node.db4o. There are two config settings, the first is whether to defrag on startup, the second is whether to reset the first setting. Both are true by default. - Aggregate download notifications on the home page. This is the tip of the iceberg of ljb's changes to user-alerts, introducing events... - Changes to ULPRs behaviour. ULPRs are a mechanism whereby a node can remember recent requests and if it finds the data nodes have been looking for later on, it can forward it to those nodes originally looking for it. This helps to improve performance of FMS, Frost, etc. Some security issues have been fixed with ULPRs, which will now generally respond faster, also the slashdot cache was needed to make ULPRs work with the caching changes. - Some internal fixes and optimisations.
Freenet will attempt to defragment your node.db4o on startup, and then if your physical security level is NORMAL, and there is enough disk space or you are running on java 1.5, it will attempt to encrypt it (disk space usage being equal to the size of node.db4o). You can turn this off using the following settings (in freenet.ini, shut down the node first, then edit the freenet.ini, then update the node, then start it back up): node.defragDatabaseOnStartup=false node.autoChangeDatabaseEncryption=false It is likely that there will be a small performance reduction in the short term as a result of these changes, and there may be an adjustment shock due to the HTL changes. However Bloom filter sharing will greatly improve performance, and the sooner we make the caching changes the more data will be flagged as usable by Bloom filter sharing (as we cannot share data that might have been requested locally). If you find any bugs, please let us know, post to the bug tracker at https://bugs.freenetproject.org/ (create an account first so we can contact you), or report them to the support list. Thanks! Please upgrade! Thanks. This build is not mandatory but it should have been; the next one probably will make this one mandatory.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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:support-requ...@freenetproject.org?subject=unsubscribe
