From: Igor Gnatenko <i.gnatenko.brain@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Ruben Kerkhof <ruben@rubenkerkhof.com>
Subject: [PATCH] send-email: If the ca path is not specified, use the defaults
Date: Wed, 15 Jan 2014 21:31:11 +0400 [thread overview]
Message-ID: <1389807071-26746-1-git-send-email-i.gnatenko.brain@gmail.com> (raw)
From: Ruben Kerkhof <ruben@rubenkerkhof.com>
I use gmail for sending patches.
If I have the following defined in my ~/.gitconfig:
[sendemail]
smtpencryption = tls
smtpserver = smtp.gmail.com
smtpuser = ruben@rubenkerkhof.com
smtpserverport = 587
and try to send a patch, this fails with:
STARTTLS failed! SSL connect attempt failed with unknown error
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
verify failed at /usr/libexec/git-core/git-send-email line 1236.
Tested-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
Signed-off-by: Ruben Kerkhof <ruben@rubenkerkhof.com>
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1043194
---
git-send-email.perl | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/git-send-email.perl b/git-send-email.perl
index 3782c3b..689944f 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -1095,7 +1095,8 @@ sub ssl_verify_params {
}
if (!defined $smtp_ssl_cert_path) {
- $smtp_ssl_cert_path = "/etc/ssl/certs";
+ # use the OpenSSL defaults
+ return (SSL_verify_mode => SSL_VERIFY_PEER());
}
if ($smtp_ssl_cert_path eq "") {
--
1.8.4.2
next reply other threads:[~2014-01-15 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 17:31 Igor Gnatenko [this message]
2014-01-15 19:26 ` [PATCH] send-email: If the ca path is not specified, use the defaults Junio C Hamano
[not found] ` <7AD1C6ED-6177-415D-B342-D1FEA9F810B4@rubenkerkhof.com>
2014-01-15 21:30 ` Junio C Hamano
2014-01-15 21:50 ` Ruben Kerkhof
2014-01-15 21:50 ` Jonathan Nieder
2014-01-16 23:19 ` Junio C Hamano
2014-01-17 4:21 ` Kyle J. McKay
2014-01-17 18:14 ` Junio C Hamano
2014-01-17 23:34 ` Kyle J. McKay
2014-01-26 17:17 ` Ramkumar Ramachandra
2014-01-27 16:02 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1389807071-26746-1-git-send-email-i.gnatenko.brain@gmail.com \
--to=i.gnatenko.brain@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ruben@rubenkerkhof.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).