All advanced settings need to be configurable from the UI

[fpietrosanti]

All the advanced settings currently configurable from settings.py should be made configurable from the UI and from the command line.

This ticket is to implement the configurability of all advanced settings.

[vecna]

We need the "advaced settings" http://www.iconfinder.com/icondetails/23740/128/advanced_cog_gear_options_preferences_settings_icon in thee pages, and a little analysis of which default we had, and which elements are configurable at (Node|Context|Receiver) level.

[vecna]

specification. All of those value are not mandatory, because have defaults.

Node extended settings

• 138 email address of exception report

• 135 version (I've some issue in get the git revision ?)

To avoid manual hack in Settings:

• size limit in the name (apply to receiver name, context name, default 128)
• size limit in the description ( 1024)
• the size limit of all the other unicode field (default 2048)
• max file uploaded accepted (30 mb)
• Tor2web operation permission (admin, submission, tip. receiver, unauth)
• Tor proxy ? host + port + disable ?

Notification extended settings

• Title of the email (at the moment they are fixed and the mail body has flexible tempate)

Context extended settings

• receipt format regular expression
• tip time to live (express in days)
• submission time to live (express in hours)

Text embedded in the UI:

• all the descriptive texts hardcoded in the client, that may eventually require a client rebuild to be modified. This selection would grow with adopters experience, but I would start with:

  • Top of the submission page (would be called submission_introduction)
  • the text before "I agree" in the third step of submission ( submission_disclaimer )
  • The text with the receipt window ( receipt_description )

  the default present text would be the same actually shown, so this would not impact the appearance until the admin change them.

Receiver extended settings

• tags
• can delete submission (this functionality is implemented and unitTested in GLB but not yet implemented in GLClient)
• ability to disable notification (selective: mail, comments, file) since the logic it's no more Tip-centric, it's enough for an user login and check the list of available tips.

[fpietrosanti]

In implementing this ticket i suggest to:

• do not make configurable Tor host/port because this is hard-coded in the network-sandboxing-script in init.d
• be careful in exposing "new" features (open a dedicated ticket, for each of them or comment on this)

[vecna]

Ok, added all the described element, created a new branch that would pair with GLClient branch.

Plus

• Context, "file required", it's a boolean variable, if true, a submission can't be completed without almost one file selected.

Minus

• Tor settings

[vecna]

https://github.com/globaleaks/GLClient/pull/56 https://github.com/globaleaks/GLBackend/pull/109

Not yet completed (open/close view client side, unitTest backend)

[vecna]

Done GLBackend side https://github.com/globaleaks/GLBackend/commit/c25039e532206306f49415d3bdd863030ec0bd86

[vecna]

Merged in GLBackend, merged GLClient, still missing GLC interface

[vecna]

GLC interface completed. enhancing in GLClient GPGs branch.

update: Need to be merged with the GLC mods before merge in master. would broke retro compatibility, and for this reason would broke GLB retrocompatibility, and for this reason I'm on DB update tools.

[fpietrosanti]

@vecna is this fixed?

[vecna]

Yes, now is merged in master