hal-luks-setup-linux does not handle password containing the backslash charactesr

Bug #112657 reported by Fabrizio Tarizzo on 2007-05-05
2
Affects Status Importance Assigned to Milestone
HAL
Confirmed
Low
hal (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: hal

If the passphrase of a LUKS encrypted partition contains the backslash character, hal-luks-setup-linux returns a "Bad password" message, you have to type the passphase escaping the backslash (i.e., if your password is abc\123, you have to type abc\\123).

The "read password" in the hal-luks-setup-linux script should be "read -r password".

I verified this on hal 0.5.8.1-4ubuntu12 (Feisty)

I have a usb hard drive with one encrypted partition. When I turn on my computer and my hard is plugged, cryptdisks-early service ask my password and all things are ok. But when I turn on my computer and plug the hard when gnome is started, /usr/lib/hal/scripts/linux/hal-luks-setup-linux asks my password. I have "\" character in my password and it is escaped in this line of that script:

if ! echo "$PASSWORD" | $CRYPTSETUP luksOpen $HAL_PROP_BLOCK_DEVICE luks_crypto_$HAL_PROP_VOLUME_UUID 2> /dev/null; then

It's not so bad! I have a device which accepts two different passwords depending on the situation, one with one backslash and the other with two backslashes; It's more secure! :D

Changed in hal:
status: Unknown → Confirmed

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in hal (Ubuntu):
status: New → Incomplete

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in hal (Ubuntu):
status: Incomplete → Invalid
Changed in hal:
importance: Unknown → Low
Changed in hal:
importance: Low → Unknown
Changed in hal:
importance: Unknown → Low

Reza Mohammadi,
Do you still experience this issue with newer soft ?
Please check the status of your issue.
Or close this bug.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.