GSSAPI for sieve

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

is GSSAPI authorization supported by timsieved? It seems that either 
sieveshell (which I used to test GSSAPI for sieve) or timsieved itself 
failed to finish GSSAPI session correctly:

Nov 21 17:37:01 ****** imaps[98068]: login: dhcp250-232.****** 
[*.*.250.232] ****** GSSAPI+TLS User logged in

Nov 21 17:37:06 ****** sieve[98007]: badlogin: dhcp250-232.****** 
[*.*.250.232] ****** GSSAPI error base64 decoding string

[17:37][****@slayer:q3][~]$ klist
Credentials cache: FILE:/tmp/krb5cc_1001
         Principal: slayer@******

   Issued           Expires          Principal
Nov 21 17:30:00  Nov 22 03:30:04  krbtgt/KDC_DOMAIN@KDC_DOMAIN
Nov 21 17:32:34  Nov 22 03:30:04  imap/*********@KDC_DOMAIN
Nov 21 17:33:10  Nov 22 03:30:04  sieve/*********@KDC_DOMAIN

In the same time imap server authenticates users perfectly, also, I 
think, it could be a problem in SASL library - I have found some 
discussions about processing CR+LF in saslutil.c - but patch I used did 
not help.

If someone has working timsieved+GSSAPI?

pkg_info | grep cyrus
cyrus-imapd-2.3.13
cyrus-sasl-2.1.22_2

-- 
Oleg Gorokhov
System Administrator, Yandex
Tel.: +7 (495) 739-7000 (+7166)
----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux