You could look at how Juseppe signs its update site data: https://github.com/yandex-qatools/juseppe/blob/master/src/main/java/ru/lanwen/jenkins/juseppe/gen/Signer.java
On 14.09.2015, at 15:09, [email protected] wrote: > Hi everyone! > > I want to filter "malicious" plugin updates from the update center so no one > can install them accidentially. > Just stripping the update information from the JSON doesn't work because the > output is signed. > > Is there another way to filter updates? > If not, is there a documentation about how to sign the output so Jenkins > would accept it? > > Thanks in advance > > Steffen > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" 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-users/0b90218c-c4b7-49ae-8a9b-c509ab150211%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/E4DAB215-573F-4753-A8FD-11BE8368155F%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
