Package: gsasl
Version: 1.8.0-6
Severity: normal
Dear Maintainer,
I noticed while trying to use GSSAPI in msmtp that gsasl does not seem
to support it, despite claims to the contrary in the description.
My smarthost is responding to EHLO with 'AUTH GSSAPI' on port 25 and
'AUTH LOGIN PLAIN GSSAPI' after negotiating STARTTLS, so I am sure
that's not the issue.
Using gsasl, however, I get this:
$ gsasl msa.wesleyan.edu 25
Trying ‘msa.wesleyan.edu’...
220 msa.wesleyan.edu ESMTP WesMSA; Thu, 6 Nov 2014 13:21:36 -0500
EHLO [127.0.0.1]
250-msa.wesleyan.edu Hello al.wesleyan.edu [129.133.22.76], pleased to
meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 65000000
250-AUTH GSSAPI
250-STARTTLS
250-DELIVERBY
250 HELP
STARTTLS
220 2.0.0 Ready to start TLS
EHLO [127.0.0.1]
250-msa.wesleyan.edu Hello al.wesleyan.edu [129.133.22.76], pleased to
meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 65000000
250-AUTH LOGIN PLAIN GSSAPI
250-DELIVERBY
250 HELP
AUTH PLAIN
334
After which it prompts me for PLAIN auth credentials.
Furthermore, it seems gsasl is throughly confused by the crazy ideas I'm
throwing around:
$ gsasl msa.wesleyan.edu 25 -m GSSAPI
Trying ‘msa.wesleyan.edu’...
220 msa.wesleyan.edu ESMTP WesMSA; Thu, 6 Nov 2014 13:25:54 -0500
EHLO [127.0.0.1]
250-msa.wesleyan.edu Hello al.wesleyan.edu [129.133.22.76], pleased to meet
you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 65000000
250-AUTH GSSAPI
250-STARTTLS
250-DELIVERBY
250 HELP
STARTTLS
220 2.0.0 Ready to start TLS
EHLO [127.0.0.1]
250-msa.wesleyan.edu Hello al.wesleyan.edu [129.133.22.76], pleased to meet
you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 65000000
250-AUTH LOGIN PLAIN GSSAPI
250-DELIVERBY
250 HELP
AUTH GSSAPI
gsasl: mechanism unavailable: Unknown SASL mechanism
$gsasl msa.wesleyan.edu 25 --client-mechanisms
This client supports the following mechanisms:
ANONYMOUS EXTERNAL LOGIN PLAIN SECURID NTLM DIGEST-MD5 CRAM-MD5 SCRAM-SHA-1
SAML20 OPENID20
$gsasl msa.wesleyan.edu 25 --server-mechanisms
This server supports the following mechanisms:
ANONYMOUS EXTERNAL LOGIN PLAIN SECURID DIGEST-MD5 CRAM-MD5 SCRAM-SHA-1
SAML20 OPENID20
I looked in the source for the gsasl package, and could find nothing
that indicated GSSAPI had been intentially disabled.
Any help would be appreciated.
Yours, C. Morgan Hamill
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gsasl depends on:
ii dpkg 1.17.21
ii install-info 5.2.0.dfsg.1-5
ii libc6 2.19-12
ii libgnutls-deb0-28 3.3.8-3
ii libgsasl7 1.8.0-6
gsasl recommends no packages.
gsasl suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
