public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] First release of Gentoo Keys
Date: Tue, 13 Jan 2015 07:58:54 +0300	[thread overview]
Message-ID: <20150113075854.51dfb8e536b1b9bd15f9ec4e@gentoo.org> (raw)
In-Reply-To: <54B4161E.9070502@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

On Mon, 12 Jan 2015 19:44:46 +0100 Kristian Fiskerstrand wrote:
> On 01/12/2015 07:29 PM, Rich Freeman wrote:
> > On Mon, Jan 12, 2015 at 1:06 PM, Kristian Fiskerstrand
> > <k_f@gentoo.org> wrote:
> >> 
> >> One issue with DSA/ElGamal is the requirement for a random k
> >> value while signing/encrypting,
> > 
> > Thanks - that was very informative.  I guess the thing that makes
> > me more concerned about RSA is that Shor's algorithm makes it
> > quite possible that it will be defeated at some point in the
> > future, perhaps without public disclosure.
> 
> Shor's would be effective against discrete logs (including ECC) as
> well, so wouldn't be applicable to this selection. For post-quantum
> asymmetric crypto we'd likely need e.g a lattice based primitive.

Why not to use post-quantum signing together with a traditional one?
app-crypt/codecrypt is already in tree and provides an GnuPG-like
solution based on post-quantum cryptography.

It would be no harm to use this solution together with GnuPG, e.g.
have two detached signatures: a traditional RSA-4096 and a
post-quantum one.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-01-13  4:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 13:05 [gentoo-dev] First release of Gentoo Keys Pavlos Ratis
2015-01-11 16:43 ` Brian Dolbec
2015-01-11 17:06   ` Rich Freeman
2015-01-11 18:32     ` Peter Stuge
2015-01-12  1:34     ` Brian Dolbec
2015-01-12  1:55       ` Rich Freeman
2015-01-12  2:37         ` Brian Dolbec
2015-01-12  2:46           ` Brian Dolbec
2015-01-13  4:43           ` Andrew Savchenko
2015-01-12 18:00         ` Kristian Fiskerstrand
2015-01-12 18:06       ` Kristian Fiskerstrand
2015-01-12 18:29         ` Rich Freeman
2015-01-12 18:44           ` Kristian Fiskerstrand
2015-01-12 18:48             ` Ciaran McCreesh
2015-01-12 19:11               ` Rich Freeman
2015-01-13  4:54               ` Andrew Savchenko
2015-01-13 11:10                 ` Andreas K. Huettel
2015-01-13 13:59                   ` Andrew Savchenko
2015-01-13  4:58             ` Andrew Savchenko [this message]
2015-01-13  8:46               ` Kristian Fiskerstrand
2015-01-13 12:36               ` Chí-Thanh Christopher Nguyễn
2015-01-13 13:58                 ` Andrew Savchenko

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=20150113075854.51dfb8e536b1b9bd15f9ec4e@gentoo.org \
    --to=bircoph@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