Failed passphrase returns different output from the backend when a % is in the string

[subzero79]

I really don't know whats going on here. You can have a passphrase with non alpha chars, spaces no problem whatsoever, you can unlock from the webui and terminal. A wrong password in cryptsetup returns something like this

root@debian9:~# echo -n 'darkmoon1234' | cryptsetup luksOpen '/dev/sdh' 'sdh'-crypt --key-file=-
No key available with this passphrase.
root@debian9:~# echo -n 'darkmoon%1234' | cryptsetup luksOpen '/dev/sdh' 'sdh'-crypt --key-file=-
No key available with this passphrase.
root@debian9:~# 

Doing from the webui also returns the error output from terminal

But if we use the % character this time from the webui there is no output

Is like the whole omv exec is failing before it returns something, but it doesn't fail if the passphrase was indeed with a % char

Do you have any ideas @votdev what can cause something like this?