Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Stefano Mandelli" <algebrato@lcm.mi.infn.it>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Extend the PATH buffer to 2048 for RTSP
Date: Wed, 7 Aug 2024 09:03:01 +0200
Message-ID: <20240807070301.nxz6653ipwtspr3y@nanos8.pcteor1.mi.infn.it> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]

Recently, I have been experiencing an increasing number
of user that use ffmpeg to retrive RTSP stream from
personal mediaproxies (e.g. MediaMtx) with
authorization based on JWT. The current length of PATH
does not permit to insert the token in the URL failing
the authorization with no possibilities to get the video.

VLC has just modified the RSTP max URL length, and it
permits to use token inside the URL.

For these reasons, I propose this patch to extend the
PATH buffer from 1024 to 2048 in order to use tokens
and the authorization process based on JWT.


diff --git a/libavformat/rtsp.c b/libavformat/rtsp.c
index 19b93df839..d8f45cf8d5 100644
--- a/libavformat/rtsp.c
+++ b/libavformat/rtsp.c
@@ -1727,7 +1727,7 @@ void ff_rtsp_close_connections(AVFormatContext *s)
 int ff_rtsp_connect(AVFormatContext *s)
 {
     RTSPState *rt = s->priv_data;
-    char proto[128], host[1024], path[1024];
+    char proto[128], host[1024], path[2048];
     char tcpname[1024], cmd[MAX_URL_SIZE], auth[128];
     const char *lower_rtsp_proto = "tcp";
	 int port, err, tcp_fd;

-- 
	 .''`.	Stefano Mandelli
	: :' :	GitHub:  algebrato 
	`. `'   Discord: Algebrato#0039
	  `-	

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

             reply	other threads:[~2024-08-07  7:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07  7:03 Stefano Mandelli [this message]
2024-08-08 16:09 ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240807070301.nxz6653ipwtspr3y@nanos8.pcteor1.mi.infn.it \
    --to=algebrato@lcm.mi.infn.it \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git