Skip to content

Conversation

@lemenkov
Copy link

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?

Some nasty SIP-clients sends only \n instead of \r\n. We shouldn't crash
on these packets.

Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
@kalta
Copy link
Member

kalta commented Oct 21, 2015

Maybe we could add a global config options, and accept that optionally if you activate it.
Global options are compiled and very fast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants