diff options
| author | Philip Hazel <ph10@hermes.cam.ac.uk> | 2005-03-29 15:53:12 +0000 |
|---|---|---|
| committer | Philip Hazel <ph10@hermes.cam.ac.uk> | 2005-03-29 15:53:12 +0000 |
| commit | f9b9210ed00d36e87538b5d4abe51c079826fb9c (patch) | |
| tree | 9a29df1d8fcb75c8be76313d266b09e196076c54 /doc | |
| parent | d1d97a7641e06d3372f2ded9e5cb1e97b86d3c40 (diff) | |
Fix non-check for read() error in sync check before writing banner.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/doc-txt/ChangeLog | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog index 4cb08c1dc..cf31d4690 100644 --- a/doc/doc-txt/ChangeLog +++ b/doc/doc-txt/ChangeLog @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.105 2005/03/29 15:19:25 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.106 2005/03/29 15:53:12 ph10 Exp $ Change log file for Exim from version 4.21 ------------------------------------------- @@ -108,6 +108,15 @@ PH/19 When an Exim process that is running as root has to create an Exim log run out. I reviewed all the other calls to fork(); they all seem to check for failure. +PH/20 When checking for unexpected SMTP input at connect time (before writing + the banner), Exim was not dealing correctly with a non-positive return + from the read() function. If the client had disconnected by this time, + the result was a log entry for a synchronization error with an empty + string after "input=" when read() returned zero. If read() returned -1 + (an event I could not check), uninitialized data bytes were printed. + There were reports of junk text (parts of files, etc) appearing after + "input=". + A note about Exim versions 4.44 and 4.50 ---------------------------------------- |