Some nasty SIP-clients sends only \n instead of \r\n (malicious SIP scanners). We shouldn't crash
on these packets.
Actually I'm not sure about how we should handle this. RFC 3261 states clearly that the only allowed line terminator is CRLF, however previous RFC 2543 does allows line endings with CR, LF, and CRLF. Also some people advise allowing CRLF, CR, and LF as a line delimiters when parsing incoming SIP packets (see http://www.networksorcery.com/enp/protocol/sip.htm).
What other thinks about this? Is it worth fixing at all?
Hello All!
Some nasty SIP-clients sends only \n instead of \r\n (malicious SIP scanners). We shouldn't crash on these packets.
Actually I'm not sure about how we should handle this. RFC 3261 states clearly that the only allowed line terminator is CRLF, however previous RFC 2543 does allows line endings with CR, LF, and CRLF. Also some people advise allowing CRLF, CR, and LF as a line delimiters when parsing incoming SIP packets (see http://www.networksorcery.com/enp/protocol/sip.htm).
What other thinks about this? Is it worth fixing at all?