Am Montag, den 26.07.2010, 08:27 -0500 schrieb Dan White:
> >But as i said, i just had a quick look at the code.
>
> I think you'll cause some issues with changing the SASL service name, since
> things like the kerberos principal that's used, and the sasl config file
> name are influenced by it.
On 26/07/10 03:27 -0500, Syren Baran wrote:
>Am Samstag, den 24.07.2010, 00:43 -0500 schrieb Dan White:
>> >
>> >Would be a nice and clean solution to set the service name for "imapd -s"
>> >to "imaps" and just use a second pam file for that service.
>>
>> The service name that gets passed to sasla
Am Samstag, den 24.07.2010, 00:43 -0500 schrieb Dan White:
> >
> >Would be a nice and clean solution to set the service name for "imapd -s"
> >to "imaps" and just use a second pam file for that service.
>
> The service name that gets passed to saslauthd is taken from the
> sasl_server_init call ins
On 22/07/10 06:56 -0500, Syren Baran wrote:
>Am Donnerstag, den 22.07.2010, 13:27 +0200 schrieb Josef Karliak:
>> Hi, thanks for tip. I used your entries now (I had anything else in
>> pam.d's imap config).
>
>> celer:/etc/pam.d # testsaslauthd -u user -p goodsystempass -s imap 0: OK
>> "Success."
Am Donnerstag, den 22.07.2010, 13:27 +0200 schrieb Josef Karliak:
> Hi,
>thanks for tip. I used your entries now (I had anything else in
> pam.d's imap config).
> celer:/etc/pam.d # testsaslauthd -u user -p goodsystempass -s imap
> 0: OK "Success."
If you DONT want this, remove the line "auth
Hi,
thanks for tip. I used your entries now (I had anything else in
pam.d's imap config).
Command "testsaslauthd" seem to be happy :
celer:/etc/pam.d # testsaslauthd -u user -p badimapspass -s imap
0: NO "authentication failed"
celer:/etc/pam.d # testsaslauthd -u user -p goodimapspass -s
Am Mittwoch, den 21.07.2010, 21:07 +0200 schrieb Josef Karliak:
> Hi,
>thanks for tip.
>I've rebuilded pwdfile from src and installed it.
>File /etc/pam.d/imap is :
I just use the following entries:
#dont need account
account required pam_permit.so
#check username/passwd
authsuffi
On 21/07/10 21:07 +0200, Josef Karliak wrote:
> All this procedure is because users has weak passwords, so we let them
> in the company (using only IMAP), but if anybody want to has IMAPS from
> outside of company (from home, etc...) we force him to create strong
> password and let IMAPS autho
Huh,
discovered your next mail :)
But didn't helped, I'look over internet too. Again...And waith for
kicks to the right way :)
Thanks.
J.K.
Cituji Syren Baran :
Am Mittwoch, den 21.07.2010, 09:47 +0200 schrieb Josef Karliak:
Hi everybody,
we need to use another acounts (from extr
Hi,
thanks for tip.
I've rebuilded pwdfile from src and installed it.
File /etc/pam.d/imap is :
#%PAM-1.0
auth includecommon-auth
authsufficient pam_pwdfile.so pwdfile /var/spool/imap/imaps_users
account includecommon-account
password includecommon-password
Am Mittwoch, den 21.07.2010, 09:47 +0200 schrieb Josef Karliak:
> Hi everybody,
> we need to use another acounts (from extra file) for authorization for
> IMAPS (from outside of company). IMAP stays authorized over saslauthd
> (pam). How to solve this ? I'm out of the ideas :-/.
Try libpam-pwdfile
Hi everybody,
we need to use another acounts (from extra file) for authorization for
IMAPS (from outside of company). IMAP stays authorized over saslauthd
(pam). How to solve this ? I'm out of the ideas :-/.
Using:
cyrus-sasl-crammd5-2.1.21-18.11.41
cyrus-sasl-2.1.21-18.11.41
cyrus-sasl-3
12 matches
Mail list logo
