[SailfishDevel] Update 2.0.1.3 and ssh

[David Greaves]

Login to the device as root and:

cp /etc/ssh/sshd_config /etc/ssh/sshd_config.safe
cat <<EOF >> /etc/ssh/sshd_config
# Added this line to enable SDK to connect
Ciphers +aes128-cbc
EOF
systemctl restart sshd.service

***************************************************
Don't forget to fix it when the new QtC comes out!
***************************************************


WARNING: This does 'weaken' the ssh service on your device by allowing this 
weaker cipher.

Note that 'normal' ssh connections would not typically be vulnerable but as you 
can see, QtC uses this weak cipher by default :/

David


On 28/10/15 12:42, Adam Pigg wrote:
> Is there a workaround/time frame for update? I've got fixes to make ‎for Harbour qa rejections! :)
>
> Sent from my BlackBerry 10 smartphone.
>    Original Message
> From: Jussi Pakkanen
> Sent: Wednesday, 28 October 2015 12:40 PM
> To: devel at lists.sailfishos.org
> Reply To: Sailfish OS Developers
> Subject: Re: [SailfishDevel] Update 2.0.1.3 and ssh
>
> On 28.10.2015 14:33, Adam Pigg wrote:
>
>> ‎After updating my tablet last night to 2.0.1.3 I could no longer
>> connect using Qt creator / ssh. The client and server ciphers didn't
>> match. I have not installed anything from openrepos such as a
>> different ssh package.
>
> This is caused by the fact that the SSH server has stricter cipher
> requirements in 2.0.1. The next SDK version will have newer QtC which
> will support deployment to these devices.
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org
>