From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30801-done@debbugs.gnu.org
Subject: [bug#30801] Add opencv
Date: Fri, 11 May 2018 11:51:24 +0200 [thread overview]
Message-ID: <20180511115124.0f8ed3d9@alma-ubu> (raw)
In-Reply-To: <878t8sxzdi.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
On Thu, 10 May 2018 00:01:13 +0200
ludo@gnu.org (Ludovic Courtès) wrote:
> > * gnu/packages/image-processing.scm (opencv): New variable.
>
> Applied!
Thanks.
> ‘guix lint’ reports this:
>
> gnu/packages/image-processing.scm:201:2: opencv@3.4.1: probably
> vulnerable to CVE-2018-7712, CVE-2018-7713, CVE-2018-7714
>
> Could you take a look? It could be that 3.4.2 is around the corner
> and we’ll just update at that point; if not, we may have to apply
> upstream patches for these issues.
While finally linting, I noticed these too. OpenCV claims this is not
an issue:
https://github.com/opencv/opencv/issues/10998
Should we mention it somewhere in the code? Is there a formal process
to hide or comment specific CVEs?
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-05-11 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 16:58 [bug#30801] [PATCH 0/1] Add opencv Björn Höfling
2018-03-13 17:07 ` [bug#30801] [PATCH 1/1] gnu: " Björn Höfling
2018-03-15 21:04 ` [bug#30801] [PATCH 0/1] " Ludovic Courtès
2018-03-31 22:26 ` Björn Höfling
2018-04-01 12:21 ` Ludovic Courtès
2018-05-07 18:35 ` [bug#30801] " Björn Höfling
2018-05-09 22:01 ` bug#30801: " Ludovic Courtès
2018-05-11 9:51 ` Björn Höfling [this message]
2018-05-11 12:00 ` [bug#30801] " Ludovic Courtès
2018-05-12 23:42 ` Björn Höfling
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180511115124.0f8ed3d9@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=30801-done@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).