similar to: How to get "Enter passphrase" on command line rather than GUI pop-up?

Chris Green: > Setting SSH_ASKPASS_REQUIRE=never in the environment on my xubuntu > 23.10 system doesn't seem to work. I have set it:- > > chris$ env | grep SSH > SSH_AUTH_SOCK=/run/user/1000/keyring/ssh > SSH_ASKPASS_REQUIRE=never What component is actually calling ssh-askpass? Setting SSH_ASKPASS_REQUIRE=never has no effect for me either, but that's

On Mon, 1 Jan 2024, Christian Weisgerber wrote: > Chris Green: > > > Setting SSH_ASKPASS_REQUIRE=never in the environment on my xubuntu > > 23.10 system doesn't seem to work. I have set it:- > > > > chris$ env | grep SSH > > SSH_AUTH_SOCK=/run/user/1000/keyring/ssh > > SSH_ASKPASS_REQUIRE=never > > What component is actually

There is a program call sshpass that does just that On ubuntu/debian: apt install sshpass > On 01 Jan 2024, at 20:37, Chris Green <cl at isbd.net> wrote: > > On Mon, Jan 01, 2024 at 06:34:01PM +0000, Chris Green wrote: >> Setting SSH_ASKPASS_REQUIRE=never in the environment on my xubuntu >> 23.10 system doesn't seem to work. I have set it:- >> >>

On Mon, Jan 01, 2024 at 06:34:01PM +0000, Chris Green wrote: > Setting SSH_ASKPASS_REQUIRE=never in the environment on my xubuntu > 23.10 system doesn't seem to work. I have set it:- > > chris$ env | grep SSH > SSH_AUTH_SOCK=/run/user/1000/keyring/ssh > SSH_ASKPASS_REQUIRE=never > chris$ > > But I still get the annoying GUI pop-up rather than

On Tue, Jan 02, 2024 at 03:52:29PM +1100, Damien Miller wrote: > On Mon, 1 Jan 2024, Christian Weisgerber wrote: > > > Chris Green: > > > > > Setting SSH_ASKPASS_REQUIRE=never in the environment on my xubuntu > > > 23.10 system doesn't seem to work. I have set it:- > > > > > > chris$ env | grep SSH > > >

> > There must be *something* in the environment that affects this because > I'm seeing two different ways of asking for the passphrase on the same > screen. The only difference is that one is a simple terminal window > running on my system and the other is one where I have used ssh to > connect to a remote system and then ssh again back to the 'home' > system.

On 2024/01/02 09:51, Chris Green wrote: > I think I have it! I need to unset SSH_AUTH_SOCK, that's all that's > needed. See:- > > chris$ ssh -i backup_id_rsa backup > [here the pop-up appears and I cancel it] > sign_and_send_pubkey: signing failed for RSA "backup_id_rsa" from > agent: agent refused operation > chris at backup's

https://bugzilla.mindrot.org/show_bug.cgi?id=1323 --- Comment #3 from Damien Miller <djm at mindrot.org> --- This is possible now using SSH_ASKPASS_REQUIRE: env SSH_ASKPASS_REQUIRE=force SSH_ASKPASS=/bin/false ssh-add ... </dev/null -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3562 Bug ID: 3562 Summary: make SSH_ASKPASS and SSH_ASKPASS_REQUIRE available as config options Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh

Hello, With the introduction of SSH_ASKPASS_REQUIRE in version 8.4, I've set up a script for SSH_ASKPASS to query my local passwordstore (https://www.passwordstore.org/) vault to retrieve the password for a given key. This works for ssh-add as well as ssh (configured with AddKeysToAgent set to 'yes'). My workflow effectively transforms into entering the password for the GPG key used

The idea behind this change is to add support for different "ssh-agents" being able to run at the same time. It does not change the current behaviour of the ssh-agent (which will set SSH_AUTH_SOCK just for itself). Neither does it change the behaviour of SSH_AGENT_PID (which still supports only one pid). The new implementation will go through the list of sockets (which are separated by a

https://bugzilla.mindrot.org/show_bug.cgi?id=3086 Bug ID: 3086 Summary: Ssh, scp (6.2p2 or 7.4p1) can't support the way to enter the private key password in a non-interactive way. Product: Portable OpenSSH Version: 7.4p1 Hardware: ix86 OS: Linux Status: NEW

Hi all, i'm trying to figure out if i'm being silly or if there is a genuine problem. Running on the notorious Redhat 7, 2.2.16-22 #1, X86. [user at host]$ ssh-agent -s SSH_AUTH_SOCK=/tmp/ssh-XXYFcFR6/agent.2101; export SSH_AUTH_SOCK; SSH_AGENT_PID=2102; export SSH_AGENT_PID; echo Agent pid 2102; [user at host]$ echo $SSH_AUTH_SOCK [user at host]$ echo $SSH_AGENT_PID [user at host]$

http://bugzilla.mindrot.org/show_bug.cgi?id=500 ------- Additional Comments From djm at mindrot.org 2003-02-24 12:43 ------- I think that: [ -z "$SSH_AUTH_SOCK" ] && eval `ssh-agent -s` [ -z "$SSH_AGENT_PID" ] || ssh-add -l >/dev/null 2>&1 || ssh-add Is as effective and a lot more concise. On the other hand, fragile heuristics like: > export

https://bugzilla.mindrot.org/show_bug.cgi?id=2480 Bug ID: 2480 Summary: Support a list of sockets on SSH_AUTH_SOCK Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh-agent Assignee: unassigned-bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=3572 Bug ID: 3572 Summary: ssh-agent refused operation when using FIDO2 with -O verify-required Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component:

Dear friends, First, thanks for helping me on ssh default option for smartcards. I recompiled SSH from CVS and it seems to work. I still have problems with: ssh-add -s /usr/lib/opensc-pkcs11.so Enter passphrase for PKCS#11: (I enter PIN code) SSH_AGENT_FAILURE Could not add card: /usr/lib/opensc-pkcs11.so pkcs11-tool --slot 1 -O Public Key Object; RSA 2048 bits label: Public Key ID:

On Fri, Sep 18, 2015 at 10:58 PM, ?ngel Gonz?lez <keisial at gmail.com> wrote: > On 18/09/15 15:47, Fabiano Fid?ncio wrote: >> >> Howdy! >> >> I've been working on a prototype that allows to do ssh-agent forward >> between a guest, using SPICE, and a spice client >> (remote-viewer/virt-viewer/spicy) >> The whole idea is to have something

On Fri, Sep 18, 2015 at 7:07 PM, Peter Stuge <peter at stuge.se> wrote: > Fabiano Fid?ncio wrote: >> A few possible solutions for this would involve a way to support more >> than one agent, talking to both (the local one and the spice one), >> merging then their responses and returning it to any application who >> sent the request. Note that would be really nice if

I'm having a path problem with OpenSSH 2.5.1p1 in Solaris (7). When ssh-agent is run, environment variables aren't being passed to the spawned shell. sol# env | wc -l 23 sol# env | grep -i ssh SSH_CLIENT=10.0.1.146 1047 22 SSH_TTY=/dev/pts/0 sol# sol# ssh-agent sh sol# env | wc -l 1 sol# env SSH_AGENT_PID=12032 sol# If I