So, as you most hackers love your privacy, and even if you are not a hacker, we still LOVE those big GPG keys. Only issue is that today, computers are growing stronger and stronger. In the GnuPG package, hardcoded is a limit of 4096-bit key generation. Ergo you cannot create a key bigger than 4,096-bit. So, we took the source of that nice ol’ GnuPG 1.4.12 and modified it to hard code a top limit of 16,384-bit key generation. Any program can handle the understanding of this but not generate.
So, here are the instructions of getting, compiling and creating your new wonderful key. First off, some preparations. since we are going to compile the modified source code, you will need some dependencies (libraries).
sudo apt-get install libgcrypt11-dev libgpg-error-dev libassuan-dev libksba-dev subversion automake checkinstall
That should get all of the ones you need. If we missed some, or by default you don’t have the ones we think you do, please update us to modify this post.
wget http://hackingdefined.org/tools/gnupg-1.4.12.tar.gz tar xfv gnupg-1.4.12.tar.gz cd gnugp-1.4.12 ./configure
This should configure the ‘make’ options which we are now going to run, and post on screen if you have any dependencies needed which are not installed.
make make check sudo make install
And that should be it as far as installation goes. Now let’s get to generate our new signature using ‘gpg –gen-key’. Follow the steps and you should now see that the maximum limit has now been removed. After creating your new GPG key, sign it using your old key to verify identity and don’t forget to upload it to ‘keyserver.pgp.com’ so that others can find your key.
About The Author |
||
 |
Yuval Nativ |
|
| Yuval (tisf) Nativ is the manager of the Cyber Assualt Division of See-Security Technologies. As part of his job he is the manager of the Hacking Defined Experts program, a penetration tester, security researcher and developer. If you like to find him in our offices, just ask where Moriarty is… | ||