Paweł Pokrywka

Thanks for clarification.

If for some reason you can't or don't want to change SSH port, you could use port forwarding **on your local machine** as a workaround. There are many possibilities, personally...

Thank you @sunny for mentioning me. I received [great feedback from Zeitwerk author](https://github.com/fxn/zeitwerk/issues/271) and I'm going to update the post, probably today. I will post it here too.

Ok, I've updated the post. In the new "Limitations" section, there is a link to the original version if someone liked the previous approach better.

I like the first solution you described. The feature may not be used very often, but it makes sedge complete. The second solution is also nice. When the documentation is...

Hi Florian, Thank you for reporting the issue! The behavior you are experiencing looks odd to be honest. Cryptreboot should ask you for the password, verify it, report an error,...

@Ltty I suspect the issue may be related to `crypttab` file parsing. Could you paste your `/etc/crypttab`?

I installed Ubuntu 22.04.1 and was able to replicate the issue. It occurs when choosing ZFS+encryption when installing OS. Am I right you are using this filesystem?

Currently, cryptreboot supports LUKS-encrypted volumes described in `/etc/crypttab`. Encrypted ZFS volumes are not listed in `/etc/crypttab`, therefore they are invisible to cryptreboot. Unfortunately, cryptreboot won't work on your machine unless...

I'm glad you found a solution @Ltty, congrats! To uninstall cryptreboot, uninstall the gem: ``` sudo gem uninstall crypt_reboot ``` You can also remove dependencies if you are sure you...