After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 562339 - Selection of authentication method is incorrect
Selection of authentication method is incorrect
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: HTTP Transport
2.4.x
Other All
: Normal minor
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2008-11-26 14:22 UTC by Pontus Oldberg
Modified: 2008-12-01 09:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pontus Oldberg 2008-11-26 14:22:16 UTC
Please describe the problem:
When a server requests authentication it can send a list of methods (Basic, Digest, etc) that it supports. The client should choose the method with the highest security that it supports, i.e. if the client supports both Basic and Digest authentication and the server accepts both Basic and Digest the client should choose Digest.

Today it selects Basic authentication per default.

Steps to reproduce:
1. Connect to a server that announces support for both Basic and Digest auth.
2. when "authenticate" is received call soup_auth_authenticate with the correct credentials.
3. Observe what method has been selected (I used wireshark)


Actual results:
Basic authentication is selected and carried out.

Expected results:
I expected libsoup to select the Digest authentication method.

Does this happen every time?
Yes it is reproducible.

Other information:
Comment 1 Dan Winship 2008-11-28 23:14:08 UTC
whoops. it was sorting the auth types backwards, so it ended up picking the weakest auth first rather than the strongest. :-/

fixed in trunk. will eventually make it into libsoup 2.24.3 as well. thanks for the bug report.
Comment 2 Pontus Oldberg 2008-12-01 09:40:05 UTC
Tested ! Now works as expected.
Thanks a lot Dan.

/Pontus