You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@serf.apache.org by "Branko Čibej (Jira)" <ji...@apache.org> on 2025/08/06 05:14:00 UTC
[jira] [Resolved] (SERF-207) Digest authn provider should verify received parameters.
[ https://issues.apache.org/jira/browse/SERF-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Branko Čibej resolved SERF-207.
-------------------------------
Fix Version/s: serf-trunk
Resolution: Fixed
> Digest authn provider should verify received parameters.
> --------------------------------------------------------
>
> Key: SERF-207
> URL: https://issues.apache.org/jira/browse/SERF-207
> Project: serf
> Issue Type: Improvement
> Affects Versions: serf-1.4.0, serf-trunk, serf-1.3.10
> Reporter: Branko Čibej
> Assignee: Branko Čibej
> Priority: Minor
> Fix For: serf-trunk
>
> Attachments: SERF-207.2.patch, SERF-207.patch
>
>
> The Digest authentication scheme supports only {{algorithm=MD5}} and {{qop=auth}} parameters. This is equivalent to what's supported by HTTPd's {{mod_auth_digest}}, so feature-wise that's fine.
> However, the code never checks those parameters in the response header and just blindly generates an authn response using those assumed values. If those parameters are different, the authentication will fail in any case, but we could avoid one roundtrip with a weakly-hashed password by checking the parameter values and failing early.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)