rmview asks for ssh passphrase despite the public key on remarkable and active ssh-agent

[bordaigorl]

rmview asks for ssh passphrase despite the public key on remarkable and active ssh-agent

[bordaigorl]

Ah I see what might be happening.
Would you be able to try something for me?

• make sure your ssh config file allows you to connect by just specifying the address (i.e. should specify user root and the key to use)
• comment out lines 54 and 55 of rmview/connection.py
• remove the key setting from rmview.json
• try running rmview (if you run pip install -e . it would install it so that edits to the sources would be picked up by the global script)

[bordaigorl]

@Kratacoa thanks for reporting, I think I was using Paramiko in a way that was not fully exploiting its features.
I'll push a new version soon, it would be great if you could test it.

[Kratacoa]

If by new version you meant the last commits, I am afraid I am getting the same message :/
My configuration is example.json.
Should I try out the steps mentioned in the first reply?

[bordaigorl]

Yes, try the last commits but:

• remove key and password from the configuration

This should make sure the connection settings are determined entirely by the system-wide SSH configuration

[Kratacoa]

When I remove key, it asks me for my reMarkable's password instead.
You said system-wide: so far I have used the user configuration file. Isn't that supported?

[bordaigorl]

That is the old behaviour.
Are you sure you are running the version at 0fa4234 ?
If you installed rmview with pip install . you may need to install again after pulling the changes.
Also: which OS are you on?
(Btw thanks for testing this!)

[Kratacoa]

If you installed rmview with pip install . you may need to install again after pulling the changes.

This did the trick. Thank you for the assistance, and in general for your project :)

Also: which OS are you on?

Void Linux, musl version.

[bordaigorl]

Great! I'm closing and including in next release.
Thanks for the feedback!

[pheraph]

I installed the current version (the default vnc branch) on macOS and everything works, but I still see the problem that if I try to authenticate via SSH key I am asked for my keyphrase. My .ssh/config is

Host remarkableUSB
        HostName 10.11.99.1
        User root

And I can login just fine via ssh remarkableUSB, but the following configuration doesn't work without a password prompt:

{
    "ssh": {
        "address": [
            "10.11.99.1"
        ]
    }
}

And this one keeps asking for my keyphrase:

{
    "ssh": {
        "address": [
            "10.11.99.1"
        ],
        "key" : "~/.ssh/id_rsa"
    }
}

Should this work or am I maybe on the wrong branch?

[bordaigorl]

@pheraph in principle it should work, provided the ssh-agent is running in the background and that you added to it the relevant key (which should be true if ssh does not ask you for the passphrase during login).
(By keyphrase I assume you mean the passphrase used to encrypt the id_rsa key)
You could try running rmview after running ssh-add -K ~/.ssh/id_rsa and see if it works.

You could also try using:

{
    "ssh": {
        "address": [
            "10.11.99.1"
        ],
        "auth_method": "key",
        "key" : "~/.ssh/id_rsa"
    }
}

(you can omit the key setting if you include in your ssh config IdentityFile ~/.ssh/id_rsa in the relevant Host).
If this still asks you for your passphrase then it means that Paramiko is not able to get the passphrase from your ssh-agent...
(As a workaround you could use, just for the tablet, a new key without passphrase.)

Finally, the devel branch has some changes to the authentication code, you could try to see if that helps.

[pheraph]

@bordaigorl Thanks for your detailed reply! I tried your suggestions without success though. Your assumption is right I don't have to enter my passphrase during login. Still I am asked for address and passphrase even with your provided config. I also switched to the devel branch, but was not able to launch rmview successfully:

Qt Concurrent has caught an exception thrown from a worker thread. This is not supported, exceptions thrown in worker threads must be caught before control returns to Qt Concurrent.
Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!'
libc++abi.dylib: terminating with uncaught exception of type NSException

But this is obviously out of the scope of this issue. I now helped myself by stepping away from the SSH authentication and adding the plain password to the config file (with chmod 600 on the file). This is as good for me as an unprotected SSH key.