-
-
Notifications
You must be signed in to change notification settings - Fork 147
No way to disable SSL verification #169
Comments
+1 |
1 similar comment
+1 |
AGRRHHH!
|
Quick fix: add func newTransport() Transport {
t := &HTTPTransport{}
rootCAs, err := gocertifi.CACerts()
if err != nil {
log.Println("raven: failed to load root TLS certificates:", err)
} else {
t.Client = &http.Client{
Transport: &http.Transport{
Proxy: http.ProxyFromEnvironment,
TLSClientConfig: &tls.Config{RootCAs: rootCAs, InsecureSkipVerify: true},
},
}
}
return t
} |
@subvillion mby you should add |
@subvillion Can you test out #221 - [branch] ? It adds a Unfortunately I'm unable to verify it for a few days. |
@mavidser - thx, just works! sentry, _ := raven.New("https://xxx@domain/8848")
sentry.SetSSLVerification(false)
sentry.CaptureMessageAndWait("myMSG") |
ack, verified! thanks! btw, if anyone wants to disable verification without forking raven, here's how I do it currently (until linked the PR is merged): client, _ := raven.New("https://xxx@domain/id")
// use raven.DefaultClient instead of client if using the package directly
client.Transport = &raven.HTTPTransport{
Client: &http.Client{
Transport: &http.Transport{
Proxy: http.ProxyFromEnvironment,
TLSClientConfig: &tls.Config{InsecureSkipVerify: true},
},
},
} |
Title says it all.
What'd be the best way to go ahead with implementing the solution?
One way's to implement a DisableSSLValidation() on the client, or alternatively we can use the
?ssl_verify=0
like the python client uses. Thoughts?Maybe we can implement supplying our own CertPool in the future too.
The text was updated successfully, but these errors were encountered: