Actually PAM here is broke for exim working against authentication heres hw
I have cracked it.
login:
driver = plaintext
public_name = LOGIN
server_condition = "${if and {{!eq{$1}{}}{!eq{$2}{}} \
{crypteq{$2}{${extract{1}{:} \
{${lookup{$1}lsearch{/etc/exim.passwd}{$value}{*:*}}}}}}}{1}{0}}"
server_prompts = "Username:: : Password::"
server_set_id = $1
plain:
driver = plaintext
public_name = PLAIN
server_condition = "${if and {{!eq{$2}{}}{!eq{$3}{}} \
{crypteq{$3}{${extract{2}{:} \
where /etc/exim.passwd is copy of shadow passwd file with the following
ownership
-rw-rw---- 1 mail mail 3167 Dec 20 18:47 /etc/exim.passwd
I created the file by using
# cat /root/bin/eximpass.sh
#!/bin/sh
cp /etc/shadow /etc/exim.passwd.temp
chmod 600 /etc/exim.passwd.temp
chown mail:mail /etc/exim.passwd.temp
mv /etc/exim.passwd.temp /etc/exim.passwd
I got the idea from a previous posting in the EXIM mail lists so the credit
goes to whoever created that script <grin>
if PAM is otherwsie please please let me know
Regards
Nik Butler
Director Wired4Life Limited
[EMAIL PROTECTED]
07713 241 956
www.wired4life.org
----- Original Message -----
From: "hanasaki" <[EMAIL PROTECTED]>
To: "debian-user" <[email protected]>
Sent: Friday, December 28, 2001 2:59 AM
Subject: [Exim] Auth problems with PAM
> I am running Debian Woody and the exim 3.3 that comes with it. All
> client auth's fail. exim 3.3 worked fine when it was built and
> installed separately under Potato.
>
> I think there is a problem with my pam entries. I have checked the
> readme's and docs. What should the pam entries be?
> Thanks.
>
> --
> [EMAIL PROTECTED]
> Spam : def: It's not kosher.
>
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim
> details at http://www.exim.org/ ##
>
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>
