Daniel Stenberg via curl-library wrote: > On Mon, 10 Nov 2025, Peter Krefting wrote: > >> At $DAYJOB, we use libcurl to monitor both ends of this, using a (slightly >> patched) librtmp version with a (slightly patched) libcurl. > > Thanks for this feedback. It helps! > > There is a growing concern for the wellfare of librtmp, the third party > library curl needs for RTMP. They don't do releases since many years back, > then don't > seem to have test cases and there have been no commits in their git > repository within the last year.
What is there to release? The RTMP protocol has been frozen for at least a decade. The primary use case of RTMP was in Adobe Flash, which was EOL 2020. As such there should be no new use cases for it. But also there's no reason any existing users will see any changes. And unfortunately there are many existing users, and by its nature, anyone still using it is most likely in a proprietary system which is unlikely to be upgraded to a more open and standard protocol. > This, combined with the fact that curl also has *zero* test cases for RTMP > makes it one of the weakest areas of curl. Testing has always been a pain because the RTMP servers are proprietary. Really the only usable open source RTMP server code is in librtmp itself. > If we are to keep RTMP in curl, we need to get in there and improve this. And > I don't mean that I will do it all myself on my copious spare time. The biggest problem going forward is that RTMPE uses crypto algorithms that are deprecated and won't be available in newer crypto libraries. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
