On Aug 27 22:29, Greg Morgan wrote:
More on why I selected tty ntsec
http://tech.erdelynet.com/cygwin-sshd.html. It has always worked.
These are useless. Since ssh sessions are running in a pty, they are
in tty mode anyway, ntsec is on by default.
Corinna
--
Corinna Vinschen
Corinna Vinschen schrieb:
On Aug 27 22:29, Greg Morgan wrote:
More on why I selected tty ntsec
http://tech.erdelynet.com/cygwin-sshd.html. It has always worked.
These are useless. Since ssh sessions are running in a pty, they are
in tty mode anyway, ntsec is on by default.
just ntea should be
On Aug 28 15:13, Reini Urban wrote:
Corinna Vinschen schrieb:
On Aug 27 22:29, Greg Morgan wrote:
More on why I selected tty ntsec
http://tech.erdelynet.com/cygwin-sshd.html. It has always worked.
These are useless. Since ssh sessions are running in a pty, they are
in tty mode anyway,
Greg Morgan wrote:
OPTION 1.)
...
I looked at Cygwin /usr/bin/ssh-host-config configuration script and
found the command line that I would use:
...
OPTION 2.)
...
The use vim's search and replace functions to
change all the sshd -a -D occurrences to sshd -a -D -r like so
Option 3:
echo
Corinna Vinschen schrieb:
On Aug 28 15:13, Reini Urban wrote:
Corinna Vinschen schrieb:
On Aug 27 22:29, Greg Morgan wrote:
More on why I selected tty ntsec
http://tech.erdelynet.com/cygwin-sshd.html. It has always worked.
These are useless. Since ssh sessions are running in a pty, they are
in
On Sat, Aug 28, 2004 at 11:08:03AM +0200, Corinna Vinschen wrote:
On Aug 27 22:29, Greg Morgan wrote:
More on why I selected tty ntsec
http://tech.erdelynet.com/cygwin-sshd.html. It has always worked.
These are useless. Since ssh sessions are running in a pty, they are
in tty mode anyway,
On Sat, 28 Aug 2004, Brian Dessent wrote:
Greg Morgan wrote:
OPTION 1.)
...
I looked at Cygwin /usr/bin/ssh-host-config configuration script and
found the command line that I would use:
...
OPTION 2.)
...
The use vim's search and replace functions to
change all the sshd -a -D
for a
response and having both a work around and solution already. I'll try
it tomorrow at work.
Greg
If the subject title of OpenSSH-3.9p1-1, mysterious -r option, and
documented steps to resolve Connection to host closed. message was
sshd privilege separation problem did not provide you enough
On Aug 25 20:22, Greg Morgan wrote:
I did find one oddity to what you report. I use scp daily. The scp
function works correctly with privilege separation while I received the
connection to localhost closed message trying to ssh into the PC.
That's to be expected. The problem only occurs on
Corinna Vinschen wrote:
...
Again, as Larry already noted, the most informative thread is
http://cygwin.com/ml/cygwin/2004-08/msg00625.html
Note especially http://cygwin.com/ml/cygwin/2004-08/msg00702.html
...
I can't say that I tried googling for this first. Thank you for a
response and
Hi,
I've been running sshd and it recently stopped working. I'm not sure
whether I did anything to it, but I've managed to track down the problem.
If I use privilege separation (ssh-host-config), as soon as I type the
password in, the message Connection to localhost closed. is
displayed.
At 04:47 PM 8/25/2004, you wrote:
Hi,
I've been running sshd and it recently stopped working. I'm not sure whether I did
anything to it, but I've managed to track down the problem.
If I use privilege separation (ssh-host-config), as soon as I type the password in,
the message Connection to
Colin JN Breame wrote:
Hi,
I've been running sshd and it recently stopped working. I'm not sure
whether I did anything to it, but I've managed to track down the problem.
If I use privilege separation (ssh-host-config), as soon as I type the
password in, the message Connection to localhost
13 matches
Mail list logo
