[FFmpeg-user] How to have a secure UDP BroadCast

Alessandro Molon alex.molon at vision247.com
Wed Aug 19 12:08:56 EEST 2020

I would go for SRT as well.

It doesn't have a proper username/password method, but the passphrase mechanism implement should suffice.
In addition to this it can also compensate a lot of network issues between transmitter and receiver that couldn't be compensated by UDP, and doesn't add a lot of latency like other authenticated protocols like RTMP or HLS.


-----Original Message-----
From: ffmpeg-user <ffmpeg-user-bounces at ffmpeg.org> On Behalf Of Dennis Mungai
Sent: 19 August 2020 10:05
To: FFmpeg user questions <ffmpeg-user at ffmpeg.org>
Subject: Re: [FFmpeg-user] How to have a secure UDP BroadCast

On Wed, 19 Aug 2020, 11:53 Alessandro Molon, <alex.molon at vision247.com>

> You simply cannot. UDP delivery is not meant to do that.
> There are other protocols that support authentication 😊
> If you provide a little bit more about what are your needs I can 
> suggest some.
> Alex
> -----Original Message-----
> From: ffmpeg-user <ffmpeg-user-bounces at ffmpeg.org> On Behalf Of hassan 
> shatnawi
> Sent: 02 October 2017 09:12
> To: ffmpeg-user at ffmpeg.org
> Subject: [FFmpeg-user] How to have a secure UDP BroadCast
> Dears,
> How to have a secure connection with username and password while 
> broadcasting "UPD"
> I've use this command
> ffmpeg -f dshow -video_size 1280x720 -rtbufsize 702000K -framerate 30 
> -i video="Video (00-0 Pro Capture Quad HDMI)" -r 30 -threads 4 -vcodec
> libx264 -crf 0 -preset ultrafast -f mpegts "udp:// 
> username:password at"
> but it didn't work can you advice me plz.
> Thanks in advance.
> *Hassan Shatnawi*
> Software Developer
> *Software Development Department*
> *Haupshy Establishment for Electronics*
> Al Madina Al Monawara St. bld 31 | P.O.Box 6875 Amman 11118, Jordan.
> *T: *+962 6 5820 927* | F: *+962 6 5820 926* | M: *+962 78 5792 096
> *E*: hassan at haupshy.com *|* www.haupshy.com 
> _______________________________________________

The closest there is to your requirements, ie:

(a). A container format with support for timestamps such as mpegts

(b). Capabilities similar to UDP

Would be Haivision's SRT, which FFmpeg supports if enabled on build time via --enable-libsrt.

SRT allows for optional encryption, whose details can be viewed via ffmpeg -h protocol=srt.

Note that depending on your application requirements, you'll need to ensure that your receiver can handle SRT input, OR use FFmpeg to handle SRT TX and Rx in the network segment where such content security is desired.

Hope that helps.

ffmpeg-user mailing list
ffmpeg-user at ffmpeg.org

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

More information about the ffmpeg-user mailing list