Unable to use ssh-copy-id

[mcuix]

I am unable to ssh-copy-id my ssh keys to my server.
I use

ssh-copy-id /.ssh/id_rsa.pub user@myserver

, but Blink returns an ERROR no identity found.

[yury]

Hi @mcuix,

‘ssh-copy-id’ command works only with keys from config->keys for now.

[JeremyIglehart]

Okay, it took me a while to figure this out because I couldn’t find any how to... maybe there is one somewhere and I overlooked it... if so, please feel free to point this out to us all.

Basically, I just installed Blink yesterday - my version comes with a generated key “id_rsa”. Assuming you don’t change this key, or make a new one with a different name. You could do something like:

ssh-copy-id id_rsa jeremy@192.168.10.10

Obviously you should use your username and host... but the ssh-copy-id is looking for the names of keys listed when you type config, and choose “keys” out of the menu.

Enjoy.

[ellierider]

Hi @mcuix,

‘ssh-copy-id’ command works only with keys from config->keys for now.

Can you please provide an example?

[carloscabanero]

There is more information here as well. The key is not a path but a key on your config > keys.

https://docs.blink.sh/basics/commands#ssh-copy-id

[kyleridolfo]

Thanks. I tried what @JeremyIglehart did, and looked at that link. But it simply does not find either type of key I created with the app. I tried a regular id_rsa key and I tried the Secure Enclave version

[carloscabanero]

What error message do you get? In any case, the only thing this script does is to copy the public key to the "authorized_keys" on the remote. If you still have issues, you can do it manually as well by logging to the remote.

[kyleridolfo]

Hi! I was able to get it working on iPhone. On iPad it just said it couldn’t find the key

…

On Mon, Aug 1, 2022 at 18:27 carloscabanero ***@***.***> wrote: What error message do you get? In any case, the only thing this script does is to copy the public key to the "authorized_keys" on the remote. If you still have issues, you can do it manually as well by logging to the remote. — Reply to this email directly, view it on GitHub <#1538 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAABBOBW47YXZ47JCP7OOEDVXBFNDANCNFSM55FDGAYQ> . You are receiving this because you commented.Message ID: ***@***.***>