On Thu, Apr 18, 2019 at 8:57 AM Mez Pahlan <mez.pah...@gmail.com> wrote: > I could ignore it, for sure. But that was the reason I received a security > bug that I'm looking to fix. That the tokens in my plugin were being stored > in plain text. If I leave them in plain text what am I actually fixing? I'm > fixing forward for new configurations but for existing configurations I'd > like to do something.
The plain text tokens are already potentially compromised and need to be regenerated and stored encrypted anyways. This is specific to each plugin on how to go about regenerating keys and whatnot. -- Matt Sicker Senior Software Engineer, CloudBees -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oypMhap7dxMyyrePWWcH_6G5pvY4j0NL3G4vz74eZNzWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
