Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#38184 - Add HTTP digest authentication option to pacman

Attached to Project: Pacman
Opened by Chris Clark (clark800) - Wednesday, 18 December 2013, 19:23 GMT
Last edited by Allan McRae (Allan) - Monday, 06 January 2014, 04:55 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.2
Due in Version 4.2.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
It would be nice to be able to set HTTP digest usernames and passwords for custom pacman repos. This would make it easier to implement stores like the Android Marketplace where users can purchase packages. Also, it would be useful for companies that want to host their own repos with proprietary code.

Steps to Reproduce:
1. Add a custom pacman repo that requires digest authentication.
2. Run pacman -Sy (the repo fails do to lack of authentication)
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 06 January 2014, 04:55 GMT
Reason for closing:  Fixed
Additional comments about closing:  git commit 7146096
Comment by Dave Reisner (falconindy) - Wednesday, 18 December 2013, 19:43 GMT
This should already work

http://auser:somepass@server/....
Comment by Chris Clark (clark800) - Wednesday, 18 December 2013, 20:07 GMT
I can't get it to work. When I use that format, I can access the repo using:

curl --anyauth http://auser:somepass@server/

but the same URL does not work in the pacman.conf file when XferCommand is not set.
Comment by Dave Reisner (falconindy) - Wednesday, 18 December 2013, 20:15 GMT
Thanks for the hint -- looks like only basic auth is enabled by default. We can call curl_easy_setopt(curl, CURLOPT_HTTPAUTH, CURLAUTH_ANY) to allow all reponses to all forms of authentication, but I'm a little hesistent to open the proverbial floodgates. Checking with curl upstream to see what their opinion on this is...

Loading...