Hi Quanah,
configure: error: conditional "OPAQUE_INTERNAL" was never
defined. Usually this means the macro was only invoked
conditionally. >>
Could it be fixed?
There's a PR for it waiting on review.
I confirm that PR fixes the build.
But that would also mean the build you are doing is From master
branch which is where the 2.2 work is being done. You want to build
from the Cyrus-SASL-2.1 branch.
Oh yes, indeed!
I've just grabbed the Cyrus-SASL-2.1 branch and confirm it works fine.
Looking at the changes, #773 (digestmd5: Drop the mechanism) is marked
for the 2.1.29 release but it seems that it is only in the master branch.
Testing the InterNetNews (INN) news server with Cyrus SASL, and
comparing the available mechanisms between different Cyrus SASL
versions, I see that 2.1.28 and 2.1.29 have the same.
However, master 2.2 no longer advertises DIGEST-MD5 and OTP.
Does it sound good to you (notably for OTP)?
Will DIGEST-MD5 only be removed in the 2.2 branch?
I totally understand DIGEST-MD5 is removed (obsoleted by RFC 6331 in
2011, which suggests to use the mechanisms of the SCRAM family). Do you
think SCRAM-SHA-256 (or SCRAM-SHA-512?) are good candidates for
"long-term" use?
I'm trying to find out a replacement to propose in an RFC erratum for
RFC 4643 (NNTP extension for authentication) which states:
https://datatracker.ietf.org/doc/html/rfc4643
To ensure interoperability, client and server implementations of this
extension MUST implement the [DIGEST-MD5] SASL mechanism.
Another mechanism should be mentioned. Is there a mandatory mechanism
to support in SASL implementations? (RFC 4422 for SASL does not seem to
indicate one)
--
Julien ÉLIE
« Loving unconditional means forgiving and learning to live with his
imperfections. Because in the end you'll realize that it is what you
love the most. »
------------------------------------------
Cyrus: SASL
Permalink: https://cyrus.topicbox.com/groups/sasl/T204776f7816270a8-Me14cf63b1fbd232afc852b52
Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription
