hoto / jenkins-credentials-decryptor Goto Github PK

It looks like most secrets are encrypted by the Secret class. This however does not seem to be the case with SecretBytes which has it's own implementation. This seems to invalidate the assumption made here which makes the code take the wrong branch (else). Forcing the use of decryptNewFormatCredentials unfortunately doesn't fix the issue.

when migrating Jenkins, it would be better to let this tool optionally output in JSON format. So that we can automate the following process easier with other tools.

we have been requested to use Ansible vault to source control the Jenkins Credentials. But doing several dozens of them one by one is too tedious.

Hi there
I was trying to decrypt credentials from a Jenkins version 2.190.1. Then it went error with message:
`
2023/03/04 17:19:17 Error. Decrypted hudson secret does not contain expected checksum.
Expected checksum keyword:
::::MAGIC::::
Decrypted secret:

panic: Error. Decrypted hudson secret does not contain expected checksum.
Expected checksum keyword:
::::MAGIC::::
Decrypted secret:

goroutine 1 [running]:
log.Panic(0xc00003ff68, 0x1, 0x1)
/opt/hostedtoolcache/go/1.14.10/x64/src/log/log.go:351 +0xac
main.check(...)
/home/runner/work/jenkins-credentials-decryptor/jenkins-credentials-decryptor/cmd/jenkins-credentials-decryptor/main.go:38
main.main()
/home/runner/work/jenkins-credentials-decryptor/jenkins-credentials-decryptor/cmd/jenkins-credentials-decryptor/main.go:23 +0x23e
`
I also tried other tools to decrypt it. Every tool says it cant find ":::MAGIC:::".

We are using LDAP binding. We need to include the binding username and encrypted passwords in Jenkins config.xml file. We need to be able to the ability to generate the encrypted password in the case when the binding password gets updated. Thanks in advance.