similar to: [RFE] Multiple ssh-agent support

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

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

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

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

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

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

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

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

I finally got access to some machines with more resources than the free VMware ESXi license allows which pushed me into trying kvm instead. Seems capable enough for what I need and can even import and run the existing vmdk images I already have. But, I have some questions about accessing the virt-manager console remotely for initial configuration, etc.. Normally I use freenx for remote GUI

https://bugzilla.mindrot.org/show_bug.cgi?id=2066 Bug ID: 2066 Summary: ssh tries the keys proposed by the agent before those passed with -i Classification: Unclassified Product: Portable OpenSSH Version: 6.0p1 Hardware: All OS: Linux Status: NEW Severity: normal

hello centos.. I am having a very annoying problem on my network right now. it looks like every time I try to add my ssh key to keychain I have to issue a command just to get my ssh subsystem communicating with the ssh-agent: I have this line in my .bashrc file $(keychain --eval --quick --quiet private_key1 private_key2 private_key3) If I try to perform ssh-add I get the message: [bluethundr

I recently had to upgrade my version of OpenSSH from 4.7 to 5.0p1 on my MacBook (Darwin). I installed the latest 'portable' tarball and removed the system version: $ ssh -V OpenSSH_5.0p1, OpenSSL 0.9.7l 28 Sep 2006 $ which ssh /usr/bin/ssh sshd is the same version, installed in /usr/sbin/sshd. Now, things are a bit broken: I am able to ssh from another machine into my MacBook, so the

http://bugzilla.mindrot.org/show_bug.cgi?id=496 ------- Additional Comments From hauser at acm.org 2003-03-31 16:56 ------- Created an attachment (id=266) --> (http://bugzilla.mindrot.org/attachment.cgi?id=266&action=view) Readme.txt for the japanese win-ssh-agent.exe/win-ssh-askpass.exe proofread by Nayuta ------- You are receiving this mail because: ------- You are the assignee

Hello, I've got a problem with newer versions of ssh-agent not accepting all keys being forwarded to them. Example: LOCAL-WORKSTATION ssh-add -l 4096 SHA256:HFSzrozPapudofYJi8QvXQdA1/vNpFc2iPWH8CGVsEg (none) (RSA) 2048 SHA256:lbjpmHAYtUO+zaLaKvWVxGNYkXRkOumcoOpLdRSVX/U /home/matt/.ssh/id_rsa_embedded (RSA) ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 BROKEN-REMOTE ssh

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 Thu, Oct 1, 2015 at 12:27 PM, Christoph <mangel at gmx.de> wrote: > Am 2015-10-01 12:33, schrieb Fabio Fantoni: >> >> Should be something like /var/log/xen/qemu-dm-marax.log > > oh ok: > > qemu-system-i386: -spice > port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on: There is no > option group 'spice' > spice is not supported by this

Hi all, as per subject, when a Windows guest using a Spice display is rebooted with a planned chkdsk, the consistency check is always skipped. It seems that the Spice display issues some "phantom" keystrokes, which are then intended by Windows as the "skip chkdsk at boot" signal. I tried to use a Spice display with no additional features (ie: USB redirection), but to no

On 19/10/2018 08:13, Gionatan Danti wrote: > Il 17-10-2018 09:15 Gionatan Danti ha scritto: >> Hi all, >> as per subject, when a Windows guest using a Spice display is rebooted >> with a planned chkdsk, the consistency check is always skipped. >> >> It seems that the Spice display issues some "phantom" keystrokes, >> which are then intended by

Usage: spicevdagent=1|0 (default=0) Enables spice vdagent. The Spice vdagent is an optional component for enhancing user experience and performing guest-oriented management tasks. Its features includes: client mouse mode (no need to grab mouse by client, no mouse lag), automatic adjustment of screen resolution, copy and paste (text and image) between client and domU. It also requires vdagent