["Wrong Key!" error on starting array after upgrading to 6.8]

5 hours ago, limetech said:

If you don't mind please try this.  First Stop array and then take note of what device id is assigned to one of your data disks, doesn't matter which one.  Let's say you pick 'sdb'.  Then type this:

cryptsetup luksOpen /dev/sdb1 sdb1

The command should prompt you to enter your passphrase, please do so and hit Enter.  If the command succeeds it will simply exit; if not it will spit out an error.

 

If it succeeds, you should then type this:

cryptsetup luksClose sdb1

Please let me know what happens.

Upgraded to 6.8 rc1 as directed, as others have stated - still getting the same error. Keyfile works fine. Trimming passphrase down doesn't work.

 

Following the steps above provides no errors or feedback from the terminal but after does allow the array to mount 😎😎

["Wrong Key!" error on starting array after upgrading to 6.8]

Earlier I nuked my 6.8 test box and created a new config, formatted the drives as encrypted and set a "new" passphrase (the same as before). I'm still getting the "Wrong Key!" error - and using a keyfile still fixes the issue, and show passphrase displays the expected characters.

 

I've just repeated the same process, but this time removed any non alphanumeric characters and that works just fine... (the only non A-Z,a-z,0-9 char was an exclamation mark)

["Wrong Key!" error on starting array after upgrading to 6.8]

1 hour ago, bonienl said:

Silly question...

When you click on the button to show the passphrase as text, does it show your expected input?

Just checked and yes - the passphrase appears exactly as expected.

["Wrong Key!" error on starting array after upgrading to 6.8]

34 minutes ago, limetech said:

I can't reproduce.  What I'm doing is booting server with 6.7.2. Specify encrypted file type for a disk.  Specify a test passphrase, then format and verify passphrase still works.  Then boot 6.8.0 and enter same passphrase - always works.  The latest passphrase I tried was: !234567890

Very puzzling, all code looks correct.  To eliminate encoding issues, in 6.8 we did change how the passphrase is transmitted to the server - it now uses base64 encoding, and then decoded on server side.

Since this is a 'test box' are you willing to PM your exact passphrase to me?

Just sent it via PM.

["Wrong Key!" error on starting array after upgrading to 6.8]

2 hours ago, limetech said:

I booted a server running 6.7.2 and created an encrypted volume using passphrase: !@#$^&*)(

I then booted 6.8.0 and specifying same passphrase volume opened correctly.

 

Please tell me exactly which special characters you're using.

 

My test box only has ! as a special character, with 4 Uppercase letters and 4 numbers - nothing else. Main server has only Upper, Lower, Numeric, !, " and £ in its passphrase. Both exhibit the same behaviour.

["Wrong Key!" error on starting array after upgrading to 6.8]

3 hours ago, bonienl said:

That's exactly the same as entering a passphrase ...

Are you having an off day?! It's not the same in the slightest - I can enter a passphrase with a keyboard - I can't recreate a keyfile without another machine on the network (which, again, if someone will take the time to read - I DON'T HAVE).

["Wrong Key!" error on starting array after upgrading to 6.8]

15 hours ago, limetech said:

After starting array there is a button that says "Delete keyfile".

That won't work on my main server as the only machine on the network that can create a temp keyfile (to be deleted after successfully starting the array) is a VM on the server itself. If the keyfile is deleted and the server restarted - I'm back to square one - making a permanent keyfile (or making the passphrase less secure) the only feasible "workaround".

["Wrong Key!" error on starting array after upgrading to 6.8]

8 hours ago, limetech said:

The Help info for encryption says,

 

We need to look into exactly where the issue lies, you must use keyfile workaround for now.

 

And that is exactly how I constructed the passphrase.

 

Using a keyfile on my main server is not an option and completely unacceptable - a permanent keyfile completely negates the point encryption, and when the system is down - there's no means to create the keyfile.

 

Changing they passphrase to less secure construct is the only workaround, but not something I'm willing to compromise. I'll wait until this mess is fixed before upgrading.

["Wrong Key!" error on starting array after upgrading to 6.8]

Minor? Requiring an additional machine on the network every time I want to reboot my server is hardly "Minor"...

["Wrong Key!" error on starting array after upgrading to 6.8]

There are, yes.

I've given the keyfile workaround a go and it appears to work.