From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 3/3] crypto/crypto_user01.c: new test for information leak bug
Date: Mon, 17 Dec 2018 14:01:01 +0100 [thread overview]
Message-ID: <20181217130101.GA12026@rei.lan> (raw)
In-Reply-To: <20181211205243.GE221175@gmail.com>
Hi!
> Yes that sounds reasonable to me, please feel free to just put it under the
> newer CVE number. Thanks!
Pushed, thanks.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-12-17 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 6:03 [LTP] [PATCH v2 0/3] ltp: new test for crypto_user information leak bug Eric Biggers
2018-12-11 6:03 ` [LTP] [PATCH v2 1/3] lapi/cryptouser.h: add more declarations Eric Biggers
2018-12-11 6:03 ` [LTP] [PATCH v2 2/3] tst_netlink: inline functions in header Eric Biggers
2018-12-11 6:03 ` [LTP] [PATCH v2 3/3] crypto/crypto_user01.c: new test for information leak bug Eric Biggers
2018-12-11 12:32 ` Cyril Hrubis
2018-12-11 18:43 ` Eric Biggers
2018-12-11 19:15 ` Cyril Hrubis
2018-12-11 20:52 ` Eric Biggers
2018-12-17 13:01 ` Cyril Hrubis [this message]
2018-12-11 8:46 ` [LTP] [PATCH v2 0/3] ltp: new test for crypto_user " Richard Palethorpe
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=20181217130101.GA12026@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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