On 2024-01-05 06:41, FOPPE, JEFFERY via Cygwin wrote:
Is the openssh 9.6 package going to be released soon?
The Air Force has given us a Jan 11th suspense to have it installed.
Jeff Foppe
AFLCMC/WFRQ
Can not have it installed if it has not been released!
Upgrade delays vary from days to weeks
Greetings, Jim Garrison via Cygwin!
Replying to the first post to reduce quoting, but I did read the entire thread.
> My Cygwin ssh client stopped working... It would successfully connect to
> the remote (Debian) host but then hang without displaying the command
> prompt. See debug output attach
On 4/3/2022 9:50 AM, Henry S. Thompson wrote:
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
...
There are reports out there
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
>> > ...
>> There are reports out there of ssh-agent getting s
> -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
> > the remote (Debian) host but then hang without displaying the command
> > prompt. Se
On 4/1/2022 2:21 AM, Henry S. Thompson wrote:
Jim Garrison via Cygwin writes:
My Cygwin ssh client stopped working... It would successfully connect to
the remote (Debian) host but then hang without displaying the command
prompt. See debug output attached, as well as cygcheck output.
I decided
Jim Garrison via Cygwin writes:
> My Cygwin ssh client stopped working... It would successfully connect to
> the remote (Debian) host but then hang without displaying the command
> prompt. See debug output attached, as well as cygcheck output.
>
> I decided to run setup to see if there was a newe
On 05.10.2020 18:05, Bruce Halco wrote:
Is there any information available on when openssh 8.4 will be available?
Bruce
No.
It all depends when the package manager have time to dedicate to it.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/
On Thu, Feb 27, 2020 at 4:10 PM TestUser1 wrote:
So is this expected to work fine in my environment, Windows Server 2016 (OS
> Version 10.0.14393), without the workaround?
>
I can't reproduce on Windows Server 8.1/Server 2012 R2 or later.
But you can certainly try the workaround.
Bill
--
Prob
So is this expected to work fine in my environment, Windows Server 2016 (OS
Version 10.0.14393), without the workaround?
Thanks!
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.
On Thu, Feb 27, 2020 at 11:09 AM n0nc3 wrote:
It appears Cygwin SSHD's functionality is partially broke in the later
> versions, where SSHD runs as SYSTEM (no longer cyg_server).
>
> On reboot, any attempt to SSH into the server *before* any previous logon
> attempt (RDP/locally/etc) is quickly d
I was able to build OpenSSL with FIPS and OpenSSH using those OpenSSL libraries
from scratch and install on 32-bit Cygwin.
I'm documenting what I did here and would like some feedback.
Install Cygwin 32-bit with the following extras:
---
Rollback Ope
On 2019-06-24 12:50, Pinzone, Gerard wrote:
> I've been able to build OpenSSL 1.0.2 with FIPS support on Cygwin 32-bit and
> native Windows using Visual Studio. The 64-bit edition of Cygwin doesn't
> build the FIPS module correctly. There is a workaround, but that workaround
> invalidates the FIP
On Thu, Apr 18, 2019 at 8:46 AM Corinna Vinschen wrote:
> I know, I'm subscribed to the openssh-dev mailing list.
Understood - the intent was to inform those subscribed to the Cygwin list
who might not know already that there's something good to look forward to.
My apologies for any annoyance. T
On Apr 18 08:32, Bill Stewart wrote:
> It's here:
I know, I'm subscribed to the openssh-dev mailing list.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
signature.asc
Description: PGP signature
On 2019-03-20 09:06, Bill Stewart wrote:
> On Wed, Mar 20, 2019 at 8:53 AM Bruce Halco wrote:
>> The problem is I have 8 customers failing PCI network scans because of
>> CVE-2019-6111, so I don't think the patch for CVE-2018-20685 is going to
>> help.
>> If 8.0 is close (maybe weeks?) I can afford
On Wed, Mar 20, 2019 at 8:53 AM Bruce Halco wrote:
> The problem is I have 8 customers failing PCI network scans because of
> CVE-2019-6111, so I don't think the patch for CVE-2018-20685 is going to
> help.
>
> If 8.0 is close (maybe weeks?) I can afford to wait a while. Otherwise
> I'll have to t
The problem is I have 8 customers failing PCI network scans because of
CVE-2019-6111, so I don't think the patch for CVE-2018-20685 is going to
help.
If 8.0 is close (maybe weeks?) I can afford to wait a while. Otherwise
I'll have to take some other action. I don't like any of my
alternatives
On Mar 20 09:13, Bruce Halco wrote:
> openSSH 7.9 is subject to vulnerability CVE-2019-6111. This has been fixed
> in at least some distributions, Debian at least.
Fedora (which is our role model) doesn't and the vulnerability is not
deemed that critical by the upstream maintainers:
https://lists
> cyg Simple kirjoitti 10.1.2019 kello 16.50:
>
> On 1/9/2019 4:59 PM, Erik Soderquist wrote:
>> On Tue, Jan 8, 2019 at 11:56 PM Jari Fredriksson wrote:
>>> It is indeed removed. There is no ”Cygwin sushi” service any more.
>> I have encountered this as well, but it seems very inconsistent.
>
On 1/9/2019 4:59 PM, Erik Soderquist wrote:
On Tue, Jan 8, 2019 at 11:56 PM Jari Fredriksson wrote:
It is indeed removed. There is no ”Cygwin sushi” service any more.
I have encountered this as well, but it seems very inconsistent.
People on this list who have tried to intentionally reproduce
On Tue, Jan 8, 2019 at 11:56 PM Jari Fredriksson wrote:
> It is indeed removed. There is no ”Cygwin sushi” service any more.
I have encountered this as well, but it seems very inconsistent.
People on this list who have tried to intentionally reproduce it have
been unable to. At the same time, on
> Stephen John Smoogen kirjoitti 8.1.2019 kello 23.33:
>
> On Tue, 8 Jan 2019 at 16:20, Jari Fredriksson wrote:
>
>> Hello!
>>
>> I have used Cygwin and OpenSSH server from Windows 7 to these days with
>> Windows 10.
>>
>> In some late Windows update it seems that Microsoft has removed the
On Tue, 8 Jan 2019 at 16:20, Jari Fredriksson wrote:
> Hello!
>
> I have used Cygwin and OpenSSH server from Windows 7 to these days with
> Windows 10.
>
> In some late Windows update it seems that Microsoft has removed the
> "Cygwin sshd” -service all together!
>
>
I don't think it removed it..
On 05/31/2017 05:37 AM, Houder wrote:
On Tue, 30 May 2017 21:28:41, "Larry Hall (Cygwin)" wrote:
[snip]
Cygwin's link to the Windows user ID is through the UID/SID mapping. In
your case, you're apparently using /etc/passwd and so that's where the
mapping happens. You can map the UID of a Cygw
On 2017-05-31 13:52, Marco Atzeri wrote:
> On 29/05/2017 11:48, Houder wrote:
>> On 2017-05-29 10:39, Marco Atzeri wrote:
>>> On 29/05/2017 07:23, Houder wrote:
>>
>> [snip]
... because, that is, I think, what I am seeing:
- the userid of child sshd is still 'cyg_server' ...
-
Greetings, Houder!
> Anyone out there, who uses AD, in stead of /etc/{passwd,group},
Nobody here uses "/etc/{passwd,group}" anymore, except for very special cases.
This is not related to AD.
--
With best regards,
Andrey Repin
Wednesday, May 31, 2017 23:14:34
Sorry for my terrible english...
On 29/05/2017 11:48, Houder wrote:
On 2017-05-29 10:39, Marco Atzeri wrote:
On 29/05/2017 07:23, Houder wrote:
[snip]
... because, that is, I think, what I am seeing:
- the userid of child sshd is still 'cyg_server' ...
- and I get an elevated shell when I login ...
Not what I expected ..
On 5/31/2017 12:34 PM, Houder wrote:
> On Wed, 31 May 2017 10:59:38, cyg Simple wrote:
>> On 5/31/2017 10:16 AM, Houder wrote:
>>> On Wed, 31 May 2017 09:27:02, cyg Simple wrote:
>>>
>>> [snip]
All of this talk of /etc/passwd leads me to point you to
https://cygwin.com/cygwin-ug-net/ntsec
On Wed, 31 May 2017 10:59:38, cyg Simple wrote:
> On 5/31/2017 10:16 AM, Houder wrote:
> > On Wed, 31 May 2017 09:27:02, cyg Simple wrote:
> >
> > [snip]
> >> All of this talk of /etc/passwd leads me to point you to
> >> https://cygwin.com/cygwin-ug-net/ntsec.html.
> >
> > cyg,
> >
> > Do you wa
On 5/31/2017 10:16 AM, Houder wrote:
> On Wed, 31 May 2017 09:27:02, cyg Simple wrote:
>
> [snip]
>> All of this talk of /etc/passwd leads me to point you to
>> https://cygwin.com/cygwin-ug-net/ntsec.html.
>
> cyg,
>
> Do you want me to study that text a second, third, fourth or Xth time ...?
>
On Wed, 31 May 2017 16:16:38, Houder wrote:
[snip]
> Anyone out there, who uses AD, in stead of /etc/{passwd,group}, and is brave
> enough to delete the sshd account? Is ssh still working?
i.e. NOT from AD, but delete as an account (net user sshd /delete).
Regards,
Henri
--
Problem reports:
On Wed, 31 May 2017 09:27:02, cyg Simple wrote:
[snip]
> All of this talk of /etc/passwd leads me to point you to
> https://cygwin.com/cygwin-ug-net/ntsec.html.
cyg,
Do you want me to study that text a second, third, fourth or Xth time ...?
However, let me take another angle now ...
Active Dir
On 5/31/2017 5:37 AM, Houder wrote:
> On Tue, 30 May 2017 21:28:41, "Larry Hall (Cygwin)" wrote:
>
> [snip]
>> Cygwin's link to the Windows user ID is through the UID/SID mapping. In
>> your case, you're apparently using /etc/passwd and so that's where the
>> mapping happens. You can map the UID
On Tue, 30 May 2017 21:28:41, "Larry Hall (Cygwin)" wrote:
[snip]
> Cygwin's link to the Windows user ID is through the UID/SID mapping. In
> your case, you're apparently using /etc/passwd and so that's where the
> mapping happens. You can map the UID of a Cygwin user to any valid Windows
> SID
On 05/30/2017 09:50 AM, Houder wrote:
On Mon, 29 May 2017 19:14:30, Houder wrote:
[snip]
As if the "sshd" account is NEVER, NEVER used during the _whole_ process
(that is, there is NO privilege separation, as far as I can tell).
.. wanted to share this experience with you.
- deleted user/a
On Mon, 29 May 2017 19:14:30, Houder wrote:
[snip]
> As if the "sshd" account is NEVER, NEVER used during the _whole_ process
> (that is, there is NO privilege separation, as far as I can tell).
.. wanted to share this experience with you.
- deleted user/account 'sshd' # net user sshd /delete
On 2017-05-29 21:57, Andrey Repin wrote:
Greetings, Houder!
- however, the userid of the grandchild of the sshd listener, is
STILL
cyg_server ... NOT sshd!
Exactly. cyg_server is the user which does impersonation.
You've been told that when you've been setting up your host.
http:
Greetings, Houder!
> - however, the userid of the grandchild of the sshd listener, is STILL
> cyg_server ... NOT sshd!
Exactly. cyg_server is the user which does impersonation.
You've been told that when you've been setting up your host.
> As if the "sshd" account is NEVER, NEVER used duri
On 2017-05-29 11:48, Houder wrote:
On 2017-05-29 10:39, Marco Atzeri wrote:
On 29/05/2017 07:23, Houder wrote:
[snip]
... because, that is, I think, what I am seeing:
- the userid of child sshd is still 'cyg_server' ...
- and I get an elevated shell when I login ...
Not what I expected ..
On 2017-05-29 11:48, Houder wrote:
The following might help help clarify "my words" in my previous
post ... (pictures!)
https://security.stackexchange.com/questions/115896/can-someone-explain-how-sshd-does-privilege-separation
http://www.citi.umich.edu/u/provos/ssh/privsep.html
h
On 2017-05-29 11:48, Houder wrote:
- pre-authentication:
Shell 1:
64-@@ ssh -p 222 -l Henri 192.168.178.15
Enter passphrase for key '/home/Henri/.ssh/id_rsa': < passphrase not
yet entered
Shell 2: (observer)
64-@@# ps -af
UID PIDPPID TTYSTIME COMMAND
Henri230
On 2017-05-29 10:39, Marco Atzeri wrote:
On 29/05/2017 07:23, Houder wrote:
[snip]
... because, that is, I think, what I am seeing:
- the userid of child sshd is still 'cyg_server' ...
- and I get an elevated shell when I login ...
Not what I expected ...
Gr. Henri
Hi Houder,
please re
On 29/05/2017 07:23, Houder wrote:
Hi,
Privilege separation in sshd defaults to "sandbox" (as far as
I understand, "openssh" has implemented a new mechanism).
... now I remember Corinna writing, that 'sandbox will not be
an option for Cygwin' ... or words to that effect.
Does this mean, that u
On Tue, Aug 30, 2016 at 2:32 PM, Massimo Balestra wrote:
> Forget it
>
> I copied the sshd_config from /etc/defaults/etc/sshd_config to /etc and now
> it works again as it should.
>
> Now I need to figure out what was the parameter that broke it
I look forward to those results too.
Also, please d
Forget it
I copied the sshd_config from /etc/defaults/etc/sshd_config to /etc and
now it works again as it should.
Now I need to figure out what was the parameter that broke it
Thank you
On 8/30/2016 10:44 AM, Massimo Balestra wrote:
Hi,
I have installed several years ago my cygwin openss
On May 27 09:41, Michael Brux wrote:
> Hi Cygwin mailinig list,
>
> In /usr/share/doc/Cygwin/openssh.README the --name option is missing.
Thanks, I sent a matching patch upstream.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer
On Thu, Jan 28, 2016 at 10:44 PM, Glenn G wrote:
> Very strange. You could log in as the user, regenerate the keys and try
> porting it over again. User id shouldn't have anything to do with this
> though. Sounds like impersonation is messed up for sshd user on machine b.
>
>
> Sent from my iP
On Aug 16 17:24, Max Polk wrote:
> On a new 64-bit Cygwin install, no /etc/ssh* files or dirs exist,
That's what /usr/bin/ssh-host-config is for.
> I copied over id_dsa and id_dsa.pub into my ~/.ssh, nothing else, and
> got the directory and file permissions right.
>
> Kept running into this fai
On 1 April 2015 at 21:03, wilson wrote:
>
> I saw the following on https://www.cygwin.com/ml/cygwin/2015-03/msg00477.html
> and I've been having the same issue with keychain. The fix to the
> /usr/bin/keychain shell script worked as shown, but I've added information
> about where the fix belong
I saw the following on
https://www.cygwin.com/ml/cygwin/2015-03/msg00477.html and I've been
having the same issue with keychain. The fix to the /usr/bin/keychain
shell script worked as shown, but I've added information about where the
fix belongs (in the script) later in this message. I suggest
On 4/11/2014 5:49 PM, Auteria W. Winzer Jr. wrote:
I noticed an anomaly within both 32bit and 64bit distributions of
OpenSSH. The package maintainer inadvertently placed the architectures in
their opposition. At 1st glance I thought I had clicked the wrong icon
thinking I was using 64bit within
On Feb 20 09:36, Corinna Vinschen wrote:
> On Feb 19 17:18, Karl M wrote:
> > >>> Subject: Re: OpenSSH port forwarding bug
> > >>> Date: Wed, 12 Feb 2014 22:44:54 -0500
> > >>>
> > >>>> Hi All..
On Feb 19 17:18, Karl M wrote:
> >>> Subject: Re: OpenSSH port forwarding bug
> >>> Date: Wed, 12 Feb 2014 22:44:54 -0500
> >>>
> >>>> Hi All...
> >>>> The following example shows the port forwarding problem.
> >>>>
> Subject: RE: OpenSSH port forwarding bug
> Date: Fri, 14 Feb 2014 22:11:03 -0800
>
>> Subject: RE: OpenSSH port forwarding bug
>> Date: Fri, 14 Feb 2014 12:48:53 -0800
>>
>> Hi Andrew...
>>
>> This is what I usually use in a proxycommand. So the examp
> Subject: RE: OpenSSH port forwarding bug
> Date: Fri, 14 Feb 2014 12:48:53 -0800
>
> Hi Andrew...
>
> This is what I usually use in a proxycommand. So the example localized
> it to just one layer. You can see that it connects to an ssh server and
> then drops whe
> Hi All...
> The following example shows the port forwarding problem.
>
>
> ~
>
> $ ssh raven -W coyote:22
> getsockname failed: Bad file descriptor
> SSH-2.0-OpenSSH_6.5
> Protocol mismatch.
> ~
>
> $ ssh raven nc coyote 22
> SSH-2.0-OpenSSH_6.5
> Protocol mismatch.
What are you trying to
On Feb 2 11:04, Ola Strömfors wrote:
>
> On Feb 1 13:54 Corinna Vinschen wrote
> >On Feb 1 09:12, Ola Stromfors wrote:
> >>Hi,
> >>
> >>After upgrading openssh from 6.4p1-1 to 6.5p1-1, ssh to host names
> >>listed in /etc/hosts fails. /etc/hosts is actually a symlink to
> >>/cygdriv/c/Windows/sy
On Feb 1 13:54 Corinna Vinschen wrote
On Feb 1 09:12, Ola Stromfors wrote:
Hi,
After upgrading openssh from 6.4p1-1 to 6.5p1-1, ssh to host names
listed in /etc/hosts fails. /etc/hosts is actually a symlink to
/cygdriv/c/Windows/system32/drivers/etc/hosts.
Not sure that's the actual reason.
On Feb 1 09:12, Ola Strömfors wrote:
> Hi,
>
> After upgrading openssh from 6.4p1-1 to 6.5p1-1, ssh to host names
> listed in /etc/hosts fails. /etc/hosts is actually a symlink to
> /cygdriv/c/Windows/system32/drivers/etc/hosts.
Not sure that's the actual reason. getaddrinfo is a WinSock call
w
On Apr 2 16:33, Pach Roman (DGS-EC/ESG2) wrote:
> Corinna wrote in the cygwin-announce from Tue, 26 Mar 2013 15:48:16 +0100:
>
> Bugfixes:
>
> * ssh(1): Record "Received disconnect" messages at ERROR rather than
>INFO priority. bz#2057.
>
> I'm using gitolite under cygwin. After performing
On Mon, Feb 04, 2013 at 01:20:39PM +0100, Corinna Vinschen wrote:
>On Jan 29 17:01, Linda Walsh wrote:
>> Who is the person who ports/packages openssh for cygwin?
>
>That's me.
>
>> I was wondering if they could include the HPN patches (High Performance
>> Networking)
>>
>> http://www.psc.edu/ind
On Jan 29 17:01, Linda Walsh wrote:
> Who is the person who ports/packages openssh for cygwin?
That's me.
> I was wondering if they could include the HPN patches (High Performance
> Networking)
>
> http://www.psc.edu/index.php/component/remository/HPN-SSH/OpenSSH-6.0-Patches/
>
> specifically:
On Sat, Dec 8, 2012 at 10:07 PM, Mike Richardson wrote:
> I was about to post this as a question on here, but I was able to
> solve my problem. I post it here in case anyone else comes along and
> has the same problem.
>
> I'm running Windows Server 2008 R2 Enterprise. I installed the latest
> Cy
On 10/8/2012 9:11 AM, victorwoo wrote:
My sshd failed to start after "ssh-host-config" setup.
[...]
The versions are:
cygwin 1.7.16-1
openssh 6.1p1-1
I suggest that you try a Cygwin snapshot:
http://www.cygwin.com/snapshots/
Ken
--
Problem reports: http://cygwin.com/problems.htm
On 9/19/2012 7:56 AM, Andre Rothe wrote:
Hi,
I have to use an outdated system with Windows 2000 Server and an OpenSSH service
on it. It uses OpenSSH 3.8.1p1-1 for Windows, which uses a Cygwin server v1.0 or
something.
The problem:
I try to mount a windows network share on the Cygwin server to
On Thu, May 10, 2012 at 12:10 PM, bartels wrote:
>>
>> Yes. You've changed the tool you're using when you changed your path.
>> Try '( id; PATH=/cygdrive/c/devkit/msys/1.0.11/bin:/usr/bin:;
>> /cygdrive/c/cygiwn/bin/id)'.
>>
>>
> You are right, of course.
> Now the question is how to use the devki
On 05/10/2012 05:39 PM, Larry Hall (Cygwin) wrote:
On 5/10/2012 8:51 AM, bartels wrote:
Hi All,
I have a situation where the uid changes to cyg_server unexpectedly when
changing PATH:
$ ( id; PATH=/cygdrive/c/devkit/msys/1.0.11/bin:/usr/bin:; id )
UID=1001(pleezy) GID=513(None)
groepen=513(No
On 5/10/2012 8:51 AM, bartels wrote:
Hi All,
I have a situation where the uid changes to cyg_server unexpectedly when
changing PATH:
$ ( id; PATH=/cygdrive/c/devkit/msys/1.0.11/bin:/usr/bin:; id )
UID=1001(pleezy) GID=513(None)
groepen=513(None),544(Administrators),545(Gebruikers),1000(HomeUse
> Date: Sat, 5 May 2012 10:55:56 +0200
> From: corinna
> To: cygwin
> Subject: Re: OpenSSH using root for the .ssh directory?
>
> If you run mkpasswd with the -c option to generate an entry for the
> current user, and if $HOME is set at the time, then mkpasswd misses to
On 5 May 2012 01:23, Fedin Pavel wrote:
> Look at your /etc/passwd. Here, on my machine,home directory is empty for
> my username. Perhaps mkpasswd's bug. You can fix it by manually setting the
> right path in /etc/passwd.
That fixed it, thanks!
On 5 May 2012 04:55, Corinna Vinschen wrote:
> Ind
Am 05.05.2012 07:23, schrieb Fedin Pavel:
On 05.05.2012 7:06, Chris Sutcliffe wrote:
I'm at a loss as to why it's looking in the root directory.
Look at your /etc/passwd. Here, on my machine,home directory is empty
for my username. Perhaps mkpasswd's bug. You can fix it by manually
setting
On May 5 09:23, Fedin Pavel wrote:
> On 05.05.2012 7:06, Chris Sutcliffe wrote:
> >I'm at a loss as to why it's looking in the root directory.
>
> Look at your /etc/passwd. Here, on my machine,home directory is
> empty for my username. Perhaps mkpasswd's bug. You can fix it by
> manually setting
On 05.05.2012 7:06, Chris Sutcliffe wrote:
I'm at a loss as to why it's looking in the root directory.
Look at your /etc/passwd. Here, on my machine,home directory is empty
for my username. Perhaps mkpasswd's bug. You can fix it by manually
setting the right path in /etc/passwd.
--
Kind r
On Wed, Feb 15, 2012 at 10:44:48AM +0100, Corinna Vinschen wrote:
>On Feb 14 20:49, Stepp, Charles wrote:
>> > On Feb 14 17:54, Charles Stepp wrote:
>> > Does the FAQ help?
>> >
>> > http://cygwin.com/faq-nochunks.html#faq.using.sshd-in-domain
>>
>> Yes it did! Essentially, it needs to be a domain
On Feb 14 20:49, Stepp, Charles wrote:
> > On Feb 14 17:54, Charles Stepp wrote:
> > Does the FAQ help?
> >
> > http://cygwin.com/faq-nochunks.html#faq.using.sshd-in-domain
>
> Yes it did! Essentially, it needs to be a domain user. I had to use my
> own domain ID. I added permissions through some
> On Feb 14 17:54, Charles Stepp wrote:
> >
> > Jim Garrison troux.com> writes:
> >
> > >
> > > I'm consistently getting a stack trace when attempting to run a command
> > > via
> > ssh, using a dsa key, on a remote
> > > Windows Server 2003 SP2 x64 that has Cygwin sshd installed and configured.
On Feb 14 17:54, Charles Stepp wrote:
>
> Jim Garrison troux.com> writes:
>
> >
> > I'm consistently getting a stack trace when attempting to run a command via
> ssh, using a dsa key, on a remote
> > Windows Server 2003 SP2 x64 that has Cygwin sshd installed and configured.
> The error is oc
Jim Garrison troux.com> writes:
>
> I'm consistently getting a stack trace when attempting to run a command via
ssh, using a dsa key, on a remote
> Windows Server 2003 SP2 x64 that has Cygwin sshd installed and configured.
The error is occurring at the
> remote sshd process:
>
> $ ssh q
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 problems
with ssh-agent
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 program is unable to add SSH keys beca
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't appear to be creatin
> > ssh-copy-id requires that password authentication is working, which is
> > not happening, so I tried manual moving of the files
>
> Sorry, I obviously overlooked that.
> I assume sshd_config is properly configured to allow public key
> authentication.
>
> Have you checked your /etc/passwd a
On Fri, Oct 14, 2011 at 03:28:14PM -0500, Clayton Evans wrote:
> > I'd double-check StrictModes and PubkeyAuthentication in sshd_config.
> ssh-copy-id requires that password authentication is working, which is not
> happening, so I tried manual moving of the files
Sorry, I obviously overlooked
> > > > > > debug1: Next authentication method: publickey
> > > > > > debug1: Offering RSA public key: /home/cevans/.ssh/id_rsa
> > > > > > debug3: send_pubkey_test
> > > > > > debug2: we sent a publickey packet, wait for reply
> > > > > > debug1: Authentications that can continue:
> > > > > > pub
On Fri, Oct 14, 2011 at 01:43:57PM -0500, Clayton Evans wrote:
> > > > > debug1: Next authentication method: publickey
> > > > > debug1: Offering RSA public key: /home/cevans/.ssh/id_rsa
> > > > > debug3: send_pubkey_test
> > > > > debug2: we sent a publickey packet, wait for reply
> > > > > debug1
> > > > debug1: Next authentication method: publickey
> > > > debug1: Offering RSA public key: /home/cevans/.ssh/id_rsa
> > > > debug3: send_pubkey_test
> > > > debug2: we sent a publickey packet, wait for reply
> > > > debug1: Authentications that can continue:
> > > > publickey,password,keyboard
> > > debug1: Next authentication method: publickey
> > > debug1: Offering RSA public key: /home/cevans/.ssh/id_rsa
> > > debug3: send_pubkey_test
> > > debug2: we sent a publickey packet, wait for reply
> > > debug1: Authentications that can continue:
> > > publickey,password,keyboard-interactive
> > debug1: Next authentication method: publickey
> > debug1: Offering RSA public key: /home/cevans/.ssh/id_rsa
> > debug3: send_pubkey_test
> > debug2: we sent a publickey packet, wait for reply
> > debug1: Authentications that can continue:
> > publickey,password,keyboard-interactive
> > debug1:
> debug1: Next authentication method: publickey
> debug1: Offering RSA public key: /home/cevans/.ssh/id_rsa
> debug3: send_pubkey_test
> debug2: we sent a publickey packet, wait for reply
> debug1: Authentications that can continue:
> publickey,password,keyboard-interactive
> debug1: Offering DSA
Greetings, Thorsten Kampe!
>> 4) What files from the ssh-user-config is it necessary to move to the
> other machine?
> None. Just re-run ssh-user-config.
You'd want to move your keys...
--
WBR,
Andrey Repin (anrdae...@freemail.ru) 09.10.2011, <18:56>
Sorry for my terrible english...
--
Prob
* Clayton Evans (Wed, 5 Oct 2011 17:43:45 -0500)
>
> I have four questions that are not clear to after reading
> /usr/doc/Cygwin/openssh.README.
>
> 1) When running ssh-host-config, what is the correct string to enter for the
> CYGWIN environment variable?
Just leave it blank.
> 2) When runni
On Jun 15 07:11, roadworrier wrote:
>
> I saw this problem "spawn_guts: CreateDesktop failed, Win32 error 8" listed
> in many Google results with some suggestions but without any conclusive
> solutions.
>
> My 2003 Server has 16gb of RAM, and only about 10gb were in use, so the
> issue wasn't a
I saw this problem "spawn_guts: CreateDesktop failed, Win32 error 8" listed
in many Google results with some suggestions but without any conclusive
solutions.
My 2003 Server has 16gb of RAM, and only about 10gb were in use, so the
issue wasn't a lack of RAM. However, I went and quit some program
> As usual the logs only show what happens, but they don't show why.
>
> I installed OpenSSH-5.8p1 on Windows 7 64 bit. I tried to connect from
> 32 and 64 bit Cygwin machines using ssh 5.8p1 and I tried it from a
> Linux machine with ssh 5.5p1. No problems at all. I removed the ECDSA
> host ke
On Feb 12 12:31, Andrew Ng wrote:
> I've also been experiencing connection problems with OpenSSH
> versions newer than 5.6p1-2. These problems occur with both Cygwin
> sshd (versions 5.6 to 5.8) and other UNIX sshd (e.g. Solaris).
>
> I've attached client and server debug logs of both Cygwin ssh 5
> I'm not sure what to do to fix this though.
The administrative prohibition is on the server. There's nothing you can do to
fix it, other than find a server that isn't github to proxy through.
Accelrys Limited (http://accelrys.com)
Registered office: 334 Cambridge Science Park, Cambridge, CB4 0
On 8:59 PM, Maring, Steven wrote:
From a 50K foot perspective, what I'm trying to do is punch a hole through my
corporate http proxy to get to github. By itself, cygwin, along with openssh
and corkscrew, does not have a problem (i.e. remote git commands work).
However, I would also like to
On Aug 11 16:14, carsten.porz...@spb.de wrote:
> Dear Cygwin community,
>
> unfortunately we got on some of our Windows 2003 servers this error
> message while logging on by using OpenSSH
>
>5791 [main] sshd 9288! spawn_guts: CreateDesktop failed, Win32 error 8
bash$ net helpmsg 8
Not
On 8/11/2010 10:14 AM, carsten.porz...@spb.de wrote:
Dear Cygwin community,
unfortunately we got on some of our Windows 2003 servers this error
message while logging on by using OpenSSH
5791 [main] sshd 9288! spawn_guts: CreateDesktop failed, Win32 error 8
This error message occurs after t
1 - 100 of 350 matches
Mail list logo
