> Is this something that can be protected from future breakage with a > few new tests somewhere in t/t5559 (which may also involve touching > t/lib-httpd.sh as well)? I am not sure about that. That required only for local access to the cert and key from curl пн, 20 мар. 2023 г. в 20:23, Junio C Hamano <gitster@xxxxxxxxx>: > > "Stanislav Malishevskiy via GitGitGadget" <gitgitgadget@xxxxxxxxx> > writes: > > > From: Stanislav Malishevskiy <s.malishevskiy@xxxxxxxxxx> > > > > Basically git work with default curl ssl type - PEM. But for support > > eTokens like SafeNet tokens via pksc11 need setup 'ENG' as sslcert type > > and as sslkey type. So there added additional options for http to make > > that possible. > > > > Signed-off-by: Stanislav Malishevskiy <stanislav.malishevskiy@xxxxxxxxx> > > --- > > > http.c | 12 ++++++++++++ > > 1 file changed, 12 insertions(+) > > Thanks. > > Is this something that can be protected from future breakage with a > few new tests somewhere in t/t5559 (which may also involve touching > t/lib-httpd.sh as well)?
