From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [PATCH] vnc: avoid deprecation warnings for SASL on OS X
Date: Fri, 4 Jun 2021 14:14:54 +0100 [thread overview]
Message-ID: <YLonThBK4yhIEgfL@redhat.com> (raw)
In-Reply-To: <155dcb87-c6ab-de58-e2cd-c6bfb478c56b@amsat.org>
On Fri, Jun 04, 2021 at 03:07:05PM +0200, Philippe Mathieu-Daudé wrote:
> On 6/4/21 2:09 PM, Paolo Bonzini wrote:
> > Apple has deprecated sasl.h functions in OS X 10.11. Therefore,
> > all files that use SASL API need to disable -Wdeprecated-declarations.
> > Remove the only use that is outside vnc-auth-sasl.c and add the
> > relevant #pragma GCC diagnostic there.
> >
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > ---
> > ui/vnc-auth-sasl.c | 20 ++++++++++++++++++++
> > ui/vnc-auth-sasl.h | 1 +
> > ui/vnc.c | 10 ++--------
> > 3 files changed, 23 insertions(+), 8 deletions(-)
> >
> > diff --git a/ui/vnc-auth-sasl.c b/ui/vnc-auth-sasl.c
> > index df7dc08e9f..cf65a0b161 100644
> > --- a/ui/vnc-auth-sasl.c
> > +++ b/ui/vnc-auth-sasl.c
> > @@ -28,10 +28,30 @@
> > #include "vnc.h"
> > #include "trace.h"
> >
> > +/*
> > + * Apple has deprecated sasl.h functions in OS X 10.11. Therefore,
> > + * files that use SASL API need to disable -Wdeprecated-declarations.
> > + */
> > +#ifdef CONFIG_DARWIN
> > +#pragma GCC diagnostic warning "-Wdeprecated-declarations"
> > +#endif
> > +
> > /* Max amount of data we send/recv for SASL steps to prevent DOS */
> > #define SASL_DATA_MAX_LEN (1024 * 1024)
> >
> >
> > +bool vnc_sasl_server_init(Error **errp)
> > +{
> > + int saslErr = sasl_server_init(NULL, "qemu");
>
> What is the plan once these functions are removed for the
> distribution? Is there a replacement or should we start warning
> the users here and in docs/system/deprecated.rst VNC/SASL will
> go away soon?
VNC/SASL isn't going anywhere. It is fully supported on Linux and a
critically important security feature.
If macOS removes SASL, that sucks for macOS users, but then in that case I
assume HomeBrew/MacPorts would bring it back to life, because SASL is an
important feature for many apps.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-06-04 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 12:09 [PATCH] vnc: avoid deprecation warnings for SASL on OS X Paolo Bonzini
2021-06-04 13:07 ` Philippe Mathieu-Daudé
2021-06-04 13:14 ` Daniel P. Berrangé [this message]
2021-06-04 13:32 ` Peter Maydell
2021-06-09 12:24 ` Daniel P. Berrangé
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=YLonThBK4yhIEgfL@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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
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;
as well as URLs for NNTP newsgroup(s).