From: "François Perrad" <francois.perrad@gadz.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot <buildroot@busybox.net>
Subject: Re: [Buildroot] [PATCH] package/vsftpd: fix build with libressl
Date: Wed, 18 Aug 2021 09:01:15 +0200 [thread overview]
Message-ID: <CAB0FRssnm9aW6OmD9upQjEz+gLGTZzWs6BawLtkMX4RHOF4w1A@mail.gmail.com> (raw)
In-Reply-To: <92ad8dbd-77c2-6a5c-6ca2-b91b5632a1a0@mind.be>
[-- Attachment #1.1: Type: text/plain, Size: 2207 bytes --]
Le mar. 17 août 2021 à 22:55, Arnout Vandecappelle <arnout@mind.be> a
écrit :
>
>
> On 15/08/2021 15:52, Francois Perrad wrote:
> > Fixes the following error:
> > ssl.c: In function 'ssl_init':
> > ssl.c:98:18: error: 'SSL_OP_NO_TLSv1_3' undeclared (first use in this
> function); did you mean 'SSL_OP_NO_TLSv1_1'?
> >
> > in ssl.h (libressl), the definition of SSL_OP_NO_TLSv1_3 is under the
> condition LIBRESSL_HAS_TLS1_3 or LIBRESSL_INTERNAL
> >
> > with libopenssl, this definition is unconditional
> >
> > this issue appears with vsftpd 3.0.4
> >
> > Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> > ---
> > package/vsftpd/vsftpd.mk | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/package/vsftpd/vsftpd.mk b/package/vsftpd/vsftpd.mk
> > index 8daf07c62..e36ba299c 100644
> > --- a/package/vsftpd/vsftpd.mk
> > +++ b/package/vsftpd/vsftpd.mk
> > @@ -41,7 +41,7 @@ VSFTPD_LIBS += -lpam
> > endif
> >
> > define VSFTPD_BUILD_CMDS
> > - $(TARGET_MAKE_ENV) $(MAKE) CC="$(TARGET_CC)"
> CFLAGS="$(TARGET_CFLAGS)" \
> > + $(TARGET_MAKE_ENV) $(MAKE) CC="$(TARGET_CC)"
> CFLAGS="$(TARGET_CFLAGS) -DLIBRESSL_HAS_TLS1_3" \
>
> I don't think this is how the libressl feature flags are supposed to be
> used. I
> think you're supposed to patch opensslfeatures.h before building libressl.
> AFAIU, the flags are indented to tell client applications which features
> are
> available in the library, so vsftpd could do something like
>
> #ifdef LIBRESSL_HAS_TLS1_3
> ... do something with SSL_OP_NO_TLSv1_3
> #endif
>
> So I think a better solution would be to patch libressl to enable the two
> feature flags (TLS1_3 and DTLS1_2).
>
> But I could be wrong, of course.
>
>
Arnout,
well, I wrote this PR
https://github.com/libressl-portable/openbsd/pull/124/files
what do you think about it ?
François
Regards,
> Arnout
>
>
> > LDFLAGS="$(TARGET_LDFLAGS)" LIBS="$(VSFTPD_LIBS)" -C $(@D)
> > endef
> >
> >
> _______________________________________________
> buildroot mailing list
> buildroot@busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
[-- Attachment #1.2: Type: text/html, Size: 3686 bytes --]
[-- Attachment #2: Type: text/plain, Size: 145 bytes --]
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-08-18 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 13:52 [Buildroot] [PATCH] package/vsftpd: fix build with libressl Francois Perrad
2021-08-17 20:55 ` Arnout Vandecappelle
2021-08-18 7:01 ` François Perrad [this message]
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=CAB0FRssnm9aW6OmD9upQjEz+gLGTZzWs6BawLtkMX4RHOF4w1A@mail.gmail.com \
--to=francois.perrad@gadz.org \
--cc=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.