Re: [Exim] CRAM-MD5 fudging

On Tue, 11 Mar 2003, John Jetmore wrote:

> That said, I still think it could be done with plaintext:
>
> radius_cram:
> driver: plaintext
> public_name = CRAM-MD5
> server_prompts = $auth_cram_challenge

this is perfectly doable. i did something like this when i wanted to
move cram-md5 back in postgres. the simple trick lies in a macro :>

sth like this:

CHALLENGE = $tod_epoch@$primary_hostname

[...]

cram:
driver = plaintext
public_name = CRAM-MD5
server_prompts = CHALLENGE
server_condition = <some lookup to which you pass CHALLENGE>

the only problem with that is that it needs server_prompts to be
expandable. when i had this issue (july 2002), it was not, i don't
know if it is since, but its pretty obvious to change it to be.


--
[-]
... and the rest is silence.