From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 7/8] package/rtmpdump: Fix compilation issues with openssl 1.1.x
Date: Mon, 04 Feb 2019 21:11:30 +0100 [thread overview]
Message-ID: <87ef8ns499.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <8a058fda-b1f8-4ed6-9570-b47669b37d8a@mind.be> (Arnout Vandecappelle's message of "Mon, 4 Feb 2019 19:15:19 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> On 04/02/2019 11:06, Peter Korsgaard wrote:
>>>>>>> "Patrick" == Patrick Havelange <patrick.havelange@essensium.com> writes:
>>
>> > From: Vadim Kochan <vadim4j@gmail.com>
>> > Upstream is dead, other distros use gnutls exclusively,
>> > so patch is not sent upstream.
>>
>> So shouldn't we do the same?
>>
>> What other distributions exactly?
> IIRC I checked at least Fedora and Debian, possibly also Gentoo and/or Arch.
Ok, which probably makes sense for a binary distribution.
It is not exactly clear to me where this patch comes from. Googling
around I see a very similar patch on this github repo:
https://github.com/JudgeZarbi/RTMPDump-OpenSSL-1.1
But that repo has an open issue about a crash in the handshake handling
(code that gets changed by this patch) and the README states:
I modified a few of the files in the librtmp directory to conform to the
new getters and setters in OpenSSL 1.1.0. I don't claim to be a security
expert, and neither have I had any experience with OpenSSL in a
programming sense, so I'm not sure exactly if it's correct, but it
compiles and seems to work for what I use it for.
Which does not sound very reassuring to me, so I have instead pushed a
patch to drop the openssl support for rtmpdump.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-02-04 20:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 9:39 [Buildroot] [PATCH v7 1/8] package/libshout: Add support for openssl 1.1.x Patrick Havelange
2019-01-29 9:39 ` [Buildroot] [PATCH v7 2/8] package/nut: " Patrick Havelange
2019-01-29 15:43 ` Peter Korsgaard
2019-01-29 9:39 ` [Buildroot] [PATCH v7 3/8] package/pound: Fix build with OpenSSL 1.1.x Patrick Havelange
2019-01-29 15:49 ` Peter Korsgaard
2019-01-30 14:08 ` Arnout Vandecappelle
2019-02-05 1:25 ` Matthew Weber
2019-02-05 9:19 ` Patrick Havelange
2019-02-05 9:48 ` Peter Korsgaard
2019-02-05 16:01 ` [Buildroot] [External] " Matthew Weber
2019-01-29 9:39 ` [Buildroot] [PATCH v7 4/8] mariadb: use host-openssl from buildroot-system Patrick Havelange
2019-02-04 9:27 ` Peter Korsgaard
2019-02-04 20:10 ` Peter Seiderer
2019-02-04 20:22 ` Peter Korsgaard
2019-01-29 9:39 ` [Buildroot] [PATCH v7 5/8] Introduce the variable BR2_TOOLCHAIN_HAS_UCONTEXT Patrick Havelange
2019-02-04 10:03 ` Peter Korsgaard
2019-01-29 9:39 ` [Buildroot] [PATCH v7 6/8] package/thrift: bump to 0.12.0, add support for openssl 1.1.x Patrick Havelange
2019-01-29 9:39 ` [Buildroot] [PATCH v7 7/8] package/rtmpdump: Fix compilation issues with " Patrick Havelange
2019-02-04 10:06 ` Peter Korsgaard
2019-02-04 18:15 ` Arnout Vandecappelle
2019-02-04 20:11 ` Peter Korsgaard [this message]
2019-01-29 9:39 ` [Buildroot] [PATCH v7 8/8] libopenssl: bump version to 1.1.1a Patrick Havelange
2019-02-04 20:57 ` Peter Korsgaard
2019-02-04 22:12 ` Peter Korsgaard
2019-02-04 22:43 ` Vadim Kochan
2019-01-29 15:42 ` [Buildroot] [PATCH v7 1/8] package/libshout: Add support for openssl 1.1.x Peter Korsgaard
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=87ef8ns499.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox