Developer Certificate of Origin

Jussi Kivilinna jussi.kivilinna at
Fri Aug 23 19:14:41 CEST 2019


Where I can find you public key so I have verify the signature? 


>         Developer's Certificate of Origin 1.1
>         By making a contribution to this project (libgcrypt), I certify that:
>         (a) The contribution was created in whole or in part by me and I
>             have the right to submit it under the open source license
>             indicated in the file; or
>         (b) The contribution is based upon previous work that, to the best
>             of my knowledge, is covered under an appropriate open source
>             license and I have the right under that license to submit that
>             work with modifications, whether created in whole or in part
>             by me, under the same open source license (unless I am
>             permitted to submit under a different license), as indicated
>             in the file; or
>         (c) The contribution was provided directly to me by some other
>             person who certified (a), (b) or (c) and I have not modified
>             it.
>         (d) I understand and agree that this project and the contribution
>             are public and that a record of the contribution (including all
>             personal information I submit with it, including my sign-off) is
>             maintained indefinitely and may be redistributed consistent with
>             this project or the open source license(s) involved.
> Hash: SHA256
> The patches I just sent are here
> cd09b29154daad1954f26cb5a21f6221505346f6
> and I sign off on them.
> aEOaAQDNlTwqHjspFaZEUyvvaWojzFl7/GDM2UT7BnqAr84rUAEA9ZNfjLZwMpIg
> fpPgTYzb6N/iK5jG5TrVzhblHb3LtgQ=
> =/pmU
> -- 
> Shawn Landden
> _______________________________________________
> Gcrypt-devel mailing list
> Gcrypt-devel at

More information about the Gcrypt-devel mailing list