Bug 370239 - CRAM-MD5 authentication does not work
Summary: CRAM-MD5 authentication does not work
Status: RESOLVED WORKSFORME
Alias: None
Product: sieveeditor
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Laurent Montel
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-10-07 10:06 UTC by Steffen Lehmann
Modified: 2018-10-28 03:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Lehmann 2016-10-07 10:06:29 UTC
The CRAM-MD5 authentication mechanism calculates wrong digest, so it cannot be used for authentication.

Reproducible: Always

Steps to Reproduce:
1. Take the example user name and password from RFC 2195, and configure it in KSieve, using CRAM-MD5 authentication and a sieve server of your choice:
Username: tim
Password: tanstaaftanstaaf
2. When receiving the challenge from server, change it in your code for testing to the one as in this RFC before calculating the response:
Challenge: <1896.697170952@postoffice.reston.mci.net>
3. Look at the digest sent by KSieve. The calculated digest by KSieve is different from the one in this RFC! It must be
b913a602c7eda7a495b4e6e7334d3890.

Actual Results:  
Log in using CRAM-MD5 is not possible. The server sends an error response, but no visible indication about any problem is given by the GUI.

Expected Results:  
Calculate the correct digest.
Comment 1 Laurent Montel 2016-12-01 06:23:53 UTC
Where in code did you see that "The calculated digest by KSieve" is uncorrected ?
Comment 2 Laurent Montel 2017-07-08 14:35:32 UTC
wait info
Comment 3 Andrew Crouthamel 2018-09-28 02:35:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-28 03:15:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!