On Tue, 13 Jan 2015 12:10:47 +0100 Andreas K. Huettel wrote:
> Am Dienstag 13 Januar 2015, 07:54:16 schrieb Andrew Savchenko:
> > Are you sure? The simplest Shor's factorisation machine was already
> > built and published in open press:
> > http://arxiv.org/abs/quant-ph/0112176
> > This was done 14
On Tue, 13 Jan 2015 13:36:01 +0100 Chí-Thanh Christopher Nguyễn
wrote:
> Andrew Savchenko schrieb:
> > On Mon, 12 Jan 2015 19:44:46 +0100 Kristian Fiskerstrand wrote:
> >> Shor's would be effective against discrete logs (including ECC) as
> >> well, so wouldn't be applicable to this selection. For
Andrew Savchenko schrieb:
On Mon, 12 Jan 2015 19:44:46 +0100 Kristian Fiskerstrand wrote:
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
Am Dienstag 13 Januar 2015, 07:54:16 schrieb Andrew Savchenko:
> On Mon, 12 Jan 2015 18:48:41 + Ciaran McCreesh wrote:
> > On Mon, 12 Jan 2015 19:44:46 +0100
> >
> > Kristian Fiskerstrand wrote:
> > > Shor's would be effective against discrete logs (including ECC) as
> > > well, so wouldn't b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/13/2015 05:58 AM, Andrew Savchenko wrote:
> 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
>>> wrote:
One is
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
> > wrote:
> >>
> >> One issue with DSA/ElGamal is the requirement for a random k
> >> value while signing/encrypting,
> >
> >
On Mon, 12 Jan 2015 18:48:41 + Ciaran McCreesh wrote:
> On Mon, 12 Jan 2015 19:44:46 +0100
> Kristian Fiskerstrand wrote:
> > 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 li
On Sun, 11 Jan 2015 18:37:36 -0800 Brian Dolbec wrote:
> When you add a signing subkey, that subkey then becomes the default key
> used for signing with. If you have more than one signing subkey, the
> default can be set in gnupg.conf without editing the key. Otherwise
> you must specify which ke
On Mon, Jan 12, 2015 at 1:48 PM, Ciaran McCreesh
wrote:
> On Mon, 12 Jan 2015 19:44:46 +0100
> Kristian Fiskerstrand wrote:
>> 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
On Mon, 12 Jan 2015 19:44:46 +0100
Kristian Fiskerstrand wrote:
> 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.
We're not post-quantum, an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/12/2015 07:29 PM, Rich Freeman wrote:
> On Mon, Jan 12, 2015 at 1:06 PM, Kristian Fiskerstrand
> wrote:
>>
>> One issue with DSA/ElGamal is the requirement for a random k
>> value while signing/encrypting,
>
> Thanks - that was very informat
On Mon, Jan 12, 2015 at 1:06 PM, Kristian Fiskerstrand 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
po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/12/2015 02:34 AM, Brian Dolbec wrote:
> On Sun, 11 Jan 2015 12:06:18 -0500 Rich Freeman
> wrote:
>
>> On Sun, Jan 11, 2015 at 11:43 AM, Brian Dolbec
>> wrote:
>>> Of the remaining devs, only 16 keys total pass the GLEP 63
>>> requirements.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/12/2015 02:55 AM, Rich Freeman wrote:
> On Sun, Jan 11, 2015 at 8:34 PM, Brian Dolbec
> wrote:
>> But for the rest, yes, you don't need gkeys to create your key,
>> It is just most people seem to know little about using gpg, so
>> creating the
On Sun, 11 Jan 2015 18:37:36 -0800
I forgot to mention:
You enter the primary key fingerprint and keyid
into LDAP, not the signing subkey.
The subkeys information will be imported along
with the primary key. Even if you change signing subkey later, there
should be no need to edit LDAP with t
On Sun, 11 Jan 2015 20:55:29 -0500
Rich Freeman wrote:
> On Sun, Jan 11, 2015 at 8:34 PM, Brian Dolbec
> wrote:
> > I added a little more info to the First-Use wiki page, I included a
> > link to a great webpage about setting up gpg keys.
> >
> > https://alexcabal.com/creating-the-perfect-gpg-k
On Sun, Jan 11, 2015 at 8:34 PM, Brian Dolbec wrote:
> But for the rest, yes, you don't need gkeys to create your key, It is
> just most people seem to know little about using gpg, so creating the
> template where you just filled out name, email, password, makes it easy.
Makes sense. I can alway
On Sun, 11 Jan 2015 12:06:18 -0500
Rich Freeman wrote:
> On Sun, Jan 11, 2015 at 11:43 AM, Brian Dolbec
> wrote:
> > Of the remaining devs, only 16 keys total pass the GLEP 63
> > requirements. More info can be found in the First-Use wiki page
> > [4]
>
> If you just create a gpg key with
Rich Freeman wrote:
> Would this work:
> gpg --gen-key
> option 2 - DSA and Elgamal
Watch that entropy.
//Peter
On Sun, Jan 11, 2015 at 11:43 AM, Brian Dolbec wrote:
> Of the remaining devs, only 16 keys total pass the GLEP 63
> requirements. More info can be found in the First-Use wiki page [4]
If you just create a gpg key with 5yr expiry and otherwise-default
options, typing a larger number into the
There is a short, "First USE" intro to using gkeys [4] in our wiki.
Notes:
Not all devs have seeds in the gentoo-devs.seeds file downloaded
during the install of gkeys. The log stating the devs with bad info
in LDAP can be viewed here [1]. There were 19 devs with conflicting
or missing
Hello all,
We're very pleased to announce the first official release of the Gentoo Keys
toolkit.
What is the Gentoo Keys project?
=
Gentoo Keys is a Python based project that aims to manage the OpenPGP keys
used for validation on users and Gentoo's infrastructure servers.
22 matches
Mail list logo
