Re: Signing keys

Hello Sven,

The individual .sig files are all available in the download area 
directly.  The bacula-sig tar file is for convenience, and is the only one
that is listed in the WordPress download area.  We have been doing it 
that way for years.  Perhaps you misunderstood my email -- I have
replaced all the .sig files with the correct version.

In fact what was previously released was perfectly fine, it was just 
signed with an older signature key (DSA I think).  Since 2018 we have
used a new RSA key for signing.

Bottom line is that I did just replace the existing bacula-*.tar.gz 
(and  .bz2) files with new signature files as you have now requested.

I think this already satisfies your request.  If not, please let me know.

Thanks for confirming that the tar'ed .gz signature files are correct. :-)

Best regards,
Kern

On 12/11/20 10:49 AM, Sven Hartge wrote:
> On 11.12.20 10:17, Kern Sibbald wrote:
>
>> If you find any additional problems, please let me know.
>
> One nitpick is that the signatures are bundled into the 
> bacula-sigs-9.6.7.tar.gz, but at least the Debian system for 
> downloading and verifying upstream releases cannot use this (to my 
> knowledge), as it expects the signature file to be available as 
> tarbal-name.sig
>
> If you could just replace the already existing bacula-*.tar.gz.sig 
> files, this would help us tremendously.
>
> Other that that, by manually extracting the correct signature file, I 
> can confirm it now verifies correctly with the pubkey from the website.
>
> Grüße,
> Sven.
>
>
> _______________________________________________
> Bacula-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-devel



_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel