From: Milan Broz <gmazyland@gmail.com>
To: Simone Bossi <simone.bossi2@studenti.unimi.it>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] How to report security issues
Date: Mon, 12 Oct 2015 16:47:45 +0200 [thread overview]
Message-ID: <561BC811.7070900@gmail.com> (raw)
In-Reply-To: <72c0a69c1e7d5.561bdb0d@studenti.unimi.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/12/2015 04:08 PM, Simone Bossi wrote:
> Is there a private way to report security issues?
For cryptsetup? We do not have a private list.
If it is not anything really bad I would prefer to report
it as a public bug.
Otherwise you can send an encrypted mail to me as maintainer
(using the key which I signed this mail).
You can also report security bug to cryptsetup component
in Fedora bugzilla (bugzila.redhat.com)
Red Hat security team will contact me as maintainer anyway.
Milan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWG8gRAAoJENmwV3vZPpj8rhcP/1OmdghA414TjX0sPoKQM7ha
V3oG+/3qCyyvFt8k77Wxd2ed4e9lkxgnP9ier4nkpID9eTYPEPYf1dcjWZsY9LDm
bfTOQXCdudmsiM2ujP5DH371oI/k08ZenfR80xsy0xX9RT9GWEogBwRaJOuBpBAe
tgcfPHtcwBtCt7nnpo4/rvsFpUp2d+OSBOaNrijrdQ5kPsa8+w/MGpSMI5WeJfLB
ssRzNdmNajz+bxr4XMNBUJuN8NvhtXJdmq4xl1FR4BvXx5A0NcgWp04iGiT0Cww2
KWZuuezNAWhDZJeIGap1lVl4X3bSTHZ415+7FqUGpNCQFyhdVr43cd6DPXNenGUt
MUzIRsCcWXY2ecX46sM1zWok1cfBdqPdBFFPqjMS3qrBqdtLA8iDSCjGIYmCyFC9
ovbgVA61wPj0o0+xpwVePWLZTFeCw8oUq8UbApZXLs12Efc9fBZCxPlIadv7Y5Ha
YIivPrQNx0K0ON5iaCtjY+znDgZNdCSBivcqapxMMi/RLSrHR/MRGEFPiia+0GBK
bfSP5trxx2aAbhPTqPq2UjOtZ3e1x1u+NBWt0pLEyrWTUIA1VoFuNH4wFmw+I4/B
P0NGaG2CMEOsSiDvI5dk3bxKiQzR1XmprikM/+wlXYFUK0R4YOlZBbL1Zv/totEa
qUro+fx+jLdncv+/t1hH
=RTsC
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-10-12 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 14:08 [dm-crypt] How to report security issues Simone Bossi
2015-10-12 14:47 ` Milan Broz [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=561BC811.7070900@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=simone.bossi2@studenti.unimi.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