I’ve just published a new article on Medium.com.
I’m lazy today, so I’ll just give you a link to it:
https://medium.com/@dSebastien/using-junit-5-with-spring-boot-2-kotlin-and-mockito-d5aea5b0c668
Enjoy!
Some notes about my current setup for GPG/PGP.
I’m currently using GnuPG: https://www.gnupg.org/ and in particular GPG4Win.
As usual, I like portable installs and GPG is no exception. I’ve uncompressed it in my tools folder (synchronized across my machines). By itself, the tool is portable, maybe Kleopatra isn’t but I don’t care too much.
By default, Gpg4win installs in two locations:
Here’s how my bash profile is configured to have GPG tools available:
# GPG/PGP # where the tool is installed export GPG4WIN_HOME=$TOOLS_HOME/Gpg4Win_3.0.1 export GPG_HOME=$GPG4WIN_HOME/GnuPG export KLEOPATRA_HOME=$GPG4WIN_HOME/Gpg4win append_to_path $GPG_HOME append_to_path $GPG_HOME/bin append_to_path $KLEOPATRA_HOME/bin_64 append_to_path $KLEOPATRA_HOME/bin # where it puts its files and looks for its configuration export GNUPGHOME=$HOME/.gnupg # create it otherwise it complains mkdir -p `echo $GNUPGHOME` alias gpg='gpg.exe' alias pgp='gpg' # who cares ;-) alias kleopatra='kleopatra.exe'
Here’s my current GPG configuration (~/.gnupg/gpg.conf). I’ve removed comments for stuff I don’t use for clarity, although I like to keep those in my actual configs):
# get rid of the copyright notice no-greeting # key server keyserver hkp://keys.gnupg.net # Ensure that stronger secure hash algorithms are used by default default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAMELLIA256 CAMELLIA192 CAMELLIA128 TWOFISH CAST5 ZLIB BZIP2 ZIP Uncompressed personal-digest-preferences SHA512 cert-digest-algo SHA512 # Enable the passphrase agent use-agent # Avoid locking files lock-never # Armor when exporting armor # Keyserver options keyserver-options auto-key-retrieve include-subkeys honor-keyserver-url honor-pka-record # Import/export options import-options import-clean export-options export-clean # Don't use key ids are those are unsafe (both short and long!) keyid-format none
With this configuration, I’ve forced the usage of stronger secure hash algorithms by default and also disabled key ids (short & long) since those are insecure. There’s nothing much to it.
First of all, I didn’t reinvent the wheel, I’ve mostly applied what Alex Cabal has described here, so thanks to him!
You might ask “Why not a simple key that does it all?”. Because in general, mixing signing and encryption keys is not a good idea, management & security wise. Firstly, different key types have different lifecycles. Secondly, it might just not be safe to do so.
Also, without this setup, if the keys I use on a daily bases were to be compromised, I wouldn’t have any other choice but to re-create everything from scratch (i.e., new identity!). With the configuration below I can just revoke a specific sub-key and create a new one, while keeping my identity.
Here’s the whole shabang.
First of all, create the key:
gpg --gen-key
Settings to use:
When selecting the passphrase, use a tool like Keepass, don’t choose the passphrase yourself, you’re not smart enough ;-).
Just to make sure:
gpg --edit-key [email protected] ... gpg> setpref SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAMELLIA256 CAMELLIA192 CAMELLIA128 TWOFISH CAST5 ZLIB BZIP2 ZIP Uncompressed gpg> save
Next, create a signing sub-key for code signing:
gpg --edit-key [email protected] ... gpg> addkey ... gpg> save
Settings:
Next, create an authentication sub-key for SSH authentication:
gpg --expert --edit-key [email protected] gpg>addkey ... gpg>save
Settings:
Generating a revocation certificate will allow me to later revoke this keypair if it is compromised. It must be kept safe because it can render my keys useless ;-)
gpg --output ./[email protected] --gen-revoke [email protected]
First export the private key:
gpg --export-secret-keys --armor [email protected] > [email protected]
Then export the public key:
gpg --export --armor [email protected] > [email protected]
Finally, you can export the sub-keys alone:
gpg --export-secret-subkeys [email protected] > /tmp/gpg/subkeys
We’ll see why afterwards.
Ideally, you should export your private key to a temporary in-memory file system. Alex proposed the following:
mkdir /tmp/gpg # create a temp folder sudo mount -t tmpfs -o size=1M tmpfs /tmp/gpg
Once that’s mounted, you can safely write there and remove the folder once you’re done.
Once exported, back-up those keys in a safe location (e.g., Keepass).
Once you’re 100% it’s backed-up, delete the secret key from the gpg keyring:
gpg --delete-secret-key [email protected]
Now re-import the sub-keys. With this you’ll only have the sub-keys at your disposal (and you don’t need more than that on a daily basis):
gpg --import /tmp/gpg/subkeys
So simple steps:
To verify that you didn’t mess up, go ahead and try to add a new sub-key; you shouldn’t be able to:
gpg --edit-key [email protected] gpg> addkey Secret parts of primary key are not available. gpg: Key generation failed: No secret key
That’s it!
Using Google! Err I mean like this: https://wiki.debian.org/Subkeys.
First re-import my whole key (i.e., master + sub-keys)
gpg --allow-secret-key-import --import
Second, edit the key and revoke the sub-key that I don’t want anymore:
gpg --edit-key [email protected] gpg> list # list the keys gpg> xyz # select the unwanted key gpg> revkey # generate a revocation certificate gpg> save
Once done, I can export/back-up the result and finally make sure to send the updated key to the key servers.
Once my key was ready, I’ve published it at various locations.
For starters I needed the full fingerprint (the 40 chars beauty):
gpg --fingerprint
In my case: 9AEC 7595 2F0F 8E52 65A8 4364 6448 ABB4 AEAD 81A2.
Just to be in the clear, if you need to share your key, always try to use the full fingerprint, certainly never the short version (8 hex chars one) nor the “long” (16 hex chars) since those are really unsafe.
First I sent the public key to the MIT key server using gpg:
gpg --send-keys [email protected]
Then I exported my public key to a file (ASCII-armored):
gpg --export --armor > dsebastien-pgp-key.asc
I then uploaded that file to my FTP, updated my about page to add the full fingerprint and a link to my public key. Then I added a blog post with the same information.
I’ve also sent an update on twitter the same. After that I’ve updated my Twitter bio to link to that tweet (optimizing character count :p).
Next up, I’ve uploaded the public key manually on Ubuntu’s key server.
Finally, I’ve updated my GitHub profile to add my PGP key.
I’ve also updated my git client configuration in order to make my life easier.
This tells git which key to use. BTW, don’t enable automatic commit signing. Sign tags instead.
Verifying signatures is a breeze with git.
In a later post, I’ll explain how I use my PGP keys with SSH, git and my Yubikey.
That’s all folks!
I’ve got a new PGP key.
My PGP key fingerprint is: 9AEC 7595 2F0F 8E52 65A8 4364 6448 ABB4 AEAD 81A2
You can find my public PGP key here: https://dsebastien.net/pgp/dsebastien-pgp-key.asc
If you’re using CrashPlan to backup data on your Synology NAS in headless mode, you’ve probably already had to go through this update nightmare. This is pretty regular unfortunately; each time an update arrives for CrashPlan, the package gets broken in various ways.
Basically, clicking the “update” button always leads to a couple of hours wasted :(
Here’s how I fixed the issue this time, just in case it could help other people! Before you start, make sure you have a good hour in front of you.. ;-)
The commands are assumed to be executed as root…
Hope this helps!
Enjoy :)
RSS Feed