After updating to MR5 (update went quick as usual), I cannot connect via Sophos Connect (IPsec).
Connection fails with "Incorrect PSK" error.
I tried re-applying the key from the scx file, but it did not help.
Exporting a new scx file (with the same key) revealed that after 95 characters "\\" is added and again after another 27 characters.
All in all, the key in the new scx file is 132 characters long instead of 128.
Trying with a new, shorter, key works, but it means deploying it to all the users, which is a bit problematic.
Inserting the "wrong" key (that is, the 132 characters key) into the firewall configuration and exporting a new scx revealed that this time, after each "\\" another 8 characters of "\" were inserted.
That is the exported key is now 148 characters long.
But: Do you have already Sophos Connect 2.1 deployed? Because SC2.1 can publish the new config by its own, if you use a new .pro file. https://docs.sophos.com/nsg/sophos-firewall/18.0/Help/en-us/webhelp/onlinehelp/nsg/sfos/concepts/SConProvisioningFile.html?hl=sophos%2Cconnect%2Cprovisioning%2Cfile
But i will forward this feedback.
Yep, that is with 2.1
Hi Oz Group,
Thank you for reaching out to Sophos Community.
I'm in a discussion with the internal team regards with the issue which you've reported. I'll also try to configure Sophos Connect with a pre-shared key 128 characters long and will update this thread soon.