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: Sun, 13 May 2018 01:42:38 +0200 [thread overview]
Message-ID: <20180513014238.44d7da6f@alma-ubu> (raw)
In-Reply-To: <87bmdmpflm.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On Fri, 11 May 2018 14:00:05 +0200
ludo@gnu.org (Ludovic Courtès) wrote:
> >> ‘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?
>
> The developer’s reasoning makes sense to me (IOW, the CVEs should be
> against the applications that don’t handle exceptions properly rather
> than against OpenCV itself.)
>
> You can use the ‘lint-hidden-cve’ property to explicitly hide them.
> Please add a comment with the URL above as well.
I added a new patch including documentation about lint-hidden-cve:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31437
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-05-12 23:43 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 ` [bug#30801] " Björn Höfling
2018-05-11 12:00 ` Ludovic Courtès
2018-05-12 23:42 ` Björn Höfling [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=20180513014238.44d7da6f@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.