•  
      request #44081 Internal symmetric cryptographic API should be resistant against Invisible Salamanders / Confused Deputies attacks
    Infos
    #44081
    Thomas Gerbet (tgerbet)
    2026-01-26 17:52
    2025-08-05 17:33
    45816
    Details
    Internal symmetric cryptographic API should be resistant against Invisible Salamanders / Confused Deputies attacks

    In it's current form the our internal API does not make possible to prevent this sort of attack from happening, it should.

    References:
    https://eprint.iacr.org/2019/016
    https://soatok.blog/2023/03/01/database-cryptography-fur-the-rest-of-us/

    Other
    All
    Empty
    • [ ] enhancement
    • [x] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2026-01-26
    Attachments
    Empty
    References
    Referencing request #44081

    Git commit

    tuleap/tuleap/stable

    chore: Move current symmetric crypto implementation to a legacy namespace 2cc4163f8e
    feat: Introduce a new symmetric crypto API b123f8514c
    chore: Re-encrypt the Git Jenkins tokens with the new cryptography API a1d954ca8f
    fix: Re-encrypting Git Jenkins token must not always set an empty string 7c68c0125d
    chore: Re-encrypt the TTM job campaign tokens with the new cryptography API 8da7c07fce
    chore: Re-encrypt OAuth2 keys with the new cryptography API 6ac3b2551d
    chore: Re-encrypt Bugzilla API keys with the new cryptography API ab62457d4b
    chore: Do not display newly created SVN tokens 9e6ceb8161
    chore: Re-encrypt ForgeConfig secret values with the new cryptography API f4ffc3094a
    chore: Re-encrypt GitLab webhook secret with the new cryptography API 2ef222f2c1
    chore: Re-encrypt GitLab group/repository secrets with the new cryptography API 33cdae2c66
    fix: Move DB migration of the ForgeConfig secrets to the new crypto API into Tuleap core 098c4ef04b
    chore: Re-encrypt JIRA token with the new cryptography API ce37d62826
    chore: Re-encrypt OO Document Server token with the new cryptography API 9cc64aec8d
    chore: Remove legacy cryptography API 1f9ed394cf
    Referenced by request #44081

    Follow-ups