Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #9519 Bug Fix for plugin tracker encryption: Add the possibility to empty an encrypted field already set
    Actions
    Infos
    #9519
    Fares BEN KHALIFA (khalifaf)
    2016-10-03 14:34
    2016-09-23 17:55
    9787
    Details
    Bug Fix for plugin tracker encryption: Add the possibility to empty an encrypted field already set
    Empty
    Trackers
    8.17
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2016-10-03
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #9341 Tuleap Releases 9.0 Delivered 2016-17-10 11:32 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #9519

    Git commit

    tuleap/tuleap/stable

    Merge 'gerrit #6541' into stable/master 55f35c2170
    User avatar Thomas Gerbet (tgerbet) , 2016-10-03 14:27
    request #9519: Bug Fix for plugin tracker encryption, Add the possibility to empty an encrypted field already set ccd127f514
    User avatar Fares BEN KHALIFA (khalifaf) , 2016-09-24 05:58

    Release

    release #130
    Referenced by request #9519

    Artifact Tracker v5

    rel #9341 9.0

    Other

    gerrit #6541
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2016-10-03 14:34
    Integrated into Tuleap 8.19.99.60.
    • Status changed from Acknowledged to Closed
    • Reported in version set to 8.17
    • Connected artifacts
    • Close date set to 2016-10-03
    • Is an Enhancement or an internal improvement? cleared values: enhancement
    User avatar
    Thomas Gerbet (tgerbet)2016-09-29 11:28
    Hum ok but I'm not fully convinced on this one, it looks like we are doing the wrong choice to try to make the plugin more usable than it is going to be.

    Not directly related to this specific request but in terms of usability it would be nice if we display the large random string only if the user ask for it because I do not know a lot of people capable of doing cryptographic operations just by looking at a string.
    • Status changed from New to Acknowledged
    User avatar
    Fares BEN KHALIFA (khalifaf)2016-09-27 16:38
    Hi Thomas,

    We prefer to separate the empty strings and the other ones because if an empty field will be encrypted, it will be displayed in its encrypted form, so the end user can not detect that the field is empty.
    User avatar
    Thomas Gerbet (tgerbet)2016-09-27 13:39
    Hello,

    I'm not sure that allowing an empty value like it is possible when the artifact is created is the right call here. After all, an empty string is valid value too. Why do not encrypt the value every time?