issue2550864 - Potential information leakage via journal/history Fix this by making the hyperdb::Class::history function check for view permissions on the journaled properties. So a user that sees [hidden] for a property in the web interface doesn;t see the property changes in the history. While doing this, relocated the filter for quiet properties from the templating class to the hyperdb. Also added the skipquiet option to the history command in roundup-admin.py to enable filtering of quiet params. Also changed calls to history() in the backend databases to report all items. Changed inline documentation for all history calls that document the actions. The create action (before nov 6 2002) used to record all parameters. After that point the create call uses an empty dictionary. The filtering code depends on the create dictionary being empty. It may not operate properly on very old roundup databases. Changed calls to logging.getLogger to roundup.hyperdb.backends to allow filtering the back end while keeping hyperdb logging. In cgi/templating.py, changed history() function consolidating handiling of link and unlink actions Added tests for quiet property filtering and permission filtering of history.

--- a/doc/design.txt	Tue Apr 11 22:20:13 2017 -0400
+++ b/doc/design.txt	Fri Apr 14 23:24:18 2017 -0400
@@ -286,10 +286,12 @@
 will create a property called ``title`` that will be included in the
 get_required_props() output. Calling
 db.issue.properties['title'].get_default_value() will return "not set".
-Changes to the property will not be displayed in emailed change notes,
-the history at the end of the item pages in the web interface and will
-be suppressed in the confirmation notice (displayed as a green banner)
-shown on changes.
+Changes to the property will not be displayed in:
+
+   - emailed change notes,
+   - the history at the end of the item pages in the web interface
+   - in the confirmation notice (displayed as a green banner)
+     shown on changes.
 
 These objects are used when specifying what properties belong in classes::