On 14-11-2018 18:04, Maarten de Vries wrote:
On Wed, 14 Nov 2018 at 17:51, Eli Schwartz <eschwartz@archlinux.org <mailto:eschwartz@archlinux.org>> wrote:
On 11/14/18 11:37 AM, Maarten de Vries wrote: > These patches add support for client certificates to alpm and pacman. > > This can already be achieved currently by setting an XferCommand, > but doing so significantly reduces the quality of the feedback pacman > gives during the downloads. Especially annoying are the 404 errors on > most database signature files, but that's not the only issue. > > I admit this is a bit of an edge case, but I find myself in the > situation where I have to download packages from a private repository > that requires a valid client certificate. I really want the nice regular > pacman feedback back though, so I figured I'd hack it in myself. Surely this can also be achieved by adding the certificate to your system certificate store?
No, that would work if I want to verify a self signed server certificate (or a server certificate issues by a private CA). But I need to present a client certificate to the server.
So, any thoughts on adding support for client certificates? Kind regards, Maarten de Vries