rtsp-client: Avoid reuse of channel numbers for interleaved
authorDavid Svensson Fors <davidsf@axis.com>
Fri, 17 Aug 2018 07:54:27 +0000 (09:54 +0200)
committerSebastian Dröge <sebastian@centricular.com>
Wed, 29 Aug 2018 11:46:01 +0000 (14:46 +0300)
commita2e182c3b41cf7a149d099d65e32ac512dd60dc3
treeb746855635c8e92c411716d354afefb6937949c0
parent990d5dde86a04f64b9da663eb54e2e46bd8b6c69
rtsp-client: Avoid reuse of channel numbers for interleaved

If a (strange) client would reuse interleaved channel numbers in
multiple SETUP requests, we should not accept them. The channel
numbers are used for looking up stream transports in the
priv->transports hash table, and transports disappear from the table
if channel numbers are reused.

RFC 7826 (RTSP 2.0), Section 18.54, clarifies that it is OK for the
server to change the channel numbers suggested by the client.

https://bugzilla.gnome.org/show_bug.cgi?id=796988
gst/rtsp-server/rtsp-client.c
tests/check/gst/client.c