unlocking error on RP3B+ - Not enough available memory to open a keyslot about cryptmypi

[unixabg]

Greetings,
I just pushed to next-4.x and master a kali encrypted basic dropbear example that builds and unlocks on my test setup. Please try that example as a starting point and see if you have better luck. If so please close issue.

[splitstrikestream]

I've encountered this error once, but it never happened again (even on the same image).

To prevent eventually getting stuck some other time, Ive placed a command to reboot the Pi if a problem like this happened, so if it happened, in a few seconds everything should be back and you could retry.

Do you still have this image? Can you verify it is a deterministic error?

[superuser5]

Hi,
i have tested on RPi3B+ and no luck to unlock it :(

On the client side i have this, i have to enter password twice for some reason, even though i have same error while using bearssh "Not enough available memory to open a keyslot.", but on the screen it drops to Busybox with some errors, please find screenshot attached.

ssh console
kali@kali ~> ssh [email protected] -p 2222 -i /home/kali/.ssh/id_rsa_test
[email protected]: Permission denied (publickey).
kali@kali ~ [255]> ssh [email protected] -p 2222
Enter passphrase for /dev/mmcblk0p2:
Not enough available memory to open a keyslot.
Connection to 192.168.1.13 closed.
kali@kali ~> ssh [email protected] -p 2222
Enter passphrase for /dev/mmcblk0p2:
Not enough available memory to open a keyslot.
Connection to 192.168.1.13 closed.

and the screenshot is attached.

[superuser5]

I have tested the RPI4 and similar problem, even thought i don't get any errors during step 1 or step2 of the process, i need to enter password few times to get accepted and get other errors:

ssh console

screenshot error testing kali unencrypted basic dropbear

[superuser5]

I've encountered this error once, but it never happened again (even on the same image).

To prevent eventually getting stuck some other time, Ive placed a command to reboot the Pi if a problem like this happened, so if it happened, in a few seconds everything should be back and you could retry.

Do you still have this image? Can you verify it is a deterministic error?

Hello,
I tried imaging multiple times but i still have errors above on the kali-encrypted-basic-dropbear and pios-encrypted-basic and test on RPi3B+ and RPI4. I tried imaging multiple times, make sure there is enough space and for some reason it does not recognize my password consistently on both and have "Not enough available memory to open a keyslot" on RPi3 consistently.

Is there a way to verify that there is no corruption during image creation process?

[unixabg]

Greetings,

Hello,
I tried imaging multiple times but i still have errors above on the kali-encrypted-basic-dropbear and pios-encrypted-basic and test on RPi3B+ and RPI4. I tried imaging multiple times, make sure there is enough space and for some reason it does not recognize my password consistently on both and have "Not enough available memory to open a keyslot" on RPi3 consistently.

Is there a way to verify that there is no corruption during image creation process?

The only thing I can think of for you since the examples/kali-encrypted-basic-dropbear works for me is to try building inside a pristine VM with latest kali (I am using kali-linux-2020.2-installer-amd64.iso installer with VirtualBox) and a fresh clone. I will leave this open and wait for you to test in a pristine environment. Oh and I do not have a Pi4 to test with. I have one ordered and upon arrival I will attempt to test all examples. And another edit and oh, what is the size of your sdcard?

[unixabg]

Greetings,
Also if still having trouble can you submit full build log? Something like:

sudo ./cryptmypi.sh examples/pios-encrypted-basic | tee pios-encrypted-basic_build-log.txt

[superuser5]

on the same machine that successfully creates RPI4b images, i run the following profile as is for RPi3B+: $ sudo ./cryptmypi.sh examples/kali-encrypted-basic-dropbear | tee rpi3b_plus_kali-encrypted-basic-dropbear_build_log.txt

remote and local unlock gives same error message:
$ ssh [email protected] -p 2222
Enter passphrase for /dev/mmcblk0p2:
Not enough available memory to open a keyslot.
Connection to 192.168.1.13 closed.

log file attached.
rpi3b_plus_kali-encrypted-basic-dropbear_build_log.txt

[superuser5]

tested same RPi3 with the example profile as is (running v7+)
sudo ./cryptmypi.sh examples/pios-encrypted-basic | tee pios-encrypted-basic_build-log.txt.

Problem: I cannot authenticate using local unlock (cryptsetup: ERROR: crypt: cryptsetup failed, bad password or options?)

log file:
pios-encrypted-basic_build-log.txt

[splitstrikestream]

The original issue **Not enough available memory to open a keyslot
** should be solved in the latest PR #20

[unixabg]

Greetings,
I am going to close this since I tested latest v4-1-beta tagged release with both rpi3b+ and rpi4 on kali-encrypted-basic-dropbear and both runs worked as expected. If more assistance is needed please open a new issue.

[howtodo1]

I have the same problem and same kind of raspberry pi, did I do something wrong during the build?
Update: I maybe found out why this is happening, at least 1GB of ram is needed at luksOpen and the raspberry pi 3b plus has 1gb of ram so it would not be able to open. You should see this website here

[unixabg]

Greetings,
First thank you for the update and information. I will be on the look out for this during my testing in the coming weeks. Please know that I am really only testing against the next-4.x branch and primary testing on rpi3b+.