Jenkins already includes the `instance-identity` module, which is the standard mechanism¹ for both uniquely identifying a Jenkins installation, and permitting asymmetrically-encrypted communications with it. Is there a reason you are not using it? If so, that should be clearly documented under “Alternative Approaches”. There is a vague mention of OpenSSH keys, but this module is not limited to SSH (much less OpenSSH), and public-key encryption has widespread library support.
¹ https://wiki.jenkins.io/display/JENKINS/Instance+Identity -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2RgWBM-2f-Ys6-hONCdiOuyHayf0NhZF7oEMcbpNWHnQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
