On Thursday, April 16, 2020, 04:50:03 AM EDT, Andrey Repin
wrote:
>> sshd: PID 1721: fatal: seteuid 1610619958: No such device or address
>> I just did a clean install:
>> openssh 8.2p1-1
>> The uid corresponds to me:
>> uid=1610619958(+kevins)
> Can
Greetings, Kevin Schnitzius!
> sshd: PID 1721: fatal: seteuid 1610619958: No such device or address
> I just did a clean install:
> openssh 8.2p1-1
> The uid corresponds to me:
> uid=1610619958(+kevins)
Can we see the full output of `id` when you logged
On Tue, Apr 14, 2020 at 8:01 PM Kevin Schnitzius wrote:
> sshd: PID 1721: fatal: seteuid 1610619958: No such device or address
>
> I just did a clean install:
> openssh 8.2p1-1
>
> The uid corresponds to me:
> uid=1610619958(+kevins)
>
> Local users work
sshd: PID 1721: fatal: seteuid 1610619958: No such device or address
I just did a clean install:
openssh 8.2p1-1
The uid corresponds to me:
uid=1610619958(+kevins)
Local users work fine; it's only a problem with domain users.
Strictmode=no and the
On 2019-03-07 01:53, Corinna Vinschen wrote:
> On Mar 6 23:15, Brian Inglis wrote:
>> On 2019-03-06 13:59, Corinna Vinschen wrote:
>>> I'm reasonably sure there won't be any fix for these systems for at
>>> least two reasons:
>>> - All affected systems are EOLed or in the last year of their
On Mar 6 23:15, Brian Inglis wrote:
> On 2019-03-06 13:59, Corinna Vinschen wrote:
> > I'm reasonably sure there won't be any fix for these systems for at
> > least two reasons:
> > - All affected systems are EOLed or in the last year of their Extended
> > Support Cycle, all ending on
On 2019-03-06 13:59, Corinna Vinschen wrote:
> I'm reasonably sure there won't be any fix for these systems for at
> least two reasons:
> - All affected systems are EOLed or in the last year of their Extended
> Support Cycle, all ending on 2020-01-14.
> - I opened a support case for an older
On Wed, Mar 06, 2019 at 03:44:36PM -0800, Stephen Paul Carrier wrote:
> PW=`dd if=/dev/random bs=15 count=1 | base 64`
That should be 'base64' of course, without the space.
--S
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Wed, Mar 06, 2019 at 02:24:59PM -0700, Bill Stewart wrote:
...
> For my part, I'm writing a PowerShell script that does the following:
>
> 1) Create a local user account
> 2) Grant it SeBatchLogonRight
> 3) Create a scheduled task for it
Powershell is probably more elegant if you're
On Wed, Mar 6, 2019 at 2:00 PM Corinna Vinschen wrote:
> > Whether this workaround is feasible likely depends on the end user. The
> > workaround has its own limitations. Here are at least 2 that I can
think of
> > right now:
> >
> > 1. The local user must have "Log on as a batch job"
On Mar 6 13:47, Bill Stewart wrote:
> On Wed, Mar 6, 2019 at 1:14 PM Corinna Vinschen wrote:
>
> > > > > What precisely happens when Cygwin uses MSV1 S4ULogon on versions
> older
> > > > > than 6.3 before a user has logged on?
> > > >
> > > > MsV1S4ULogon returns with STATUS_NOT_SUPPORTED.
On Wed, Mar 6, 2019 at 1:14 PM Corinna Vinschen wrote:
> > > > What precisely happens when Cygwin uses MSV1 S4ULogon on versions
older
> > > > than 6.3 before a user has logged on?
> > >
> > > MsV1S4ULogon returns with STATUS_NOT_SUPPORTED. Funny status code,
> > > given it works if some user
On Mar 6 09:45, Bill Stewart wrote:
> On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
>
> > On Mar 6 08:38, Bill Stewart wrote:
> > > On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> > > > On Mar 6 15:17, Corinna Vinschen wrote:
> > > > > But the old Systems like Windows 7
On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
> On Mar 6 08:38, Bill Stewart wrote:
> > On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> > > On Mar 6 15:17, Corinna Vinschen wrote:
> > > > But the old Systems like Windows 7 don't want to play nice.
> > > >
> > > > - On Vista
On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
> > What precisely happens when Cygwin uses MSV1 S4ULogon on versions older
> > than 6.3 before a user has logged on?
>
> MsV1S4ULogon returns with STATUS_NOT_SUPPORTED. Funny status code,
> given it works if some user already logged in by
On Mar 6 08:38, Bill Stewart wrote:
> On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> > On Mar 6 15:17, Corinna Vinschen wrote:
> > > But the old Systems like Windows 7 don't want to play nice.
> > >
> > > - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> > > at all,
On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> On Mar 6 15:17, Corinna Vinschen wrote:
> > But the old Systems like Windows 7 don't want to play nice.
> >
> > - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> > at all, which required to keep the create_token method
>
On Mar 6 15:17, Corinna Vinschen wrote:
> But the old Systems like Windows 7 don't want to play nice.
>
> - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> at all, which required to keep the create_token method
> available
>
> - On Vista and Windows 7 MsV1_0S4ULogon does
On Mar 6 13:48, Corinna Vinschen wrote:
> On Mar 6 13:11, Corinna Vinschen wrote:
> > On Mar 5 17:02, Stephen Carrier wrote:
> > > Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> > > fail unless some user logs into Windows first. In this case, that is by
> > > RDP,
On Mar 6 13:11, Corinna Vinschen wrote:
> On Mar 5 17:02, Stephen Carrier wrote:
> > Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> > fail unless some user logs into Windows first. In this case, that is by
> > RDP, and it doesn't need to be the same user as the one
On Mar 5 17:02, Stephen Carrier wrote:
> Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> fail unless some user logs into Windows first. In this case, that is by
> RDP, and it doesn't need to be the same user as the one logging in by ssh.
> After logging out of the
Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
fail unless some user logs into Windows first. In this case, that is by
RDP, and it doesn't need to be the same user as the one logging in by ssh.
After logging out of the windows-native session, ssh continues to work.
Has anyone been able to get CYGWIN sssd service to interact with the windows
desktop?
If yes, could you please reply with the configuration you used to get it to
work.
Thanks,
Mitch Hall
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
Problem reports:
Hello!
Two days ago I posted a problem report regarding not being able to get the
SSHD daemon properly started on this normal installation. I even provided a
collection of almost meaningful information regarding my problem. I then
prepared to wait until resubmitting that problem report, with more
On Nov 15 15:25, Ken Brown wrote:
On 11/15/2010 11:53 AM, Corinna Vinschen wrote:
On Nov 15 11:40, Christopher Faylor wrote:
On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
On Nov 13 10:00, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken
On 11/16/2010 8:58 AM, Corinna Vinschen wrote:
On Nov 15 15:25, Ken Brown wrote:
On 11/15/2010 11:53 AM, Corinna Vinschen wrote:
On Nov 15 11:40, Christopher Faylor wrote:
On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
On Nov 13
On Nov 16 09:33, Ken Brown wrote:
On 11/16/2010 8:58 AM, Corinna Vinschen wrote:
Is there a chance that your service entires still point to a cygrunsrv
under C:\cygwin instead of D:\cygwin-1.7?
No. The installation in C:\cygwin is newer than the one in D:\cygwin-1.7;
it's just a small
On Nov 17 20:11, Christopher Faylor wrote:
On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm. Except, maybe, since you seem to be set up to build Cygwin from
CVS, could you start building the 09-12 version from CVS and then just
On Nov 18 12:07, Corinna Vinschen wrote:
On Nov 17 20:11, Christopher Faylor wrote:
On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm. Except, maybe, since you seem to be set up to build Cygwin from
CVS, could you start
On Nov 18 17:22, Corinna Vinschen wrote:
On Nov 18 12:07, Corinna Vinschen wrote:
On Nov 17 20:11, Christopher Faylor wrote:
On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm. Except, maybe, since you seem to be set up to
On 11/18/2010 1:56 PM, Corinna Vinschen wrote:
On Nov 18 17:22, Corinna Vinschen wrote:
On Nov 18 12:07, Corinna Vinschen wrote:
On Nov 17 20:11, Christopher Faylor wrote:
On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm.
Were you able to reproduce this on Windows 7? When will this fix be
released in the regular distro?
Thanks,
- Jeff
On 12:59 PM, Corinna Vinschen wrote:
On Nov 18 17:22, Corinna Vinschen wrote:
On Nov 18 12:07, Corinna Vinschen wrote:
On Nov 17 20:11, Christopher Faylor wrote:
On Wed,
On Thu, Nov 18, 2010 at 05:08:16PM -0700, jeff.odeg...@gmail.com wrote:
Were you able to reproduce this on Windows 7? When will this fix be
released in the regular distro?
If you are seeing a problem with Cygwin 1.7.7 then, as I mentioned earlier,
this is not the same problem.
To answer your
On 11/16/2010 9:59 AM, Corinna Vinschen wrote:
The failing chmod(/dev/tty1, 0622) is actually trying to change the
permissions on internal objects, like events, mutexes, and pipes, which
together constitute a tty/pty.
Here are some more data points:
1. I have access to four computers with
On Nov 17 09:56, Ken Brown wrote:
On 11/16/2010 9:59 AM, Corinna Vinschen wrote:
The failing chmod(/dev/tty1, 0622) is actually trying to change the
permissions on internal objects, like events, mutexes, and pipes, which
together constitute a tty/pty.
Here are some more data points:
1. I
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm. Except, maybe, since you seem to be set up to build Cygwin from
CVS, could you start building the 09-12 version from CVS and then just
add one change from CVS at a time using
cvs up -D '-mm-dd HH:MM'
as filter until you encounter the
On Wed, Nov 17, 2010 at 05:03:03PM -0500, Ken Brown wrote:
On 11/17/2010 10:47 AM, Corinna Vinschen wrote:
Hmm. Except, maybe, since you seem to be set up to build Cygwin from
CVS, could you start building the 09-12 version from CVS and then just
add one change from CVS at a time using
On 11/16/2010 9:59 AM, Corinna Vinschen wrote:
These changes only affect files, not ttys.
The failing chmod(/dev/tty1, 0622) is actually trying to change the
permissions on internal objects, like events, mutexes, and pipes, which
together constitute a tty/pty.
I'm grasping at straws now, but
On Nov 13 10:00, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The connection is closed right after I
type my password. The problem first appears in the snapshot of
20100917. To
On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
On Nov 13 10:00, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The connection is closed right after I
type my password. The problem
On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
On Nov 13 10:00, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The
On Nov 15 11:40, Christopher Faylor wrote:
On Mon, Nov 15, 2010 at 11:18:57AM -0500, Ken Brown wrote:
On 11/15/2010 11:09 AM, Corinna Vinschen wrote:
On Nov 13 10:00, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable
Bump. I just posted the same problem on Friday night on Windows 7.
On 12:59 PM, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The connection is closed right after I
type my password.
On Sun, Nov 14, 2010 at 08:45:01PM -0700, Jeff Odegard wrote:
On 12:59 PM, Ken Brown wrote:
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The connection is closed right after I
type my password. The
On 11/5/2010 8:03 AM, Ken Brown wrote:
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The connection is closed right after I
type my password. The problem first appears in the snapshot of
20100917. To reproduce:
1. Start sshd.
2. While
If I start sshd on a machine running a recent snapshot, I'm unable to
login to that machine via ssh. The connection is closed right after I
type my password. The problem first appears in the snapshot of
20100917. To reproduce:
1. Start sshd.
2. While logged in as one user, try to login as
I installed cygwin for the second time. I installed all the packages
from ftp%3a%2f%2fmirror.cs.vt.edu%2fpub%2fcygwin%2fcygwin%2f mirror.
My session then ran as follows (after I configured the mkpasswrd thing
for my domain account):
gsfo...@gsfogus ~
$ ssh-host-config -y
*** Query:
On Fri, Jun 26, 2009 at 09:28:50AM -0700, Gordon Fogus wrote:
I installed cygwin for the second time. I installed all the packages
from ftp%3a%2f%2fmirror.cs.vt.edu%2fpub%2fcygwin%2fcygwin%2f mirror.
My session then ran as follows (after I configured the mkpasswrd thing
for my domain account):
Gordon Fogus wrote:
gsfo...@gsfogus ~
$ net start sshd
System error 2 has occurred.
The system cannot find the file specified.
Are there any clues in /var/log/sshd.log?
HTH,
David
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
/var/log/sshd.log does not exist.
---
gsfo...@gsfogus /var/log
$ ls -a
. apache exim messages setup.log.full wtmp
.. apache2 lastlog setup.log squid
---
On Fri, Jun 26, 2009 at 9:47 AM, David
Christensendpchr...@holgerdanske.com wrote:
Gordon Fogus wrote:
gsfo...@gsfogus ~
$
On Fri, Jun 26, 2009 at 10:17:57AM -0700, Gordon Fogus wrote:
/var/log/sshd.log does not exist.
How about the event log?
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe
On Fri, Jun 26, 2009 at 01:21:41PM -0400, Christopher Faylor wrote:
On Fri, Jun 26, 2009 at 10:17:57AM -0700, Gordon Fogus wrote:
/var/log/sshd.log does not exist.
How about the event log?
And, also:
VVV
--
Problem reports:
On Sun, Dec 16, 2007 at 10:31:06PM -0500, Christopher Faylor wrote:
On Sun, Dec 16, 2007 at 06:30:14PM -0800, David Christensen wrote:
I moved my C:\cygwin directory aside today and did a fresh install of
Cygwin on Windows XP Professional SP2. I also found that sshd would not
start. There was a
I know there have been postings regarding the issues with sshd on
Windows 2003 64-bit servers, but I cannot locate a definitive
explanation about this issue.
I have been running cygwin sshd on the server, using the default
sshd_config scripts and running the service as the sshd_server user
Len Jacobs wrote:
... sshd ...
The services have been working, but now they are not ...
/var/empty directory ...
I moved my C:\cygwin directory aside today and did a fresh install of
Cygwin on Windows XP Professional SP2. I also found that sshd would not
start. There was a clue regarding
On Sun, Dec 16, 2007 at 06:30:14PM -0800, David Christensen wrote:
I moved my C:\cygwin directory aside today and did a fresh install of
Cygwin on Windows XP Professional SP2. I also found that sshd would not
start. There was a clue regarding ownership of the above directory in
hello:
I hv a problem while running sshd service on windows vista. When i
start the sshd service it start successfully, but after few seconds, i
stop automatically. It may be due to the security of vista or b.c. of
some other reason. I need ur help me in sovling it.
thanks.
/Aamir
--
to the Cygwin version and I've not
seen it on other
systems.
Well, the problem is this. I just tried it and I can't reproduce it.
Each session gets another display number, starting at 10, as expected.
Maybe this is somehow due to a sshd_config setting which uncovers a
sshd problem? I don't see
From: Corinna Vinschen corinna-cygwin at cygwin dot com
To: cygwin at cygwin dot com
Date: Tue, 28 Mar 2006 09:37:28 +0200
On Mar 27 18:55, David Picton wrote:
I have encountered a problem with the sshd server when the client
specifies X11 passthru i.e. ssh -Y or ssh -X.
The allocation of
display number, starting at 10, as expected.
Maybe this is somehow due to a sshd_config setting which uncovers a
sshd problem? I don't see how this should be related to Cygwin. I still
think this should be a question for a ssh mailing list.
Corinna
--
Corinna Vinschen Please, send
.
Well, the problem is this. I just tried it and I can't reproduce it.
Each session gets another display number, starting at 10, as expected.
Maybe this is somehow due to a sshd_config setting which uncovers a
sshd problem? I don't see how this should be related to Cygwin. I still
think
I have encountered a problem with the sshd server when the client
specifies X11 passthru i.e. ssh -Y or ssh -X.
The allocation of virtual displays doesn't work correctly if two or
more X11-enabled sessions run at the same time.
As I understand it, the server should give each session a unique
On Mar 27 18:55, David Picton wrote:
I have encountered a problem with the sshd server when the client
specifies X11 passthru i.e. ssh -Y or ssh -X.
The allocation of virtual displays doesn't work correctly if two or
more X11-enabled sessions run at the same time.
As I understand it, the
On Mar 22 15:35, Glenn wrote:
I have a problem with sshd where it;
(1) won't allow users to login, users recieve the message Read from
socket failed: Connection reset by peer
(2) sshd terminates prematurely.
The problem I believe (though I'm not really sure) relates to the second
I have a problem with sshd where it;
(1) won't allow users to login, users recieve the message Read from
socket failed: Connection reset by peer
(2) sshd terminates prematurely.
The problem I believe (though I'm not really sure) relates to the second
final line of output from the sshd
I'm seeing an odd behavior with the latest openssh package.
When I scp -r files from a cygwin host running sshd, the directory will copy
over, but none of the files within.
The cygwin ssh client doesn't seem to have that problem that I've seen.
Here's the illustration with some verbosity:
1)
On Feb 10 02:24, Peter Wohlers wrote:
I'm seeing an odd behavior with the latest openssh package.
When I scp -r files from a cygwin host running sshd, the directory will copy
over, but none of the files within.
The cygwin ssh client doesn't seem to have that problem that I've seen.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jacek Trzcinski on 11/15/2005 12:29 AM:
Thanks . It turned out that I had cygwin1.dll in AVR gcc compiler and it
caused errors.
Just as we had predicted.
It is a little bit strange because LoadLibrary function (
I assume Cygwin
Hi everybody !
After a lot of time I decided to upgrade my very old version of Cygwin
to latest release.
Unfortunately there is something wrong when I try to execute sshd sever
by for example net start sshd. Any trial ends with message:
Entry point of procedure _impure_ptr not found in library
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jacek Trzcinski on 11/14/2005 5:02 AM:
Hi everybody !
After a lot of time I decided to upgrade my very old version of Cygwin
to latest release.
Unfortunately there is something wrong when I try to execute sshd sever
by for example
Użytkownik Eric Blake napisał:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jacek Trzcinski on 11/14/2005 5:02 AM:
Hi everybody !
After a lot of time I decided to upgrade my very old version of Cygwin
to latest release.
Unfortunately there is something wrong when I try to
On Mon, Nov 14, 2005 at 03:28:56PM +0100, Jacek Trzcinski wrote:
U??ytkownik Eric Blake napisa??:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jacek Trzcinski on 11/14/2005 5:02 AM:
Hi everybody !
After a lot of time I decided to upgrade my very old version of Cygwin
to latest
Thanks for response but:
1) Rebooting did not resolve the problem
2) Cygwin1.dll is from July 2005 so I guess it is new. As a matter of
fact I removed all cygwin files from
Cygwin directory and installed latest version of Cygwin to other
partition on my disk. Situation did not changed.
Użytkownik Christopher Faylor napisał:
On Mon, Nov 14, 2005 at 03:28:56PM +0100, Jacek Trzcinski wrote:
U??ytkownik Eric Blake napisa??:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jacek Trzcinski on 11/14/2005 5:02 AM:
Hi everybody !
After a lot of time I
When I try to log into my Windows Server 2003 SP1 machine over ssh, I get the
following error and my connection is closed after typing my password:
$ ssh [EMAIL PROTECTED]
[EMAIL PROTECTED]'s password:
Last login: Wed May 4 14:04:26 2005 from mymachine
setgid: Invalid argument
Connection to
iirc your cygwin passwords are out of sync with windows.
The details of this are covered in the readme I believe its been
a long while since I set it up.
Steve
- Original Message -
From: Douglas De Couto
When I try to log into my Windows Server 2003 SP1 machine over ssh, I get the
Hi Igor
I completely removed my cygwin installation and reinstalled. That fixed
the problem. I don't know how things managed to get so broken; I think
it was to do with running ssh-host-config as a second user perhaps, but
I'm not sure of that.
So, problem solved, although not elegantly.
On Mon, 17 Nov 2003, John Pye wrote:
Thanks for the extra tips, Igor. Do any of these results look strange to
you?
Igor Pechtchanski wrote:
That's the default mode Windows gives it. This should work, but somehow
doesn't... Can sshd get to all the necessary files and directories? Look
Hi everyone
I'm still having problems with my SSH configuration. I have followed all
the steps give by Corinna earlier, plus some more, but it hasn't changed
anything. Does anyone have any more tips or suggestions?
Perhaps other files which could secretly be snarling up my SSH config,
other
On Thu, 13 Nov 2003, John Pye wrote:
Hi everyone
I'm still having problems with my SSH configuration. I have followed all
the steps give by Corinna earlier, plus some more, but it hasn't changed
anything. Does anyone have any more tips or suggestions?
Perhaps other files which could
Well... This is looking weird now :-)
In response to your suggestions, Igor...
Access is denied.
At a guess, your sshd doesn't have permissions to execute bash.
$ net helpmsg 5
[EMAIL PROTECTED] ~
$ net helpmsg 5
Access is denied.
[EMAIL PROTECTED] ~
Please post the output of ls -ln
On Fri, 14 Nov 2003, John Pye wrote:
Well... This is looking weird now :-)
In response to your suggestions, Igor...
Access is denied.
At a guess, your sshd doesn't have permissions to execute bash.
$ net helpmsg 5
[EMAIL PROTECTED] ~
$ net helpmsg 5
Access is denied.
[EMAIL
Hi everyone
I have a strange problem with sshd and can't seem to find any tips in
the mailing list archives, ssh docs, or on the web.
I have been getting the following error, ssh_exchange_identification:
Connection closed by remote host - see (1) below
When I run a verbose ssh, I get the
On Mon, Nov 10, 2003 at 07:38:46PM +1100, John Pye wrote:
Hi everyone
I have a strange problem with sshd and can't seem to find any tips in
the mailing list archives, ssh docs, or on the web.
I have been getting the following error, ssh_exchange_identification:
Connection closed by
Just a quick note to say I managed to fix my sshd
problem. The original message is below. The problem
was actually an NTFS file permission issue. The
volume had 'authenticated users' as a file permission.
When I added 'everyone' with 'read/execute' access to
the cygwin directory sshd was able
85 matches
Mail list logo
