Deployment to remote Linux development

aha_1980

@SPlatten

You've hit QTCREATORBUG-22030. Please comment and vote there so that password input will be possible again.

For now, you have two possibilities:

Go back to Creator 4.8 where password still works
Create a SSH public/private key pair and load the public key to the remote device and specify the private key in Creator.

I currently use option 2, but it is tedious if you have a lot of different devices without the key.

Regards

SPlatten

Thank you, this option really needs to be restored in the configuration. How do I vote for it to be put back in?

J.Hilk

@SPlatten
you can't vote for it, because the ticket is in the closed state.

Apparently it's the way its supposed to be. You would have to make a change request ticket (same platform as the bug report)

But chances seem to be slim

aha_1980

@J.Hilk said in Deployment to remote Linux development:

you can't vote for it, because the ticket is in the closed state.

Huh? I didn't know that! That's IMHO a a bad restriction, as uses can't show their interest in a specific bug.

But chances seem to be slim

Never give up :)

SPlatten

This is as frustrating as hell....I need to deploy to a target which previously used username and password, I have no idea how to get the target device to accept a private key file and the instructions are not very helpful or clear.

This is a backward step and should be an option.

aha_1980

@SPlatten Can you log on the device by SSH?

Then it should be possible to create a SSH public/private key pair on your development station by ssh-keygen. Afterwards you copy the public key (e.g. ~/.ssh/id_rsa.pub to the device and append it to the file ~/.ssh/authorized_keys.

Afterwards you should be able to log-in on the device without password, just by the key.

And if you now point QtCreator to your private key: voilá, it should work from there too.

nimbusgb

@aha_1980 Would be nice if Digi kept their documentation up to date though.

aha_1980

@nimbusgb What do you mean? That is documented at https://doc.qt.io/qtcreator/creator-developing-generic-linux.html

Regards

nimbusgb

@aha_1980 Sadly the standard yocto build does not have ssh-keygen on the target device so getting a key built is 'challenging' and digi's documentation only extends to Qt version 2 iirc.

aha_1980

@nimbusgb

Sadly the standard yocto build does not have ssh-keygen on the target device so getting a key built is 'challenging'

You don't need ssh-keygen on the target. You generate the key pair on your development machine and only deploy the public key to the target.

and digi's documentation only extends to Qt version 2 iirc.

What do you mean by that? Btw, the company is now called The Qt Company, not Digia.

Regards