Displaying 3 results from an estimated 3 matches for "rfc821".
Did you mean:
rfc822
2004 Jan 20
0
short analysys of qmail integer overflow bug - let there be light
...if (ch != '\r') { put("\r"); state = 0; }
}
put(&ch);
}
}
One can see that pos is later used as an index for memory location. And
that's all folks. :) I say it is exploitable. Just an opinion.
Cheers to all,
Alin-Adrian Anton.
Below there is a small rfc821 line too long implementing patch:
--- qmail-smtpd.c.orig Mon Jun 15 13:53:16 1998
+++ qmail-smtpd.c Mon Jan 19 23:29:35 2004
@@ -1,3 +1,15 @@
+/*
+* This is a patched version of qmail, implementing RFC 821 regarding
text line limitations.
+* Developed by Alin-Adrian Anton
(aanton@rev...
2017 Sep 07
3
login case sensitivity
Am 07.09.2017 um 20:07 schrieb hw:
> Gordon Messmer wrote:
>> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote:
>>> This was always
>>> problematic because DNS hostnames and email addresses in the RFC
>>> standards were case insensitive
>>
>>
>> Not quite.? SMTP is required to treat the "local-part" of the RCPT
>> argument as
2017 Sep 07
0
login case sensitivity
...quot;Smith". However, exploiting the
> case sensitivity of mailbox local-parts impedes interoperability and
> is discouraged. Mailbox domains follow normal DNS rules and are
> hence not case sensitive.
>
Thanks for the clarification to my original email. I misremembered
RFC821 and thought it was for the entire part..
Commands and replies are not case sensitive. That is, a command or
reply word may be upper case, lower case, or any mixture of upper and
lower case. Note that this is not true of mailbox user names. For
some hosts the user name is case sensit...