Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Won't Fix
Description
When upgrading Publish-over-SSH from v1.13 to v1.14, I get the following error when using "Send build artifacts over SSH":
ERROR: Exception when publishing, exception message [Failed to connect session for config [my-server-name]. Message [Session.connect: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)]]
I have configured this SSH server with user root, remote directory '/' and password authentication without a key.
When I google this error I only get responses regarding the programming of SSH clients, no mention of a misconfiguration of some kind.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Description |
When upgrading Publish-over-SSH from v1.13 to v1.14, I all of a sudden get the following error when using "Send build artifacts over SSH": {quote}ERROR: Exception when publishing, exception message [Failed to connect session for config [my-server-name]. Message [Session.connect: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)]]{quote} I have configured this SSH server with user root, remote directory '/' and password authentication without a key. When I google this error I only get responses regarding the programming of SSH clients, no mention of a misconfiguration of some kind. |
When upgrading Publish-over-SSH from v1.13 to v1.14, I get the following error when using "Send build artifacts over SSH": {quote}ERROR: Exception when publishing, exception message [Failed to connect session for config [my-server-name]. Message [Session.connect: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)]]{quote} I have configured this SSH server with user root, remote directory '/' and password authentication without a key. When I google this error I only get responses regarding the programming of SSH clients, no mention of a misconfiguration of some kind. |
Workflow | JNJira [ 171462 ] | JNJira + In-Review [ 184316 ] |
Assignee | bap [ bap ] | Alex Earl [ slide_o_mix ] |
Resolution | Won't Fix [ 2 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Not sure if it is related, but which version of Jenkins are you using?
I had the same problem with 1.14. Downgrading this plugin to 1.13 solved this issue.
This problem only happened when ssh to a Solaris Sparc machine. Other platforms (x86, freebsd, hpux) are ok.