ug output attached, as well as cygcheck output.
> I decided to run setup to see if there was a newer version of openssh.
> In preparation for that I always terminate all Cygwin processes because
> they will interfere with the update. I killed the ssh-agent process and
> on a whim decided to
of ssh-agent getting stuck: just out of
curiousity if this happens again, check to see if ssh-agent is using
100% of a CPU. If so then search for "ssh-agent" "100% CPU" to see
I did not find much with that search. I found
https://cygwin.com/pipermail/cygwin/2010-January
Jason Pyeron writes:
>> -Original Message-
>> From: Henry S. Thompson
>> Sent: Friday, April 1, 2022 5:21 AM
>>
>> Jim Garrison via Cygwin writes:
>>
>> > My Cygwin ssh client stopped working... It would successfully connect to
>> > .
playing the command
> > prompt. See debug output attached, as well as cygcheck output.
> >
> > I decided to run setup to see if there was a newer version of openssh.
> > In preparation for that I always terminate all Cygwin processes because
> > they will interfere with t
decided to run setup to see if there was a newer version of openssh.
In preparation for that I always terminate all Cygwin processes because
they will interfere with the update. I killed the ssh-agent process and
on a whim decided to try connecting again. This time it worked.
This would seem to
if there was a newer version of openssh.
> In preparation for that I always terminate all Cygwin processes because
> they will interfere with the update. I killed the ssh-agent process and
> on a whim decided to try connecting again. This time it worked.
>
> This would seem to indi
Greetings, Jesse Thompson!
> *TL:DR;* I'm looking for options to reliably start and manage an ssh-agent
> daemon in Cygwin.
I'm using ssh-pageant myself. But I do have a compatible wrapper for
ssh-agent.
> Using ssh-agent in cygwin seems very compelling.
Oh?
>
On Mon, Jul 19, 2021 at 12:44 PM Jesse Thompson wrote:
> *TL:DR;* I'm looking for options to reliably start and manage an ssh-agent
> daemon in Cygwin.
I recommend the "keychain" package, which is available in Cygwin.
You'd add something like the following to your sh
*TL:DR;* I'm looking for options to reliably start and manage an ssh-agent
daemon in Cygwin.
Using ssh-agent in cygwin seems very compelling. OpenSSH client
config AddKeysToAgent option and ssh-agent -t option allow me to keep keys
unlocked for limited times the way that I'd like, and u
On Nov 4 11:49, Tim Adye wrote:
> On 03/11/2019 19:00, Corinna Vinschen wrote:
> > On Sep 27 00:42, Tim Adye wrote:
> > > Hi,
> > >
> > > I have noticed a (new?) problem with using ssh-agent to start a session,
> > > eg.
> > > with
> &g
On 03/11/2019 19:00, Corinna Vinschen wrote:
On Sep 27 00:42, Tim Adye wrote:
Hi,
I have noticed a (new?) problem with using ssh-agent to start a session, eg.
with
ssh-agent xterm &
When the xterm (or whatever) command completes, the ssh-agent process is
still left running in
On Sep 27 00:42, Tim Adye wrote:
> Hi,
>
> I have noticed a (new?) problem with using ssh-agent to start a session, eg.
> with
>
> ssh-agent xterm &
>
> When the xterm (or whatever) command completes, the ssh-agent process is
> still left running in the back
On 10/4/2019 10:27 AM, Ken Brown wrote:
> On 9/29/2019 4:05 PM, Ken Brown wrote:
>> On 9/27/2019 10:12 AM, Ken Brown wrote:
>>> On 9/27/2019 9:37 AM, Norton Allen wrote:
>>>> On 9/26/2019 10:50 PM, Ken Brown wrote:
>>>>>
>>>>>> As a s
On 9/29/2019 4:05 PM, Ken Brown wrote:
> On 9/27/2019 10:12 AM, Ken Brown wrote:
>> On 9/27/2019 9:37 AM, Norton Allen wrote:
>>> On 9/26/2019 10:50 PM, Ken Brown wrote:
>>>>
>>>>> As a simple test example, consider:
>>>>>
>>>
On 9/27/2019 10:12 AM, Ken Brown wrote:
> On 9/27/2019 9:37 AM, Norton Allen wrote:
>> On 9/26/2019 10:50 PM, Ken Brown wrote:
>>>
>>>> As a simple test example, consider:
>>>>
>>>> /bin/ssh-agent /bin/sleep 10
>>>>
>>>&
On 9/27/2019 11:09 AM, Ken Brown wrote:
On 9/27/2019 10:27 AM, Vanda Vodkamilkevich wrote:
Hi,
this may probably be not fully related but I see from time to time a
strange behavior of ssh-agent (running in the background and initially
started by keychain launched in .bashrc) : the agent is
On 9/27/2019 10:27 AM, Vanda Vodkamilkevich wrote:
> Le ven. 27 sept. 2019 à 16:13, Ken Brown a écrit :
>
>> On 9/27/2019 9:37 AM, Norton Allen wrote:
>>> On 9/26/2019 10:50 PM, Ken Brown wrote:
>>>>
>>>>> As a simple test example, co
Le ven. 27 sept. 2019 à 16:13, Ken Brown a écrit :
> On 9/27/2019 9:37 AM, Norton Allen wrote:
> > On 9/26/2019 10:50 PM, Ken Brown wrote:
> >>
> >>> As a simple test example, consider:
> >>>
> >>> /bin/ssh-agent /bin/sleep 10
On 9/27/2019 9:37 AM, Norton Allen wrote:
> On 9/26/2019 10:50 PM, Ken Brown wrote:
>>
>>> As a simple test example, consider:
>>>
>>> /bin/ssh-agent /bin/sleep 10
>>>
>>> While the sleep is still running, ps shows:
>>>
>>>
On 9/26/2019 10:50 PM, Ken Brown wrote:
As a simple test example, consider:
/bin/ssh-agent /bin/sleep 10
While the sleep is still running, ps shows:
PID PPID PGID WINPID TTY UID STIME COMMAND
1694 1693 1694 1576 ? 22534 00:01:10
On 9/26/2019 7:42 PM, Tim Adye wrote:
> Hi,
>
> I have noticed a (new?) problem with using ssh-agent to start a session, eg.
> with
>
> ssh-agent xterm &
>
> When the xterm (or whatever) command completes, the ssh-agent process is
> still
> left running
On 9/26/2019 7:42 PM, Tim Adye wrote:
Is it just me that sees this, or could it be a bug in ssh-agent or
Cygwin?
I see the same thing (and have never heard of HitmanPro)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
Hi,
I have noticed a (new?) problem with using ssh-agent to start a session,
eg. with
ssh-agent xterm &
When the xterm (or whatever) command completes, the ssh-agent process is
still left running in the background. It should stop once its subprocess
is done.
As a simple test exa
It's fine. Maybe there are old sockets remaining on /tmp/ directory? Try
deleting all files and folders in the /tmp/ dir and relaunch ssh-agent.
I usually launch ssh-agent with this command
```
eval $(ssh-agent)
```
After launching ssh-agent with the above command, there are two
enviro
On Sep 13 10:46, DJ Sylvester wrote:
> I moved from 32- to 64-bit Cygwin (fully uninstalled 32, then installed
> 64). Since, I've spent days trying to get ssh to work. Just can't get there.
>
> $ ssh -V
> OpenSSH_6.6.1p1, OpenSSL 1.0.1i 6 Aug 2014
>
> $ ssh-ag
I moved from 32- to 64-bit Cygwin (fully uninstalled 32, then installed
64). Since, I've spent days trying to get ssh to work. Just can't get there.
$ ssh -V
OpenSSH_6.6.1p1, OpenSSL 1.0.1i 6 Aug 2014
$ ssh-agent bash (also tried "eval `ssh-agent -s`")
$ ps -ef | grep
Hello,
I prepared a patch to add a new option in ssh-agent:
$ ssh-agent -x
setx SSH_AUTH_SOCK /tmp/ssh-kVGrQ1K2lcMW/agent.3664
setx SSH_AGENT_PID 2704
echo Agent pid 2704;
It works the same way than -c or -s flag, but offers to use setx.
setx writes variables to the master environment in the
Christopher Faylor wrote at 12:41 -0400 on May 2, 2012:
> Should be fixed in the upcoming snapshot for today:
Confirmed. Thanks.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscrib
On Tue, May 01, 2012 at 09:56:44PM -0400, Christopher Faylor wrote:
>On Tue, May 01, 2012 at 12:01:21PM -0600, John Hein wrote:
>>% ssh-agent sh -c ssh-add
>>Could not open a connection to your authentication agent
>
>Yep. I broke it. I'll fix it ASAP.
Should be fixe
On Tue, May 01, 2012 at 12:01:21PM -0600, John Hein wrote:
>% ssh-agent sh -c ssh-add
>Could not open a connection to your authentication agent
Yep. I broke it. I'll fix it ASAP.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cyg
% ssh-agent sh -c ssh-add
Could not open a connection to your authentication agent
This happens with the following combinations currently available via
setup.exe: cygwin 1.7.13-1, 1.7.14-2, openssh 5.9p1-1 and
openssh 6.0p1-1.
Running it like so...
% eval `ssh-agent`
% ssh-add
... works as
;> On 2/6/2012 4:02 PM, Sponge Bob wrote:
>>> Just updated to latest CYGWIN in Windows XP. After running ssh-agent, the
>>> command prompt
>>> window that it ran in will hang on "exit". If the window is forcibly
>>> killed, it will
>>&
On Feb 6 19:30, Sponge Bob wrote:
> Rolling back the "cygwin" package from 1.7.10-1 to 1.7.9-1 makes problem go
> away.
>
> On 2/6/2012 4:02 PM, Sponge Bob wrote:
> > Just updated to latest CYGWIN in Windows XP. After running ssh-agent, the
> > command pro
Rolling back the "cygwin" package from 1.7.10-1 to 1.7.9-1 makes problem go
away.
On 2/6/2012 4:02 PM, Sponge Bob wrote:
> Just updated to latest CYGWIN in Windows XP. After running ssh-agent, the
> command prompt
> window that it ran in will hang on "exit". If
Just updated to latest CYGWIN in Windows XP. After running ssh-agent, the
command prompt
window that it ran in will hang on "exit". If the window is forcibly killed,
it will
take the ssh-agent down with it. If the ssh-agent is forcibly killed, the
"exiting"
window w
29.01.2012 10:21, Corinna Vinschen:
> This is supposed to be fixed in Cygwin 1.7.10. I just tried it and it
> worked for me. Please fetch a recent snapshot DLL from
> http://cygwin.com/snapshots/ and try again.
Indeed. I installed the 20120123 snapshot and didn't see any pro
On Jan 28 23:01, Markus Schönhaber wrote:
> 28.01.2012 22:00, Philip Lowman:
> > There appears to be a regression in the most recent OpenSSH cygwin
> > package (5.9p1-1, built 1/18/2012) related to the ssh-agent program.
>
> I see that too.
>
> > The ssh-add pro
28.01.2012 22:00, Philip Lowman:
> There appears to be a regression in the most recent OpenSSH cygwin
> package (5.9p1-1, built 1/18/2012) related to the ssh-agent program.
I see that too.
> The ssh-add program is unable to add SSH keys because the ssh-agent
> program doesn&#x
There appears to be a regression in the most recent OpenSSH cygwin
package (5.9p1-1, built 1/18/2012) related to the ssh-agent program.
The ssh-add program is unable to add SSH keys because the ssh-agent
program doesn't appear to be creating its socket file properly in
/tmp.
Platform: Wind
Another related 'recent update ?' message at cygwin-xfree:
http://old.nabble.com/Could-not-open-a-connection-to-your-authentication-agent.-tt32667563.html
"Not sure if this is directly related to the recent update, but after I
"did the update, I could not open an conn
and exit.
> >
> > On modified cygwin 1.7.9-1, the socket does not disappear
> > (until shortly, 5 seconds?, after I type exit.) No problem with strace.
> >
> >> It's tricky to debug because
> >> ssh-agent has no debug mode and for some reason i
e socket does not disappear
> (until shortly, 5 seconds?, after I type exit.) No problem with strace.
>
>> It's tricky to debug because
>> ssh-agent has no debug mode and for some reason it doesn't occur under
>> strace.
>
> Might this help ?
>-d
onds?, after I type exit.) No problem with strace.
> It's tricky to debug because
> ssh-agent has no debug mode and for some reason it doesn't occur under
> strace.
Might this help ?
-d Debug mode.
"ssh-agent -d" reacts to
SSH_AU
On Oct 17 11:07, Corinna Vinschen wrote:
> On Oct 14 13:02, Zdzislaw Meglicki wrote:
> > After the latest upgrade (yesterday) I found that ssh-agent no longer
> > works. It
> > looks like if fails to create a socket. Here is an illustration:
> >
> > gusta
On Oct 14 13:02, Zdzislaw Meglicki wrote:
> After the latest upgrade (yesterday) I found that ssh-agent no longer works.
> It
> looks like if fails to create a socket. Here is an illustration:
>
> gustav@Crawley 503 $ ssh-agent bash -l
> gustav@Crawley 501 $ ls -r /tmp
After the latest upgrade (yesterday) I found that ssh-agent no longer works. It
looks like if fails to create a socket. Here is an illustration:
gustav@Crawley 503 $ ssh-agent bash -l
gustav@Crawley 501 $ ls -r /tmp
ssh-zHtmAVFZ1412
gustav@Crawley 502 $ !!
ls -r /tmp
gustav@Crawley 503 $ env
On 6/22/2011 12:58 AM, Corinna Vinschen wrote:
> On Jun 21 16:49, David Rothenberger wrote:
>> C:\Users\drothe>bash --norc
>> bash-4.1$ mintty bash --norc -c 'ssh-agent'
>
> I don't understand the sense in this one. Shouldn't that be
>
>
On Jun 21 16:49, David Rothenberger wrote:
> I'm having a problem with recent snapshots, including the 20110616
> snapshot. I normally start ssh-agent using keychain as part of my
> bash startup. The problem I have is that once the bash process that
> starts the ssh-agent process
I'm having a problem with recent snapshots, including the 20110616
snapshot. I normally start ssh-agent using keychain as part of my
bash startup. The problem I have is that once the bash process that
starts the ssh-agent process exits, subsequent starts of mintty
fail.
Here's
On Apr 21 23:12, Nex Magik wrote:
> It looks like something is making the socket connection go bad, but I
> can't think of anything at the moment.
Firewall?
>27 27502786 [main] ssh-add 912 __set_winsock_errno: connect:1133 - winsock
> error 10061 -> errno 111
$ net helpmsg 10061
No connect
Having trouble with ssh-agent since upgrading cygwin to 1.7.x.
I start the ssh-agent, which is fine, but then if I try and to a
"ssh-add" or "ssh", that process hangs and ssh-agent starts using 100%
of a cpu.
I've managed to track down what was causing this probl
On Jan 6 14:19, E wrote:
> Hi.
>
> Having trouble with ssh-agent since upgrading cygwin to 1.7.x.
>
> I start the ssh-agent, which is fine, but then if I try and to a
> "ssh-add" or "ssh", that process hangs and ssh-agent starts using
> 100% of a cpu.
On 01/05/2010 11:50 PM, E wrote:
>> C: /c user binary,noacl
> Any difference if you remove this mount (or the 'noacl' flag at least)?
No, makes no difference. Tried with "acl" and without the mount altogether.
OK, was a longshot but...
(Would I need to reboot between updates to /etc/fstab
>> C: /c user binary,noacl
> Any difference if you remove this mount (or the 'noacl' flag at least)?
No, makes no difference. Tried with "acl" and without the mount altogether.
(Would I need to reboot between updates to /etc/fstab, or as long as all
cygwin processes are closed, and then reope
On 01/05/2010 10:19 PM, E wrote:
C: /c userbinary,noacl
Any difference if you remove this mount (or the 'noacl' flag at least)?
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton
Hi.
Having trouble with ssh-agent since upgrading cygwin to 1.7.x.
I start the ssh-agent, which is fine, but then if I try and to a
"ssh-add" or "ssh", that process hangs and ssh-agent starts using 100%
of a cpu.
Note: If I run ssh-agent in debug mode ("ssh-agent
I want to re-anime this thread because until now i did not figure out what
the problem is, and using ssh from an admin station without ssh-agent is
annoying.
The problem appears only when ssh-agent is _not_ started with the -d
"==debug" option. So this means that only when ssh-agent f
is what I consider a hack. I'd prefer
something more polished.
C:\cygwin\bin\bash.exe -c "eval `/usr/bin/ssh-agent`; /usr/bin/ssh-add; exit;"
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
.
This behaviour started last fall after a windows update, if I recall correctly.
On Tue, May 05, 2009 at 06:15:45AM -0400, Corinna Vinschen wrote:
> On May 5 10:03, Christian Anton wrote:
> > Now i have absolutely no idea what the problem is, i only see that
> > ssh-agent
&g
On May 5 10:03, Christian Anton wrote:
> Now i have absolutely no idea what the problem is, i only see that ssh-agent
> starts to get crazy eating all cpu time it can get when ssh-add is trying to
> access its socket.
I can't reproduce this problem.
> Do you have any idea
unix/linux world.
Since a few days i have a strange problem with ssh-agent whithout having
changed anything in my cygwin configuration. I have not full control over
my windows client because as it is a corporate client the patches and
system changes are globally deployed via netinstaller-script.
i
I tried updating cygwin1.dll up to version 1.7 on my production system
and it (system) failed to start. So I backed it out for now unless
someone can give me some help is upgrading to 1.7 as I have NO
experience with 1.7. Here are my errors:
Huh? No /etc/fstab file in \??\C:\cygwin\etc\fsta
Paul McFerrin wrote:
I would be happy to try it. I'm currently running version "-
Paul1.5.25-15". How do I download version 1.7? Setup is giving me
1.5.25-14!
As expected. If you want 1.7, go to the cygwin-announce mailing list
and read one of the (preferably the latest) 1.7 announcements
I would be happy to try it. I'm currently running version "-
Paul1.5.25-15". How do I download version 1.7? Setup is giving me
1.5.25-14!
- Paul
Corinna Vinschen wrote:
On Feb 22 18:24, Paul McFerrin wrote:
I've been having the same problem for the past two weeks. Just didn't
know wh
On Feb 22 18:24, Paul McFerrin wrote:
> I've been having the same problem for the past two weeks. Just didn't
> know where to look. Thanks for sharing. Maybe we can get someone on
> this.
>
> Wget would just HANG intermittently in the Connecting phase.
I don't observe this problem. Does upd
cts ssh-add which seems to
hang trying to connect to the ssh-agent on localhost, so it's not related to
connecting to other machines.
This is something that started happening recently, in the last few weeks.
Windows Update has run a few times and I thought it may have updated my
network dr
t
will stop and I can try again. This also affects ssh-add which seems to
hang trying to connect to the ssh-agent on localhost, so it's not related to
connecting to other machines.
This is something that started happening recently, in the last few weeks.
Windows Update has run a few times
message in context:
http://www.nabble.com/OpenSSH-ssh-add-ssh-agent-sitting-around-doing-nothing-forever-tp21930968p21930968.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://
Charles Wilson wrote:
It seems to do what I want, but as you say, keychain does slow down the
login process quite a bit. Other drawbacks to my approach:
(1) the console user's ssh-agent does not survive logoff (but remote
logons' ssh-agents do, since they all live in session 0).
Karl M wrote:
Karl M wrote:
Just a comment...keychain is pretty heavy for what you get in
Cygwin.
My solution was to launch ssh-agent as a service (one for each
user that wants it). That service spawns the agent and updates
the user environment in the registry so that other processes can
find
Dave Korn's message received 3/20/2007 1:28 PM:
On 20 March 2007 17:21, S Reed wrote:
ssh-agent was working fine for me over a year ago. I am sorry I cannot
tell you what version I was running then. I upgraded a few times since
then (now running 1.5.22) and I started getting "Could
On 20 March 2007 17:21, S Reed wrote:
> ssh-agent was working fine for me over a year ago. I am sorry I cannot
> tell you what version I was running then. I upgraded a few times since
> then (now running 1.5.22) and I started getting "Could not open a
> connection to your aut
ssh-agent was working fine for me over a year ago. I am sorry I cannot
tell you what version I was running then. I upgraded a few times since
then (now running 1.5.22) and I started getting "Could not open a
connection to your authentication agent." from ssh-add. I found that if
in/install -c
PERL=/usr/bin/perl
SED=/usr/bin/sed
ENT=
XAUTH_PATH=/usr/X11R6/bin/xauth
LDFLAGS=-L. -Lopenbsd-compat/
EXEEXT=.exe
INSTALL_SSH_PRNG_CMDS=
INSTALL_SSH_RAND_HELPER=
TARGETS=ssh$(EXEEXT) sshd$(EXEEXT) ssh-add$(EXEEXT) ssh-keygen$(EXEEXT)
ssh-keyscan${EXEEXT} ssh-keysign${EXEEXT} ssh
Hi,
I made a modified version of ssh-agent so it can run under cygrunsrv
under the local system account. This seems to work fine without having
to disable or uninstall McAfee.
Note: this is not an official update. It is a version I made for my own
purposes but others might find it usable too
Hmm, yup, I bet that's it. See (1) for another example (note: I am also
using Thunderbird). So, perhaps the question is why Jason complained in
the first place, since this seems to be archive policy (and no one has
complained at *me* for doing the same thing). Probably just overlooking
"that's how
The Content-Disposition is set to "inline" rather than "attachment".
Can't offer any suggestions as to how to change that, though. :-(
--Ken Nellis
-Original Message-
Not that I'm especially familiar with what I'm looking at, but that
looked OK to me.
--
Matthew
Will your shell have
Tim Beuman wrote:
Matthew,
There is a line "Content-Disposition: inline" which causes the
attachments to be shown inline. Could be the file-type that causes
Thunderbird to add this line to the section header. I will check if I
can convince Thunderbird to not include this line when sending .tx
On 10/11/2006 9:40 AM, Tim Beuman wrote:
> There is a line "Content-Disposition: inline" which causes the
> attachments to be shown inline. Could be the file-type that causes
> Thunderbird to add this line to the section header. I will check if I
> can convince Thunderbird to not include this li
On 11 October 2006 16:33, mwoehlke wrote:
> (Since this is rather OT, is there a better place to discuss possible
> shortcomings of the mail archiver?)
Well, yes. You already know where that place is. F'ups-to: set.
cheers,
DaveK
--
Can't think of a witty .sigline today
mwoehlke wrote:
Larry Hall (Cygwin) wrote:
mwoehlke wrote:
Tim Beuman wrote:
Hi Jason,
The "Ridiculous amount of stuff" was sent out as atachments but I
guess somehow it ended up inline. Sorry for that.
Um... Huh. Thunderbird shows it as attachment. The web archive does
not. Anyone that kn
s.
Jason,
I tried rebaseall as suggested already but that didn't help. ssh and
sshd run fine, as does sftp for that matter. Just ssh-agent seems to be
affected when McAfee is installed.
I will try to modify ssh-agent source code so it doesn't fork (i.e., one
of the effects of -d)
Larry Hall (Cygwin) wrote:
mwoehlke wrote:
Tim Beuman wrote:
Hi Jason,
The "Ridiculous amount of stuff" was sent out as atachments but I
guess somehow it ended up inline. Sorry for that.
Um... Huh. Thunderbird shows it as attachment. The web archive does
not. Anyone that knows the mailer so
mwoehlke wrote:
Tim Beuman wrote:
Hi Jason,
The "Ridiculous amount of stuff" was sent out as atachments but I
guess somehow it ended up inline. Sorry for that.
Um... Huh. Thunderbird shows it as attachment. The web archive does not.
Anyone that knows the mailer software have a guess what we
Tim Beuman wrote:
Hi Jason,
The "Ridiculous amount of stuff" was sent out as atachments but I guess
somehow it ended up inline. Sorry for that.
Um... Huh. Thunderbird shows it as attachment. The web archive does not.
Anyone that knows the mailer software have a guess what went wrong?
--
Ma
anning and email) but to no
avail. With the previous version of McAfee (version 8 I think) I was
able to diable enough to get it working.
When I run ssh-agent with the -d flag (which also keeps it in the
foregound), it works. Only when ssh-agent is started as daemon does the
problem show up. Looks
DePriest, Jason R. wrote:
On 10/10/06, Tim Beuman <> wrote:
I still have problems with ssh-agent/ssh-add when I install McAfee.
Browsing over the internet didn't yield a working solution. Before I
could stop McAfee and it would work but with the latest version of
McAfee (version 10?
. With the previous version of McAfee (version 8 I think) I was
able to diable enough to get it working.
When I run ssh-agent with the -d flag (which also keeps it in the
foregound), it works. Only when ssh-agent is started as daemon does the
problem show up. Looks like a privilege problem to me
On 10/10/06, Tim Beuman <> wrote:
Hi,
I still have problems with ssh-agent/ssh-add when I install McAfee.
Browsing over the internet didn't yield a working solution. Before I
could stop McAfee and it would work but with the latest version of
McAfee (version 10?) disabling McAfee d
Hi All...
From: Jörg Schaible Reply-To: To: "[ML] CygWin " Subject: RE: ssh-agent
variables available to any user process
Date: Wed, 30 Aug 2006 08:02:46 +0200
Lapo Luchini wrote on Wednesday, August 30, 2006 12:42 AM:
> Under FreeBSD, I launch ssh-agent in my .xsession s
Lapo Luchini wrote on Wednesday, August 30, 2006 12:42 AM:
> Under FreeBSD, I launch ssh-agent in my .xsession script and its
> environment is automatically inherited by every shell I then
> open in my
> X11 session.
> No such luck with Windows, but I found a way to propagate
Under FreeBSD, I launch ssh-agent in my .xsession script and its
environment is automatically inherited by every shell I then open in my
X11 session.
No such luck with Windows, but I found a way to propagate a environment
variable to any (future) user process after the user is already logged.
(or
Hi...
It is just a little program I wrote to send the message. It is attached.
The method I used works on XP and 2000. I have not tested on any other
platforms.
HTH,
...Karl
From: CyberZombie Subject: Re: how to make ssh-agent automatically
Date: Thu, 01 Dec 2005 11:03:20 -0600
I am
is not the only way. I no longer
use keychain.
I launch ssh-agent from a bash script that is run as a service from
cygrunsrv; it is run as the user, not as SYSTEM. This makes the
ssh-agent process survive Windows logout; I only have to enter a
passphrase after reboot. The bash script edit
You're right, I avoided the use of passphrases and carefully considered
the loss of security imposed by that and thus I do not need ssh-agent...
It's been so long ago, that I just forgot about those consequences...
matthias
H.S. wrote:
> Morche Matthias wrote:
>> You j
Morche Matthias wrote:
> You just want to connect from one host to another one. It's totally
> sufficient to set up the key and copy the public part into authorized
> keys on the remote host. I never used ssh-agent nor ssh-add and
1. I did that. So why I am asked for my SSH passphr
; sufficient to set up the key and copy the public part into authorized
>> keys on the remote host. I never used ssh-agent nor ssh-add and
>> passwordless logins to several hosts and Windows are hourly routine.
>> Why do you need them?
>
> Did you ever heard t
On Dec 1 08:34, Morche Matthias wrote:
> You just want to connect from one host to another one. It's totally
> sufficient to set up the key and copy the public part into authorized
> keys on the remote host. I never used ssh-agent nor ssh-add and
> passwordless logins to several
You just want to connect from one host to another one. It's totally
sufficient to set up the key and copy the public part into authorized
keys on the remote host. I never used ssh-agent nor ssh-add and
passwordless logins to several hosts and Windows are hourly routine. Why
do you need
Morche Matthias wrote:
Simpler than using keychain and ssh-agent, Hmm... did You ever try to
just generate your key by ssh-keygen and then copy the public key
~/.ssh/id_dsa.pub eg to Your remote host into ~/.ssh/authorized_keys.
Would You consider this to be simpler?
matthias
(Yes, I have
1 - 100 of 181 matches
Mail list logo
