Changes between Version 3 and Version 4 of CryptoPlugin


Ignore:
Timestamp:
Nov 9, 2014, 11:10:40 PM (9 years ago)
Author:
Steffen Hoffmann
Comment:

fix some copy-n-paste errors, revised newly added content

Legend:

Unmodified
Added
Removed
Modified

  • CryptoPlugin

    v3 v4  
    55== Description ==
    66
    7 CryptoPlugin supports cryptographically backed functions in Trac. Privacy offered based on these functions is much different compared to other privacy-related plugins.
     7CryptoPlugin supports cryptographically backed functions in Trac.
    88
    9 Privacy offered by a Trac system depending on setup and user action.
    10                                                
    11 We assume, that users always have the freedom to store data without protection, or take action to eigther sign-only or encrypt/encrypt-sign it.
     9This is [wiki:CryptoPlugin/Dev WiP] and in a very early stage. Nevertheless testers are very welcome.
    1210
    13 Trac plugins other than CryptoPlugin attempt to protect only some of Trac's content: SensitiveTicketsPlugin (tickets-only), PrivateWikiPlugin (wiki-only)
     11Why? Privacy offered based on these functions is much different compared to other privacy-related plugins, and
     12reports about your expectations as well as your findings will help them mature and match your needs.
    1413
    15 However they do not differenciate in terms of protection strength, so we're rated regardless of protected Trac content type here.
    16 
     14Tab.: Privacy offered by a Trac system depending on setup and user action
    1715|| ||Trac, no plugins||||other plugins installed||||||||!CryptoPlugin installed||
    1816||modules state||enabled||disabled||enabled||disabled||disabled||enabled||enabled||
    1917||client setting||n. a.||n. a.||n. a.||Trusted server||Trusted client||Trusted server||Trusted client||
    2018||||||||||||||||||
    21 ||regular content||n. a.||n. a.||n. a.||n. a.||n. a.||n. a.||n. a.||
    2219{{{#!tr
    2320  {{{#!td
    … …  
    118115}}}
    119116 independent of client and server security for private user key storage
    120                                                        
     117
     118Regular 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.
     119
     120While Trac plugins other than CryptoPlugin (incomplete list follows)
     121 * PrivateTicketsPlugin (ticket-only)
     122 * PrivateWikiPlugin (wiki-only)
     123 * SensitiveTicketsPlugin (ticket-only)
     124attempt to protect only some part ('realm') of Trac's content, they do not differentiate in terms of protection strength, so they're rated together for simplicity here.
     125
    121126Ultimate privacy doesn't assume any trust outside of Trac system software (plugins included). This kind of inherit Trac content protection is neither available nor planned yet.
    122127
    123 This is [wiki:CryptoPlugin/Dev WiP] and in a very early stage.  Nevertheless testers are very welcome.
    124 Reports about your expectations as well as your findings will help it grow and
    125 mature.
     128So you have to decide now, if the available protection is enough for your data. 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.
    126129
    127130== Bugs/Feature Requests ==