Author: toad Date: 2007-07-20 17:24:38 +0000 (Fri, 20 Jul 2007) New Revision: 14209
Modified: trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties Log: clarify doc Modified: trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties =================================================================== --- trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties 2007-07-20 17:18:20 UTC (rev 14208) +++ trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties 2007-07-20 17:24:38 UTC (rev 14209) @@ -524,8 +524,8 @@ Node.nodeNameLong=Node nickname. This will be visible to your friends only. Node.oneConnectionPerIP=Limit to one connection per address? Node.oneConnectionPerIPLong=Don't allow more than one connection per address? This will make it slightly harder for an attacker to connect more than once to your node as different identities, in order to dominate your routing or make harvesting easier. Also prevents having the same node connected on darknet and opennet simultaneously. -Node.opennetEnabled=Enable Opennet support? -Node.opennetEnabledLong=Enable Opennet? If opennet is enabled, the node will automatically exchange node references with other nodes. But this means that the fact that you are running a node is no longer private, and many attacks are much easier. If you know enough people running Freenet, you should stick to darknet connections to them. +Node.opennetEnabled=Enable Opennet support (automatically connect to untrusted nodes)? +Node.opennetEnabledLong=Enable Opennet? If opennet is enabled, the node will automatically exchange node references with other untrusted nodes (Strangers as opposed to Friends). But this means that the fact that you are running a node is no longer private, and many attacks are much easier. If you know enough people running Freenet, you should stick to darknet connections to them. Node.outBWLimit=Output bandwidth limit (bytes per second) Node.outBWLimitLong=Hard output bandwidth limit (bytes/sec); the node should almost never exceed this Node.port=FNP port number (UDP)
