Commit 95622b3
committed
Ensure we can transfer SecretBytes via remoting
If we tried to transfer SecretBytes via Remoting then the remote side
would end up with the encrypted byte[] but not the key needed to decrypt
the data.
Sending the decryption key would be a bad thing, but we can send the
data in plain text to the agent and then re-encrypt it with the remoting
(agent) sides key. As generally the remoting side would not be a
Jenkins the mock encryption key would be used in this case.
Whilst the mock key is static, it is not expected that ian agent
persists these SecretBytes.
fixes: #10131 parent 6afd2a4 commit 95622b3
File tree
1 file changed
+29
-1
lines changed- src/main/java/com/cloudbees/plugins/credentials
1 file changed
+29
-1
lines changedLines changed: 29 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
| 38 | + | |
38 | 39 | | |
| 40 | + | |
39 | 41 | | |
40 | 42 | | |
41 | 43 | | |
| |||
78 | 80 | | |
79 | 81 | | |
80 | 82 | | |
81 | | - | |
| 83 | + | |
| 84 | + | |
82 | 85 | | |
83 | 86 | | |
84 | 87 | | |
| |||
119 | 122 | | |
120 | 123 | | |
121 | 124 | | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
122 | 133 | | |
123 | 134 | | |
124 | 135 | | |
| |||
343 | 354 | | |
344 | 355 | | |
345 | 356 | | |
| 357 | + | |
| 358 | + | |
| 359 | + | |
| 360 | + | |
| 361 | + | |
| 362 | + | |
| 363 | + | |
| 364 | + | |
| 365 | + | |
| 366 | + | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
| 370 | + | |
| 371 | + | |
| 372 | + | |
| 373 | + | |
346 | 374 | | |
347 | 375 | | |
348 | 376 | | |
| |||
0 commit comments