On Aug 13 04:53, Brian Kasper wrote:
Corinna Vinschen wrote:
As it turns out, all my problems were caused by the fact that the
sshd_server user being created by the ssh-host-config script was not
being given all the required privileges.
This is weird. The ssh-host-config script usually makes sure that
the sshd_server user got all required privileges. See the script
at line 517ff.
I'm not at work right now, and unfortunately I can't access the gmane
news server from work, but I'll check out the script. I agree it's
weird; perhaps it's due to either the 64-bitness of the OS, or the fact
that the OS is (as far as I know) based on the server version of Windows
I just re-read your OP. There's a misunderstanding here. Windows XP is
NT kernel version 5.1. Windows 2003 Server (*not* XP 2003 Server) is
NT kernel version 5.2. Windows 2003 Server is a newer OS than XP, and
has a newer kernel, with different features and behaviour than the
Windows 2003 Server x64, as well as the client OS XP x64 are both based
on the 5.2 kernel. Thus, XP x64 is more similar to 2003 Server than to
it's 32 bit XP counterpart.
The user privilege handling of the 5.2 kernel differs in two points
from the handling in XP. None of these differences should account for
what you observed. Just FYI, I set up ssh servers on 2003 32 and 64
bit, as well as on XP 32 and 64 using ssh-host-config without any
problems. There muyst have been some satrange side-effect on your
If you're willing to experiment, I'd suggest to remove the sshd-service,
as well as the sshd and sshd_server user accounts entirely. Also remove
/etc/ssh* and /var/empty. Then start ssh-host-config again and see what
happens. Afterwards you can check with editrights again if everything's
correctly set up. If not, and if the script didn't bail out with
Assigning the appropriate privileges to user 'sshd_server' failed!
Can't create sshd service!
there's a bug in the script. Otherwise, if you got the above error
message, it might be interesting to learn why this happens. OTOH, if
the scipt runs fine this time, well, *shrug*.
If I get the chance, I'll delete the sshd_server user from that system
and re-run the ssh-host-config script to see what privileges it assigns
Oh, hmm, I wrote the above before reading further in your mail... :)