From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] zoom concerns
Date: Thu, 2 Apr 2020 17:17:14 +0200 [thread overview]
Message-ID: <1cb6f0e6-9ea6-0b46-d2dd-b324fcdbbb8f@gentoo.org> (raw)
In-Reply-To: <CACfyCdVi_gnMZfOPJvQhwpkJzZ4LvQQu2YVWf4hsO3HT-eGKaA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1302 bytes --]
Hi,
it's true that zoom is currently getting a lot of attention. It all
started with the iOS application using Facebook SDK to provide login
through Facebook and their TOS/privacy statement.
That triggered a lot of (security) researchers who are currently sitting
at home like most people in western world with a lot of time. If
upstream will address all problems this will become one of the best
(free-)audited conference software available ;-)
For this discussion please keep in mind that there are multiple versions
for different platforms. Not every platform is affected by all reported
problems.
Regarding zoom and Gentoo: net-im/zoom doesn't require any special
handling in Gentoo. Package is not even marked stable. We have a lot of
vulnerable packages...
If problems will get confirmed for the available Linux version and
upstream won't provide a fix within ~12 months (depends on severity of
reported vulnerabilities) we maybe decide to last-rite or apply a mask
to force user awareness through forced unmask action in case they need
that software. But again, this software isn't special and doesn't
require further discussion from our P.O.V.
--
Regards,
Thomas Deutschmann / Gentoo Security Team
fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2020-04-02 15:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 0:18 [gentoo-dev] zoom concerns Alessandro Barbieri
2020-04-02 0:47 ` Rich Freeman
2020-04-02 12:11 ` Ulrich Mueller
2020-04-07 10:35 ` Alessandro Barbieri
2020-04-07 11:22 ` Thomas Deutschmann
2020-04-02 0:53 ` Alec Warner
2020-04-02 2:13 ` William Kenworthy
2020-04-02 5:51 ` Michał Górny
2020-04-02 8:01 ` Michal Prívozník
2020-04-04 14:57 ` Kent Fredric
2020-04-05 16:11 ` Samuel Bernardo
2020-04-06 13:08 ` Kent Fredric
2020-04-06 22:55 ` Samuel Bernardo
2020-04-07 6:23 ` Kent Fredric
2020-04-07 15:26 ` [gentoo-dev] The importance of having an ebuild Samuel Bernardo
2020-04-07 8:48 ` [gentoo-dev] zoom concerns Ulrich Mueller
2020-04-07 10:47 ` Thomas Deutschmann
2020-04-08 6:34 ` Kent Fredric
2020-04-08 17:39 ` Peter Stuge
2020-04-09 5:09 ` Kent Fredric
2020-04-07 13:44 ` Roy Bamford
2020-04-08 6:45 ` Kent Fredric
2020-04-04 14:52 ` Kent Fredric
2020-04-02 11:55 ` Ulrich Mueller
2020-04-02 15:17 ` Thomas Deutschmann [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=1cb6f0e6-9ea6-0b46-d2dd-b324fcdbbb8f@gentoo.org \
--to=whissi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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