Skip to content
This repository has been archived by the owner on Dec 22, 2021. It is now read-only.

Stricter checking for self-signed certificates #2

Open
mkrautz opened this issue Jul 13, 2013 · 0 comments
Open

Stricter checking for self-signed certificates #2

mkrautz opened this issue Jul 13, 2013 · 0 comments
Labels

Comments

@mkrautz
Copy link
Contributor

mkrautz commented Jul 13, 2013

As-is, libmumble isn't as strict about self signed certificates as it should be. It doesn't check for the 'certificate signing' key usage.

Take for example the replay-server certificate I'm working with at the moment, created using the same template as selfsign-server from the tree:

$ openssl verify -verbose -issuer_checks -purpose sslserver -CAfile testdata/x509/replay-server/replay-server.crt testdata/x509/replay-server/replay-server.crt 
testdata/x509/replay-server/replay-server.crt: CN = localhost, O = libmumble
error 32 at 0 depth lookup:key usage does not include certificate signing
CN = localhost, O = libmumble
error 32 at 0 depth lookup:key usage does not include certificate signing
CN = localhost, O = libmumble
error 32 at 0 depth lookup:key usage does not include certificate signing
CN = localhost, O = libmumble
error 32 at 0 depth lookup:key usage does not include certificate signing
CN = localhost, O = libmumble
error 32 at 0 depth lookup:key usage does not include certificate signing
CN = localhost, O = libmumble
error 32 at 0 depth lookup:key usage does not include certificate signing
CN = localhost, O = libmumble
error 20 at 0 depth lookup:unable to get local issuer certificate
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant