diff options
author | Philip Hazel <ph10@hermes.cam.ac.uk> | 2006-02-23 12:41:22 +0000 |
---|---|---|
committer | Philip Hazel <ph10@hermes.cam.ac.uk> | 2006-02-23 12:41:22 +0000 |
commit | 4730f9424e0addeb902cc842508eea3f47a131ca (patch) | |
tree | 1aecf2add22e0e8206feb5ca136d626c765d294e /doc/doc-txt/NewStuff | |
parent | ed72ace5f09d07c620b96efaf72d328d6e7439be (diff) |
Make server prompts available in $auth<n> when plaintext is running as a
client.
Diffstat (limited to 'doc/doc-txt/NewStuff')
-rw-r--r-- | doc/doc-txt/NewStuff | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 14e08ee78..c807d931b 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.89 2006/02/22 15:08:20 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.90 2006/02/23 12:41:22 ph10 Exp $ New Features in Exim -------------------- @@ -74,6 +74,19 @@ PH/11 If retry_interval_max is set greater than 24 hours, it is quietly reset and H retry rules, and it seems reasonable to require a retry at least once a day. +PH/12 When the plaintext authenticator is running as a client, the server + challenges are now checked to ensure they are valid base64 strings. The + default action on failure is to abort the authentication. However, if + client_ignore_invalid_base64 is set true, invalid responses are ignored. + +PH/13 When the plaintext authenticator is running as a client, the challenges + from the server are placed in $auth1, $auth2, etc. as they are received. + Thus, the challege that is received in response to sending the first + string (with the AUTH command) can be used in the expansion of the second + string, and so on. Currently, up to 3 challenge strings are available in + this way. If an invalid base64 string is received when client_ignore_ + invalid_base64 is set, an empty string is put in the $auth<n> variable. + Version 4.60 ------------ |