Jump to content

[Armbian build PR] - [WIP] Fix creating builds with encrypted rootfs


RSS Bot

Recommended Posts

Description

When creating builds with CRYPTROOT_ENABLE=yes there were issues with package caching and intermittent issue with root partition not getting detected that was breaking the build. Also the functionality was broken because of /dev/mapper/armbian-root not being available during initramfs generation and there was a possibility of functionality being broken due to use of incorrect cached initrd file. This PR fixes the same.

Jira reference number AR-1799

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

  • [X] Created build for NanoPi Duo2 with CRYPTROOT_PASSPHRASE=crypt_pass CRYPTROOT_ENABLE=yes CRYPTROOT_SSH_UNLOCK=no and made sure that I was able to unlock the encrypted rootfs with passphrase
  • [ ] Will test if ssh unlock works on Orange Pi Prime and then will remove the wip status

Checklist:

  • [X] My code follows the style guidelines of this project
  • [X] I have performed a self-review of my own code
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [X] My changes generate no new warnings
  • [ ] Any dependent changes have been merged and published in downstream modules

View the full article

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines