Hello, for me GSSAPI works for very long time with imapd. I utilize it with MIT Kerberos. I have in imapd.conf
sasl_pwcheck_method: saslauthd sasl_keytab: FILENAME.keytab sasl_minimum_layer: 128 sasl_mech_list: PLAIN GSSAPI GS2-KRB5 GS2-IAKERB also the process saslauthd -a pam -r running and in /etc/pam.d/imap: account sufficient pam_krb5.so no_user_check auth sufficient pam_krb5.so no_user_check To my knowledge CRAM-MD5 and DIGEST-MD5 require storing the passwords in clear text on the server, which MIT Kerberos does not do, but other Kerberos implementations might do. So I do not know how can CRAM-MD5/DIGEST-MD5 be offered together with GSSAPI. Also I have many patches, but I do not think any of it is relevant. For testing I invoke (there are no -u and -p parameters): imtest -t "" -m GSSAPI mail.aegee.org Greeting // Дилян -----Original Message----- From: Khalid MK via Info <[email protected]> Reply-To: Info <[email protected]> To: Info <[email protected]> Subject: GSSAPI Authentication is broken in 3.10.x 3.12.x Date: 25/09/26 11:30:39 As reported by @MartySvec in https://github.com/cyrusimap/cyrus-imapd/issues/6454, GSSAPI authentication is also affected by cbe7d93 in 3.10.x and 3.12.x. The patch fixes the issue, but is it OK to use this patch until the issue is officially resolved? Thanks Khalid MK Cyrus / Info / seediscussions +participants +delivery options Permalink ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T925f0a19740e6693-M57eeb58e00e231654d467986 Delivery options: https://cyrus.topicbox.com/groups/info/subscription
