71e2654fa3
*before* a BSD-with-advertising license was added to their diffs, and other work done personally by me. sshd now works. Most permissions checks work properly. Privsep is off by default, and the sshd user is not created, on Interix until some problems with privsep are fixed (perhaps by abstracting the auth functionality out to openpam).
20 lines
995 B
Text
20 lines
995 B
Text
===========================================================================
|
|
$NetBSD: MESSAGE.Interix,v 1.1 2005/03/07 23:29:49 tv Exp $
|
|
|
|
OpenSSH on Interix has some important caveats:
|
|
|
|
* Hostname resolution uses the BIND resolver library rather than Windows
|
|
native lookup services. This requires that /etc/resolv.conf be set up
|
|
properly with a "nameserver" line; see resolv.conf(5). In most
|
|
installations, this was generated automatically when Services for UNIX
|
|
was installed (based on the name server in use at that time).
|
|
|
|
* Currently, UsePrivilegeSeparation does not work properly, so it defaults
|
|
to "no" on Interix.
|
|
|
|
* Network drives and encrypted local files may not be accessible after
|
|
logging in through sshd thanks to the way the Windows security API works.
|
|
A workaround is to "exec su USERNAME" after logging in, which will use
|
|
the password to create a proper Windows access credential key.
|
|
|
|
===========================================================================
|