FWIW: it's the final / after 'licenses' which causes the problem.
The OpenSSL Software Foundation
Individual Contributor License Agreement ("Agreement") v1.0
https://www.openssl.org/licenses/
Apparently, there is a simple rewrite rule on the server, which fails to remove the trailing slash.
https://www.openssl.org/policies/cla.html/
If you remove the trailing slash, the link works.
The OpenSSL Software Foundation
Individual Contributor License Agreement ("Agreement") v1.0
https://www.openssl.org/licenses
IMHO, both the rewrite rule as well as the link in the ICLA/CCLA document should be fixed.
https://www.openssl.org/policies/openssl_icla.pdf
Matthias
> -----Original Message-----
> From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> On Behalf Of pl
> Sent: Wednesday, April 27, 2022 10:14 PM
> To: openssl-users@xxxxxxxxxxx
> Subject: Legal : guide to sign cla. has legal mail a PGP key ?
>
> Hi,
>
> After a pull request to github for openssl demos sslecho i was requested
> to sign a cla since my change
> was considered non trivial.
>
> Using https://www.openssl.org/policies/openssl_icla.pdf as a libreoffice
> input i did recreate a pdf. One remark here, the url wihtin document
> https://www.openssl.org/licenses/ leads to an existing page.
>
> I wanted to send it ciphered since it contains personal information but
> didn't find a gpg key for legal at opensslfoundation.org, is there any ?
> If no what is the secure procedure to use to stay within digital
> boundaries ?
>
> Regards,
>
>
>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
