You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AZMCode opened this issue
Jan 9, 2022
· 5 comments
Labels
DuplicateDuplicate of another issueLinuxIssues specific for LinuxMonoIssues specific for MonoNetworkIssues affecting internet connections of CKANSupportIssues that are support requests
KSP Version: 1.12.3.3173
I haven't made any manual modifications to KSP's files.
Problem
Exactly the same issue as the currently pinned issue, #3468.
Steps to reproduce
Install ckan-bin through yay
Attempt to install a mod with its primary host being spacedock (KIS and KAS yield this problem for me)
Get error'ed
Expected behavior
CKAN manages to download the mods
Error downloading KAS 1.10: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
at /build/mono/src/mono/external/boringssl/ssl/handshake_client.c:1132
Error downloading KIS 1.29: Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
at /build/mono/src/mono/external/boringssl/ssl/handshake_client.c:1132
Further Details
Having read the pinned issue, I read the arch section on the workaround for this bug, and decided to attempt fixing it.
However, I found that the certificate being talked about here, /etc/ssl/certs/DST_Root_CA_X3.pem, does not exist at all on my system, so I could not blacklist it.
I attempted the rest of the steps, just in case my Mono install had outdated certificates, but I found that this did not fix the situation.
If I can provide further details on my install, or other related certificates in my system/blacklist folders, I will.
If it's any help, i can browse spacedock through https just fine, so there is a valid certificate for them somewhere in my system. Not sure what's going on.
The text was updated successfully, but these errors were encountered:
HebaruSan
changed the title
[Bug] Pinned OpenSSL issue despite not having the relevant certificate at all
Ssl error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED
Jan 9, 2022
Update: I ran through the checklist of causes for the bug on the wiki page for SSL Certificate errors, and have verified that I am indeed running mono 6.12.0
I have now manually run through mono's Trust store and found /usr/share/.mono/certs/Trust/ski-79B459E67BB6E5E40173800888C81A58F6E99B6E008B8263BBE0634459E340D2B0CF108200.cer, which appears to be the ISRG Root X1 certificate, which is what my browser identifies as the root certificate that eventually validates spacedock.info, so there is a valid certificate in the mono trust store.
Wow, it, uh, started working?
Is it possible for a certificate chain to start and stop working like that?
Either way, it seems to now be irreproducible on my side.
Closing.
DuplicateDuplicate of another issueLinuxIssues specific for LinuxMonoIssues specific for MonoNetworkIssues affecting internet connections of CKANSupportIssues that are support requests
Background
I haven't made any manual modifications to KSP's files.
Problem
Exactly the same issue as the currently pinned issue, #3468.
Steps to reproduce
Install
ckan-bin
through yayAttempt to install a mod with its primary host being spacedock (KIS and KAS yield this problem for me)
Get error'ed
Expected behavior
CKAN manages to download the mods
Further Details
Having read the pinned issue, I read the arch section on the workaround for this bug, and decided to attempt fixing it.
However, I found that the certificate being talked about here,
/etc/ssl/certs/DST_Root_CA_X3.pem
, does not exist at all on my system, so I could not blacklist it.I attempted the rest of the steps, just in case my Mono install had outdated certificates, but I found that this did not fix the situation.
If I can provide further details on my install, or other related certificates in my system/blacklist folders, I will.
If it's any help, i can browse spacedock through https just fine, so there is a valid certificate for them somewhere in my system. Not sure what's going on.
The text was updated successfully, but these errors were encountered: