-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cira #133
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #133 +/- ##
==========================================
- Coverage 36.51% 35.57% -0.95%
==========================================
Files 55 56 +1
Lines 4017 4124 +107
==========================================
Hits 1467 1467
- Misses 2458 2565 +107
Partials 92 92 ☔ View full report in Codecov by Sentry. |
e0ea0e5
to
62fb1d5
Compare
|
||
config := &tls.Config{ | ||
Certificates: []tls.Certificate{s.certificates}, | ||
InsecureSkipVerify: true, |
Check failure
Code scanning / CodeQL
Disabled TLS certificate check High
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix AI 19 days ago
To fix the problem, we need to ensure that the TLS client verifies the server's certificate chain and host name. This involves removing the InsecureSkipVerify: true
setting and ensuring that the server is configured with valid certificates.
- Remove the
InsecureSkipVerify: true
line from the TLS configuration. - Ensure that the server is set up with valid certificates that can be verified by the client.
@@ -64,3 +64,2 @@ | ||
Certificates: []tls.Certificate{s.certificates}, | ||
InsecureSkipVerify: true, | ||
CipherSuites: nil, |
No description provided.