Skip to content

[JENKINS-61808] Always encrypt f:password values, not just those backed by Secret #11456

Closed

Description

@jenkins-infra-bot

Too many people get the Secret getters wrong. What if we just always returned a Secret, and had a StringConverter to handle submitted secrets and transparently decrypt again?

This would eliminate this class of problem. Only storage would really need to be done as Secret, but the internal API types wouldn't matter so much.

Test cases need to include String typed encrypted secrets, and unmatched getter/setter types.


Originally reported by danielbeck, imported from: Always encrypt f:password values, not just those backed by Secret
  • assignee: danielbeck
  • status: Resolved
  • priority: Minor
  • component(s): core
  • label(s): security
  • resolution: Fixed
  • resolved: 2020-05-19T22:15:40+00:00
  • votes: 0
  • watchers: 2
  • imported: 2025-11-24
Raw content of original issue

Too many people get the Secret getters wrong. What if we just always returned a Secret, and had a StringConverter to handle submitted secrets and transparently decrypt again?

This would eliminate this class of problem. Only storage would really need to be done as Secret, but the internal API types wouldn't matter so much.

Test cases need to include String typed encrypted secrets, and unmatched getter/setter types.

Activity

  1. jenkins-infra-bot commented on Apr 4, 2020

    @jenkins-infra-bot
    Author
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions