Re: Secure Relaying -- a start
- To: debian-user@lists.debian.org
- Subject: Re: Secure Relaying -- a start
- From: Hendrik Sattler <sattler2000@gmx.de>
- Date: Mon, 03 Feb 2003 03:09:22 +0100
- Message-id: <[🔎] b1kj0i$6l8$04$1@news.t-online.com>
- References: <20030130033007$3c4f@gated-at.bofh.it> <20030130063007$00b6@gated-at.bofh.it> <20030130235101$55ed@gated-at.bofh.it> <20030131012010$7c7b@gated-at.bofh.it> <20030131141009$70c4@gated-at.bofh.it> <20030131195014$7615@gated-at.bofh.it> <20030131215008$2ffd@gated-at.bofh.it> <20030201204012$2771@gated-at.bofh.it> <20030202022006$4a52@gated-at.bofh.it> <20030202143016$2760@gated-at.bofh.it> <20030203020009$77a4@gated-at.bofh.it>
will trillich wrote:
> now if you get PAM to cooperate, let me know.
>
> plain:
> driver = plaintext
> public_name = BASIC
> # $3 =~ s/:/::/g
> # if pam($2:$3) {yes} else {no}
> server_condition = ${if pam{$2:${sg{$3}{:}{::}}}{yes}{no}}
> server_set_id = $2
>
> when i do the interactive tests, it works like a champ; when i
> try it from a remote client, nothing doing. still working on
> it...
For PAM, either run exim daemon as root or search at google for "pam_exim".
BTW: For plain auth it should be "public_name = PLAIN".
HS
Reply to: