On Thu, Sep 01, 2016 at 05:46:08PM +0200, Stefan Botter wrote:
I need help with the extending of the validity of a project's signkey. As far as I know the signkeys will be automatically extended, when they reach their expiry time. I now have several projects, where the repo will not get published. I checked deeper and found the signkey of the project expired. osc signkey --extend terminates with Server returned an error: HTTP Error 400: Bad Request /usr/bin/sign: 256 a closer look in src_server.log shows an additional line self-sig is not made with sha1
That's weird. I have no clue why the code doesn't take the hash algo from the signature instead of insisting that sign is called with a matching argument. I guess it will work if you also specify a -h sha256 argument with the extend call, but I'll change the code to take the hash type from the pubkey. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org