Contents
Cryptography for Trac
Notice: This plugin is unmaintained and available for adoption.
Description
This plugin supports cryptographically backed functions in Trac. The level of privacy offered based on these functions is different compared to other privacy-related plugins:
- PrivateTicketsPlugin (ticket-only)
- PrivateWikiPlugin (wiki-only)
- SensitiveTicketsPlugin (ticket-only)
These plugins attempt to protect only some part ('realm') of Trac's content, they do not differentiate in terms of protection strength.
This is WiP and in a very early stage. Nevertheless testers are very welcome. Reports about your expectations as well as your findings will help them mature and match your needs.
Tab.: Privacy offered by a Trac system depending on setup and user action
installation | Trac, no plugins | other plugins installed | CryptoPlugin installed | ||||
modules state | enabled | disabled | enabled | disabled | disabled | enabled | enabled |
session setting (per user) | n. a. | n. a. | n. a. | Trusted server | Trusted client | Trusted server | Trusted client |
signed content |
|
|
| weak | weak | weak | weak |
secured content |
| none | strong | strong | very strong | strong | very strong |
Privacy strength rating legend:
- n. a.
not applicable
- none
no protection, not counting read-only wiki pages for (very weak) privacy
- weak
prevents unrecognized content change without read-protection
- strong
depending on server security of Trac system software (plugins included) and storage for Trac content and private user keys
- very strong
depending on client security for private user key storage
- ultimate
independent of client and server security for private user key storage
Regular content is accessible as per applicable TracPermissions settings, and users can save content without additional protection regardless of other options, if available at all. Since it is the same for any setup, it's not worth mentioning this type of content in the table above.
Ultimate privacy doesn't assume any trust outside of the Trac system software, and this includes plugins. This kind of inherent Trac content protection is neither available nor planned yet.
Likely there are not many web services that grant at least strong protection without installation of special software at client side. And if so, they certainly do not offer Trac's documentation and bug-tracking capabilities.
Bugs/Feature Requests
Existing bugs and feature requests for CryptoPlugin are here.
If you have any issues, create a new ticket.
enhancement |
0 / 1 |
|
---|---|---|
task |
0 / 1 |
Download
Download the complete, zipped source (all branches) from here.
Source
You can check out CryptoPlugin from here using Subversion, or browse the source with Trac.
Installation
General instructions on installing Trac plugins can be found on the TracPlugins page.
Recent Changes
- 11813 by hasienda on 2012-07-27 22:48:39
-
CryptoPlugin: Implement some functionality now, starting with OpenPGP, refs #10030 and #10080.
- 11812 by hasienda on 2012-07-27 22:24:28
-
CryptoPlugin: Add blank user preferences page, refs #10080.
- 11811 by hasienda on 2012-07-27 22:18:35
-
CryptoPlugin: Create basic i18n infrastructure, refs #10080.
(more)
Author/Contributors
Author: hasienda
Maintainer: none (needsadoption)
Contributors: