Page MenuHome GnuPG

ciaby (ciaby)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Saturday

  • Clear sailing ahead.

User Details

User Since
Mar 27 2017, 4:47 PM (275 w, 2 d)
Availability
Available

Recent Activity

Oct 1 2014

ciaby added a comment to T1732: Don't break existing keys larger than 4k.

Judging by the lack of reply, I assume that this bug won't be fixed, correct?

Oct 1 2014, 3:41 AM · Not A Bug, Debian, Bug Report, gnupg

Sep 26 2014

ciaby reopened T1732: Don't break existing keys larger than 4k as "Open".
Sep 26 2014, 6:23 PM · Not A Bug, Debian, Bug Report, gnupg
ciaby added a comment to T1732: Don't break existing keys larger than 4k.

I read that. It says that RSA-2048 keys are going to be safe until 2030. Doesn't
sound like a lot to me... Considering the average human lifespan, I could be
around until 2070. So, nope, not enough.
If all the emails I sent till now have been intercepted and stored (which seems
to be the case according to Snowden), using a RSA-2048 key simply means that all
my private correspondence is going to be public (or at least accessible) in 16
years time. Now, the only thing I'm asking is to raise the amount of secure
memory allocated by GnuPG to 128k to let people use key sizes up to 16384,
something that was even allowed by the keygen itself.

Sep 26 2014, 6:23 PM · Not A Bug, Debian, Bug Report, gnupg
ciaby added a comment to T1732: Don't break existing keys larger than 4k.

By the way, is this all bullshit?
AES-256 == RSA-15360 / DSA-15360 (NIST)
http://csrc.nist.gov/groups/SMA/ispab/documents/minutes/2006-03/E_Barker-
March2006-ISPAB.pdf

AES=256 == RSA-15424 / DSA-15424 (ECRYPT2)
http://www.ecrypt.eu.org/documents/D.SPA.20.pdf

Sep 26 2014, 4:36 AM · Not A Bug, Debian, Bug Report, gnupg

Sep 25 2014

ciaby added a comment to T1732: Don't break existing keys larger than 4k.

Ok, got it. So I can just throw away my key and make a new one?
Fantastic. Thanks a lot.
Sounds a lot like "640K ought to be enough for anybody".
So long, and thanks for all the good work on GnuPG (seriously).

Sep 25 2014, 10:11 PM · Not A Bug, Debian, Bug Report, gnupg
ciaby added a comment to T1732: Don't break existing keys larger than 4k.

Yes, I know how to change the code and make it work on _my_ machine.
There is the tiny problem that everyone else has to do it, too.
Can we make that change the default? I don't see a big problem in using 64k or
128k instead of 32k of secure memory.
By the way, 16k of key size is ridiculous now, but it's going to be kind of
standard in the not so distant future. Or am I too paranoid? :)
Just trying to have a GnuPG key which is future-proof, also taking in
consideration the possible use of quantum computers in the future.

Sep 25 2014, 9:17 PM · Not A Bug, Debian, Bug Report, gnupg
ciaby added projects to T1732: Don't break existing keys larger than 4k: gnupg, Bug Report, Debian.
Sep 25 2014, 1:31 AM · Not A Bug, Debian, Bug Report, gnupg