Comment 14 for bug 848476

That's a good point, Julian. I think it is important to let people know that they *have* been vulnerable to something, in case they need to take the opportunity to double-check whether they *were* actually exploited, or in case it lets them know that they need to upgrade or take defensive action on other installations, or advise someone else to do so.

I guess a possible compromise would be to remove known_issues.rst from the distribution. I just checked and the only mentions of it in the other docs point to the current version of it on the web:

http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/known_issues.rst

Here are all the hits for "grep -r known_issues ." in my 1.8.3 sandbox:

docs/how_to_make_a_tahoe-lafs_release.rst:[✓] 1 update doc files: `<../relnotes.txt>`_, `<../CREDITS>`_, `<known_issues.rst>`_, `<../NEWS>`_. Add release name and date to top-most item in NEWS.
docs/known_issues.rst:`<http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/known_issues.rst>`_.
docs/known_issues.rst:<historical/historical_known_issues.txt>`_.
docs/historical/historical_known_issues.txt:http://tahoe-lafs.org/source/tahoe/trunk/docs/historical/historical_known_issues.txt
docs/historical/historical_known_issues.txt:http://tahoe-lafs.org/source/tahoe/trunk/docs/known_issues.rst
relnotes.txt:[2] and known_issues.rst [3] file for details.
relnotes.txt:please see the known_issues.rst file [3].)
relnotes.txt:[3] http://tahoe-lafs.org/trac/tahoe/browser/docs/known_issues.rst

So I guess you could remove docs/known_issues.rst and docs/how_to_make_a_tahoe-lafs_release.rst. The latter one is clearly not needed by users and which isn't mentioned by any other document in the source tree.