Operation failed due to one or more of the following:
- Incorrect password.
- Incorrect Volume PIM number.
- Incorrect PRF (hash).
- Not a valid volume.
I then can enter the password when prompted and it works.
Last edit: Andrew Claus 2018-12-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have you tried not enclosing the veracrypt command and parameters in double quotes when using SSH? Would not be necessary if mounting a VC volume via SSH on a Windows PC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmmmm it may be the special characters. My password started with & and after some changes it seems that breaks out of the quotes when passing a command to SSH. Enter te&st and it will say "st: command not found"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The ampersand is the problem. You should never use them in passwords you intend to invoke using the command line. In Windows, wherever it occurs, it will always be interpreted as an end marker for the current command, and an instruction to interpret everything that follows as a new command. In Linux, it has a slightly different meaning (I think Linux '&&' is equivalent to Windows '&') viz 'continue to run the current command in the background' ie where 'current' means everything up to the ampersand ie the effect is the same as in Windows.
There have been a number of discussions of this issue in the forum (though none recently, so they'd be a bit hard to track down).
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello I am trying to mount a volume on a Linux machine over ssh. I can do it once SSH'd into the machine with no user prompts with
When I run the command via shell SSH, it fails
yields
I then can enter the password when prompted and it works.
Last edit: Andrew Claus 2018-12-23
Have you tried not enclosing the veracrypt command and parameters in double quotes when using SSH? Would not be necessary if mounting a VC volume via SSH on a Windows PC.
Then it fails on my password whether I double or single quote it. I do have special characters in the password
Hmmmmm it may be the special characters. My password started with & and after some changes it seems that breaks out of the quotes when passing a command to SSH. Enter te&st and it will say "st: command not found"
The ampersand is the problem. You should never use them in passwords you intend to invoke using the command line. In Windows, wherever it occurs, it will always be interpreted as an end marker for the current command, and an instruction to interpret everything that follows as a new command. In Linux, it has a slightly different meaning (I think Linux '&&' is equivalent to Windows '&') viz 'continue to run the current command in the background' ie where 'current' means everything up to the ampersand ie the effect is the same as in Windows.
There have been a number of discussions of this issue in the forum (though none recently, so they'd be a bit hard to track down).
Thanks Adrian. That makes sense.
For other people who encounter this, I have thus far learned you cannot pass & or $. Both make sense, but threw me off