Purge false positives log spam. It is not necessary, and not helpful. If the 20%+ "false positives" were the result of actual bloom filter false positives it would indicate a serious problem, but the most likely explanation is simply a consequence of us fetching more blocks than we strictly need (since some of them will fail), and similar issues. We could quantify this in detail but IMHO it isn't a serious problem.
Upgraded to BouncyCastle 1.51 and JUnit 4
Updated dependencies.properties for BC 1.51
PluginReplySender: Add getConnectionIdentifier()
- This allow identifying to which client connection a PluginReplySender belongs.
- It is need for WOT SubscriptionManager (= event-notifications) so it can determine whether a certain client is already subscribed to certain events. Also, it will have to store the connection ID in the database so when events happen in the future it can obtain the PluginReplySender with the matching ID to send the events back to.
- For pure FCP network connections, the data needed for this was already stored: A random per-network-connection identifier at FCPConnectionHandler.connectionIdentifier. It was only a matter of exposing it through a getter.
- For intra-node connections between plugins, a new random ID is stored for each PluginTalker
- The result of getConnectionIdentifier() is not only the connection ID but also contains the client-specified "Identifier" from FCP which was already existing in the code. This is to not break clients which try to maintain multiple connections by using a different "Identifier" field.
Merge remote-tracking branch 'xor/PluginReplySender.getConnectionIdentifier' into next
Merge branch 'master' into next
Merge remote-tracking branch 'unixninja92/BC151andJUnit4' into next
DisconnectedException: Don't synchronize function which modifies nothing; JavaDoc
- The synchronized likely resulted from copy-pasting the parent function which does modify stuff as skeleton.
- Add JavaDoc which explains the typical reason for not producing a stack trace.
README: update links

The link to the FCP spec was outdated; the security site has since gone
offline.
Merge remote-tracking branch 'toad/kill-false-positives-reporting' into next
FProxy: allow hiding JVM EOL alert

The false values changed to true are userCanDismiss and
shouldUnregisterOnDismiss, respectively.

Specifying a null dismiss text for a dismissable alert prevents the
alert from displaying.
Fix big containers losing files: When we move a file to an archive ("external" container), we need to reset its name as we won't use the full path when looking it up.
better error message with too old node.
Update jSite version and download link.
Merge remote-tracking branch 'toad/fix-big-containers-losing-files' into next

When large files are moved to external containers, /path/to/filename redirects
to [external container]/filename.

Before this fix, this caused "Not in archive" errors because the file was
stored as [external container]/path/to/filename.
Remove link to FAFS, add link to jSite homepage.
Moved long too old message from *TooOldShort to *ToOld.
Merge remote-tracking branch 'ArneBab/next' into next
Merge remote-tracking branch 'bombe/update-links-to-jsite' into next
Logging: Free by finalize is a leak

Conflicts:
	src/freenet/support/io/TempBucketFactory.java