similar to: [Bug 2480] New: Support a list of sockets on SSH_AUTH_SOCK

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

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 similar to "ssh -A guest", but integrated with the desktop environment. As a proof of concept I wrote a standalone ssh-agent that _unlink_ the current running agent in the guest machine and

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

Hello OpenSSH, wolfSSL will be at FOSDEM 2016 in Brussels on the 30th and 31st of January. We are interested in getting together in person with any developers from OpenSSH to talk about the recent port of wolfSSL to OpenSSH. Please contact us at info at wolfssl.com if you are interested in setting up a meeting. Thank you all for your time. Best Regards, wolfSSL

Thanks Rich for drawing this forward, I had missed it. (I generally handle all the trademark usage queries.) The key reference is this one, the trademark guidelines: https://www.centos.org/legal/trademarks/ That document should give the GNOME project all of the authorization and guidelines on how to use and not use the CentOS marks. Fabiano -- if you have any further questions, you may also

On 09/18/2018 11:03 AM, Fabiano Fid?ncio wrote: > My understanding is that we can use all the CentOS marks provided here[0]. > However, those unfortunately are not looking good enough on Boxes and > we'd like to use, if possible, just the logo as in here[1] > > Would that be possible? As far as I could understand that would be a > violation of the trademark. > > [0]:

People, Firstly, sorry for the cross-list post (centos-devel and centos-docs). I'd like to reach you in order to ask for a formal authorization to use CentOS logo on GNOME Boxes[0]. GNOME Boxes already shows a few other distro's logos as you can check here[1]. Would be possible to get the explicit confirmation that we could use CentOS logo as well? [0]:

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

Karsten, On Wed, Oct 31, 2018 at 10:06 PM Karsten Wade <kwade at redhat.com> wrote: > > Hi all, > > There is now a draft permission letter working it's way through the > CentOS Board. It is intended to cover permission for just the GNOME > Project's use with GNOME Boxes. This is *really* good news! > > I am still pursuing resolving this within the

https://bugzilla.mindrot.org/show_bug.cgi?id=2216 Bug ID: 2216 Summary: allow forwarding a different socket than SSH_AUTH_SOCK Product: Portable OpenSSH Version: 6.5p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs

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]$

> > 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

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

Hi all, Thanks for all your hard work! I was particularly excited to see FIDO/U2F support in the latest release. I'd like to make the following bug report in ssh-agent's PKCS#11 support: Steps to reproduce: 1. Configure a smart card (e.g. Yubikey in PIV mode) as an SSH key. 2. Add that key to ssh-agent. 3. Remove that key from ssh-agent. 4. Add that key to ssh-agent. Expected results:

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

Karsten, On Tue, Sep 18, 2018 at 7:45 PM, Karsten Wade <kwade at redhat.com> wrote: > Thanks Rich for drawing this forward, I had missed it. (I generally > handle all the trademark usage queries.) > > The key reference is this one, the trademark guidelines: > > https://www.centos.org/legal/trademarks/ > > That document should give the GNOME project all of the

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 > > >

On 09/13/2018 07:54 PM, Darren Tucker wrote: > I'd guess that the reason it doesn't work is that the key is encrypted > and neither the agent nor a tty to ask for the decryption passphrase > is available. Try repeating your command line test after unsetting > SSH_AUTH_SOCK > Okay. That reproduced the issue. Is there a recommended way to provide the decryption

On 13.01.16 10:27, Richard W.M. Jones wrote: > On Wed, Jan 13, 2016 at 09:55:53AM +0200, Shahar Havivi wrote: > > Hi, > > > > I am successfully importing VM from Xen server at oVirt project via virt-v2v. > > I am setting ssh-agent and running ssh-add before the import process, > > after the import done I am trying to kill the agent via: > > ssh-agent -k (and