From: Junio C Hamano <gitster@pobox.com>
To: David Timber <dxdt@dev.snart.me>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v1 1/1] send-mail: add client certificate options
Date: Thu, 26 Feb 2026 08:41:25 -0800 [thread overview]
Message-ID: <xmqqo6lb4fuy.fsf@gitster.g> (raw)
In-Reply-To: <319bf98c-52df-4bf9-b157-e4bc2bf087d6@dev.snart.me> (David Timber's message of "Sat, 21 Feb 2026 18:16:52 +0900")
David Timber <dxdt@dev.snart.me> writes:
> I'm just trying to expose what's possible with the Perl SSL interface to
> the user as much as possible. Paranoid people(like me who would want to
> set up mtual vertification to deter bot attacks) would want both PEM and
> PKCS12 because major implementations including Thunderbird and K-9 only
> accept PKCS#12(imposed by the application and imposed by the operating
> system - Android, respectively) while the openssl x509 stack is more
> suited for PEM(separate cert and key).
>
> It's a niche, I know. But something tells me that you'd want to push
> this feature forward. Thank you for the rest of the comments. Will come
> back with the revised patch that I hope may unconfuse you. Good to know
> the project is in good hands.
OK, please incorporate what you explained here in the commit log
message and/or in-code comment, in order to help future readers of
"git log -p". I'd prefer to see it done before the topic goes out
of my short-term memory ;-)
Thanks.
next prev parent reply other threads:[~2026-02-26 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 8:17 [PATCH v1 0/1] send-email: add client certificate options David Timber
2026-02-20 8:17 ` [PATCH v1 1/1] send-mail: " David Timber
2026-02-20 16:35 ` Junio C Hamano
2026-02-21 9:16 ` David Timber
2026-02-26 16:41 ` Junio C Hamano [this message]
2026-03-02 3:16 ` [PATCH v2 0/1] send-email: " David Timber
2026-03-02 3:16 ` [PATCH v2 1/1] " David Timber
2026-03-02 16:43 ` Junio C Hamano
2026-03-04 14:39 ` David Timber
2026-02-20 16:19 ` [PATCH v1 0/1] " 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=xmqqo6lb4fuy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dxdt@dev.snart.me \
--cc=git@vger.kernel.org \
/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