[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1103720: marked as done (ssh-askpass-gnome prompts for confirmation, but the connection is always allowed)

Your message dated Tue, 29 Apr 2025 10:37:13 +0100
with message-id <aBCdyauchE_6yk_J@riva.ucam.org>
and subject line Re: Bug#1103720: ssh-askpass-gnome prompts for confirmation, but the connection is always allowed
has caused the Debian Bug report #1103720,
regarding ssh-askpass-gnome prompts for confirmation, but the connection is always allowed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1103720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103720
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ssh-askpass-gnome
Version: 1:9.9p2-2
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: erebion@erebion.eu, Debian Security Team <team@security.debian.org> 

Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate *** 

* What led up to the situation?

Using:

- ssh-askpass (GNOME version)
- KeePassXC
- GNOME Keyring as the SSH Agent
- setting /run/user/1000/gcr/ssh as SSH_AUTH_SOCK in the KeepassXC settings
Askpass asks to allow using the SSH key. Upon clicking "no", a connection is still established. 

SSH outputs the following:
sign_and_send_pubkey: signing failed for ED25519 "/home/user/.ssh/id_ed25519" from agent: agent refused operation 

Then the prompt of the remote system appears.

* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?

No idea what I could do other than report the bug.

* What outcome did you expect instead?

Clicking "no" leads to the SSH connection not getting established.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (900, 'testing')
Architecture: arm64 (aarch64)
Foreign Architectures: amd64

Kernel: Linux 6.12.21-arm64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ssh-askpass-gnome depends on:
ii libc6 2.41-6
ii libglib2.0-0t64 2.84.1-1
ii libgtk-3-0t64 3.24.49-3
ii openssh-client 1:9.9p2-2

ssh-askpass-gnome recommends no packages.

ssh-askpass-gnome suggests no packages.

-- no debconf information

--
erebion

XMPP: erebion@erebion.eu

My languages: German, English, Swedish, Norwegian, Danish
Yes, I'm a language nerd. Feel free to write to me in any of the aforementioned languages.

Attachment: OpenPGP_0x8EAF40326E02AE7D.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
On Mon, Apr 28, 2025 at 03:10:25PM +0200, erebion wrote:
I've had another look and couldn't reproduce the issue. Might have been in another package that got update, but now it works as intended. Maybe a side effect of many updates coming in because of the freeze..? 

I think this should be closed now.
Thanks for confirming; although it's a bit unsatisfying not to know exactly what the problem was, there's probably no point in keeping this open if it's gone away. I'm closing the bug with this message. 

--
Colin Watson (he/him)                              [cjwatson@debian.org]

--- End Message ---
Reply to: