Tried on 2 different XA2 Dual.
SSH password not accepted when trying to connect to the phone booted in recovery mode.
Into Jolla Recovery v2.0, choice #5, SSHD launched.
The exact same procedure working with SFOS_4.3.0.15/DUAL-Sailfish_OS-Jolla-4.3.0.15-h4113-0.0.9.9/hybris-recovery.img
Enter lockcode + [Enter]
-Try to connect to the above sshd from another terminal with ssh or sshfs
EXPECTED RESULT:
“recovery” password accepted after entering sshfs -o idmap=user,allow_other root@10.42.66.66:/ /mnt/sfos
as with ...Jolla-4.3.0.15-h4113-0.0.9.9/hybris-recovery.img
ACTUAL RESULT:
Password refused
MODIFICATIONS:
none
ADDITIONAL INFORMATION:
Linux Debian Mate-terminal, working with previous versions of hybris-recovery.img
I get the same issue on my old Jolla. I had to disable the password to use recovery mode factory reset.
Edit: I misunderstood the main message. It’s not exactly the same problem. On Jolla I tried a factory reset it only worked once a disabled password/security code.
Edit: No computer these days to verify.
But it might be that I neglected the fingerprint.
Ssh complains about it when changed but sshfs doesn’t.
And I’m not sure anymore having tried to simply connect to the phone with ssh.
/edit
Yes.
The phones are on the 4.4.0.64
The recovery image which are problematic for me are the 4.4.0.58 and 64.
The phones boot in recovery mode and should be connected through ssh with choice 5.
I usually mount the phones’ filesystem into the PC with sshfs after having opened the encrypted partition.
Since 4.4.0.58, the password ‘recovery’ is refused.
Back home I can test again.
I confirm that I cannot connect to the sshd server launched from within hybris-recovery.img's Jolla Recovery.
It works with versions prior to 4.4.0.58.
But on .58 and .64, the password is refused when I try to connct with ssh or sshfs.
This is not a problem as I have the prior versions that are working.
No big deal. Just to inform Jolla.
As it happens we already had a bug logged internally following your discussion on General, but I’ve added this bug to it and tagged it as “tracked”. If there’s new info to share on it we’ll do our best to add it here.