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
Merge remote-tracking branch 'unixninja92/BC151andJUnit4' into next
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.