Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSH Agent / Selecting 'Require user confirmation when this key is used' causes failed ssh login attempt #9955

Closed
rolling-thundar opened this issue Oct 23, 2023 · 3 comments

Comments

@rolling-thundar
Copy link

rolling-thundar commented Oct 23, 2023

Overview

Steps to Reproduce

  1. Create a new key
    ssh-keygen -t ed25519 -a 100
  2. Add the generated private key to keepassxc as attachment
  3. Add the chosen password into the 'Password' field
  4. Deselect these options:
  • 'Add key to agent when database is opened/unlocked'
  • 'Remove key from agent when database is closed/locked'
  1. [IMPORTANT] Select the option 'Require user confirmation when this key is used'
    --> this is the option causing trouble
  2. Save the entry
  3. Add key to SSH agent
  4. Go to terminal and try to ssh into your server:
    $ssh user@server

Expected Behavior

A pop-up message asking me whether I want to login with this key to my server.

Once I click on 'Ok', I successfully connect to my server.

Actual Behavior

I don't see the prompt message. Instead I get the following error message:

$ssh user@server
sign_and_send_pubkey: signing failed for ED25519 "user@client" from agent: agent refused operation
user@server: Permission denied (publickey).

Context

This problem only appears with the following SSH agent settings selected:

'Require user confirmation when this key is used'

As soon as I deselect the option, I can successfully ssh into my server.

KeePassXC - 2.7.6
Revision: dd21def

Operating System: Linux (Pop_OS)
Desktop Env: Regolith Desktop (3.0)
Windowing System: X11

@rolling-thundar
Copy link
Author

The same behaviour happens when I login to Pop_OS with the default Gnome Desktop Env, instead of Regolith Desktop.

@droidmonkey
Copy link
Member

This is on your ssh agent, if it doesn't support the setting then it generally fails to accept the key from us. Just disable the setting or use an ssh agent that supports this feature.

@droidmonkey droidmonkey closed this as not planned Won't fix, can't repro, duplicate, stale Oct 23, 2023
@rolling-thundar
Copy link
Author

Gotcha. Thanks for the quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants