This is a discussion on Re: openssh on interix - openssh ; Martin Koeppe wrote: > Hi openssh developers, > > I'm trying to port openssh to Interix. See  for more on this. > > For Interix sshd needs to be patched to not use setuid()/setgid(), but > an Interix specific ...
Martin Koeppe wrote:
> Hi openssh developers,
> I'm trying to port openssh to Interix. See  for more on this.
> For Interix sshd needs to be patched to not use setuid()/setgid(), but
> an Interix specific function setuser(). See  why it is needed.
> Unfortunately, setuser() needs the clear-text password of the user to
> be fully functional (If you use password-less setuser(), then the
> user doesn't have network access rights, e.g. no access to a network
> home dir).
Sounds like what you are trying to do is run the sshd on a Windows
machine, and get the user's windows password so they can "login"
If the sshd could use the GSSAPI and delegated credentials, it might
be possible to pass the Kerberos ticket into the LSA. This could give
you single sign on.
I believe with a registry setting, the Kerberos for Windows can do
something like this. You might want to ask on the email@example.com list
might be another possibility.
> The problem is now: How to get the clear-text password from
> where it would be needed as argument for setuser()?
> See  for the patch I'm currently using. My first idea would be to
> use the struct passwd pw_passwd field that is passed to
> permanently_set_uid() for storing the clear-text password after
> successful (password-)authentication.
> Before looking into details I just want to ask:
> Would such use of struct passwd be a security issue?
> Many thanks in advance
>  http://www.debian-interix.net/
>  http://www.suacommunity.com/forum/tm...=setuserᮕ
>  http://www.debian-interix.net/debian...2.interdiff.gz
> openssh-unix-dev mailing list
Douglas E. Engert
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
openssh-unix-dev mailing list