htimsk/securekey

Instructions for using and Aegis Secure Key with Rocket Pool

securekey's Issues

fstab issue if another drive is connected

I previously used this guide to set up an Aegis key and it works well, however it does not account for the situation of an additional drive being added later and Ubuntu reassigning sda1 to the new device instead when rebooted, which as far as I can ascertain is outside of the user's control. If this occurs, then Rocketpool will no longer be able to find the keys as fstab will be pointing to the wrong device. Assignment of sda, sdb, etc to devices by Ubuntu can be inconsistent and subject to change.

The fix to prevent this possibility is quite simple though - the /etc/fstab entry should be made using a UUID (which is fixed) instead of the variable sda.

Run blkid to see the UUID entry for the Aegis key:

blkid

Copy the UUID string delivered, and then use it without quotes in /etc/fstab:

sudo nano /etc/fstab

Replace /dev/sda1 with UUID=XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX so that the entry becomes:

UUID=XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXX /home/USERNAME/.rocketpool/key ext4 defaults 0 2

This way any changes in the connected devices will not cause Rocketpool to stop working, as the fstab entry will still always point to the correct device.

I suggest the guide be edited to use UUID from the beginning, to prevent others from having this potential problem.

Other Clients?

This is an absolutely wonderful idea and guide. Thank you for creating it.

It would be a gift to describe the correct settings for other clients (Nimbus, Lighthouse, Prysm, etc.) and what files go where and what settings to tweak.

I shall experiment myself and create a PR if I get anywhere, but you seem miles ahead :)