-
Notifications
You must be signed in to change notification settings - Fork 339
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
SSL error "certificate verify failed" #23
Comments
I'm getting the same thing. |
Me too! |
So am I & ruby --version |
I have the same problem. $ gist -v $ ruby -v |
Same here. Gist 2.0.0. I assume this is related to the recent Github switchover to HTTPS-only? Under
I get:
And under
I get:
|
Same. Thanks |
yeah -- ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-linux] same error |
Same here...
|
Same.
|
same error: ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-linux] |
Same here
|
metoo |
The gem includes CA certificates, but the standalone script is not using them. Offering a fix in rduplain/gist@1e29722b84635b8fa680dca4fd7e32a976402138. Test using: https://github.com/rduplain/gist/raw/master/gist e.g.
|
Doesn't work with 1.9.2
Adding
on the second line fixes that https://gist.github.com/762011 |
Added suggestion from darthdeus in rduplain@6553d8e3cdffce6fcc1fdf3865d39c37d8323aea |
Confirmed that rduplain's fix WorksForMe (and makes sense to read, from the PoV of someone familiar with SSL and passingly acquainted with Ruby). |
Yes, thanks rduplain! Your fix works well. |
I am getting the following error
$ echo test | gist
SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
Changing the following suppressed the error, although I doubt it is a proper fix.
diff --git a/lib/gist.rb b/lib/gist.rb
index 6ecc10a..be5b119 100644
--- a/lib/gist.rb
+++ b/lib/gist.rb
@@ -119,7 +119,7 @@ module Gist
end
Also note the following, even though I am currently using commit 1c27da3 (v2.0.0).
$ gist --version
1.4.0
I think somebody forgot to build gist in commit 83bf891. This shouldn't affect the current issue however, as it was just a version bump from v1.4.0.
Possible relevant info:
$ ruby --version
ruby 1.9.2p0 (2010-08-18 revision 29036) [i686-linux]
The text was updated successfully, but these errors were encountered: