| KNOWNBUGS (66494) | KNOWNBUGS (80785) |
|---|---|
| 1 2 3 K N O W N B U G S I N S E N D M A I L 4 5 6The following are bugs or deficiencies in sendmail that I am aware of 7but which have not been fixed in the current release. You probably 8want to get the most up to date version of this from ftp.sendmail.org --- 21 unchanged lines hidden (view full) --- 30* Null bytes are not handled properly in headers. 31 32 Sendmail should handle full binary data. As it stands, it handles 33 all values in the body, but only 0x01-0x80 and 0xA0-0xFF in 34 the header. Notably missing is 0x00, which would require a major 35 restructuring of the code -- for example, almost no C library support 36 could be used to handle strings. 37 | 1 2 3 K N O W N B U G S I N S E N D M A I L 4 5 6The following are bugs or deficiencies in sendmail that I am aware of 7but which have not been fixed in the current release. You probably 8want to get the most up to date version of this from ftp.sendmail.org --- 21 unchanged lines hidden (view full) --- 30* Null bytes are not handled properly in headers. 31 32 Sendmail should handle full binary data. As it stands, it handles 33 all values in the body, but only 0x01-0x80 and 0xA0-0xFF in 34 the header. Notably missing is 0x00, which would require a major 35 restructuring of the code -- for example, almost no C library support 36 could be used to handle strings. 37 |
| 38* Header checks are not called if header value is too long. 39 40 If the value of a header is longer than 1250 (MAXNAME + MAXATOM - 6) 41 characters or it contains a single word longer than 256 (MAXNAME) 42 characters then no header check is done even if one is configured for 43 the header. 44 |
|
| 38* Duplicate error messages. 39 40 Sometimes identical, duplicate error messages can be generated. As 41 near as I can tell, this is rare and relatively innocuous. 42 43* $c (hop count) macro improperly set. 44 45 The $c macro is supposed to contain the current hop count, for use --- 142 unchanged lines hidden (view full) --- 188 189 Since SIGALRM does not interrupt an RPC call for hard mounted 190 NFS file systems, it is impossible to implement a timeout on a file 191 open operation. Therefore, while the NFS server is not responding, 192 attempts to open a file on that server will hang. Systems with 193 local mail delivery and NFS hard mounted home directories should be 194 avoided, as attempts to open the forward files could hang. 195 | 45* Duplicate error messages. 46 47 Sometimes identical, duplicate error messages can be generated. As 48 near as I can tell, this is rare and relatively innocuous. 49 50* $c (hop count) macro improperly set. 51 52 The $c macro is supposed to contain the current hop count, for use --- 142 unchanged lines hidden (view full) --- 195 196 Since SIGALRM does not interrupt an RPC call for hard mounted 197 NFS file systems, it is impossible to implement a timeout on a file 198 open operation. Therefore, while the NFS server is not responding, 199 attempts to open a file on that server will hang. Systems with 200 local mail delivery and NFS hard mounted home directories should be 201 avoided, as attempts to open the forward files could hang. 202 |
| 196* Race condition for delivery to setuid files | 203* Race condition for delivery to set-user-id files |
| 197 198 Sendmail will deliver to a fail if the file is owned by the DefaultUser | 204 205 Sendmail will deliver to a fail if the file is owned by the DefaultUser |
| 199 or has the setuid bit set. Unfortunately, some systems clear that bit | 206 or has the set-user-id bit set. Unfortunately, some systems clear that bit |
| 200 when a file is modified. Sendmail compensates by resetting the file mode 201 back to it's original settings. Unfortunately, there's still a 202 permission failure race as sendmail checks the permissions before locking 203 the file. This is unavoidable as sendmail must verify the file is safe 204 to open before opening it. A file can not be locked until it is open. 205 206* Potential denial of service attack with AutoRebuildAliases 207 208 There is a potential for a denial of service attack if the 209 AutoRebuildAliases option is set as a user can kill the sendmail process 210 while it is rebuilding the aliases file leaving it in an inconsistent 211 state. This option and it's use is deprecated and will be removed from a 212 future version of sendmail. 213 | 207 when a file is modified. Sendmail compensates by resetting the file mode 208 back to it's original settings. Unfortunately, there's still a 209 permission failure race as sendmail checks the permissions before locking 210 the file. This is unavoidable as sendmail must verify the file is safe 211 to open before opening it. A file can not be locked until it is open. 212 213* Potential denial of service attack with AutoRebuildAliases 214 215 There is a potential for a denial of service attack if the 216 AutoRebuildAliases option is set as a user can kill the sendmail process 217 while it is rebuilding the aliases file leaving it in an inconsistent 218 state. This option and it's use is deprecated and will be removed from a 219 future version of sendmail. 220 |
| 214$Revision: 8.43.16.1 $, Last updated $Date: 2000/09/28 00:45:37 $ | 221$Revision: 8.43.16.2 $, Last updated $Date: 2001/07/31 22:42:46 $ |