* Michael Hipp (Mon, 30 Jul 2007 14:38:02 -0500)
Thorsten Kampe wrote:
* Michael Hipp (Mon, 30 Jul 2007 08:36:48 -0500)
Daniel Griscom wrote:
At 7:32 PM -0500 7/29/07, René Berber wrote:
Back to the original problem: did you use ssh-user-config? (I guess
What you reported about the
At 7:32 PM -0500 7/29/07, René Berber wrote:
Back to the original problem: did you use ssh-user-config? (I guess you did
since you had to copy the public key).
No; I'd thought that ssh-user-config was to
configure an account that was to be an ssh client
(e.g. one within which I'd use ssh to
Daniel Griscom wrote:
At 7:32 PM -0500 7/29/07, René Berber wrote:
Back to the original problem: did you use ssh-user-config? (I guess
you did
since you had to copy the public key).
No; I'd thought that ssh-user-config was to configure an account that
was to be an ssh client (e.g. one
At 8:36 AM -0500 7/30/07, Michael Hipp wrote:
Daniel Griscom wrote:
At 7:32 PM -0500 7/29/07, René Berber wrote:
Back to the original problem: did you use ssh-user-config? (I guess you did
since you had to copy the public key).
No; I'd thought that ssh-user-config was to
configure an
* Michael Hipp (Mon, 30 Jul 2007 08:36:48 -0500)
Daniel Griscom wrote:
At 7:32 PM -0500 7/29/07, René Berber wrote:
Back to the original problem: did you use ssh-user-config? (I guess
What you reported about the log is simple, the password used is not
correct...
it should prompt you
Daniel Griscom wrote:
If so, then the first line above needs to be uncommented and changed
to 'no'. (Remember to keep a session open while you're testing
changes, and any changes won't become live until sshd is restarted
on the host.)
I think you said you were using authorized_keys2 as the
I finally figured it out. When I set up Windows, I was asked for an
administrative password, and gave one. Then I was asked for a default
username. I didn't know that by default Windows creates users with no
password, and that I had to explicitly set the password for each
user. So, that user
Thorsten Kampe wrote:
* Michael Hipp (Mon, 30 Jul 2007 08:36:48 -0500)
Daniel Griscom wrote:
At 7:32 PM -0500 7/29/07, René Berber wrote:
Back to the original problem: did you use ssh-user-config? (I guess
What you reported about the log is simple, the password used is not
correct...
it
I have openssh version 4.6p1-1 installed under WinXP SP2 with all
updates. I've successfully used ssh-host-config to set up sshd
(privilege separation on, local user sshd created, sshd run as
service, CYGWIN=ntsec tty; sshd started with net start sshd; all
done under the administrative account
Daniel Griscom wrote:
I have openssh version 4.6p1-1 installed under WinXP SP2 with all
updates. I've successfully used ssh-host-config to set up sshd
(privilege separation on, local user sshd created, sshd run as service,
CYGWIN=ntsec tty; sshd started with net start sshd; all done under
At 3:31 PM -0500 7/29/07, René Berber wrote:
Daniel Griscom wrote:
I have openssh version 4.6p1-1 installed under WinXP SP2 with all
updates. I've successfully used ssh-host-config to set up sshd
(privilege separation on, local user sshd created, sshd run as service,
CYGWIN=ntsec tty; sshd
Daniel Griscom wrote:
[snip]
Look at the log (Windows' event viewer), what's the error sent when
you try to
login?
Just what you'd expect: Failed password for development from
192.168.1.101 port 1121 ssh2.
Do you happen to have a domain user as well as a local user?
(BTW, the account is
At 6:19 PM -0500 7/29/07, René Berber wrote:
Daniel Griscom wrote:
[snip]
Look at the log (Windows' event viewer), what's the error sent when
you try to
login?
Just what you'd expect: Failed password for development from
192.168.1.101 port 1121 ssh2.
Do you happen to have a domain
Daniel Griscom wrote:
[snip]
Do you happen to have a domain user as well as a local user?
I don't know the difference. I'm not at the machine now, but it's a
vanilla Windows installation. All machines on my network are in
workgroup MSHOME. I created one account when installing windows,
14 matches
Mail list logo