"Niels M�ller" wrote:

> Brian Beuning <[EMAIL PROTECTED]> writes:
>
> > Do you folks have a position about supporting
> > the lsh server on win/nt?
>
> Well, I usually don't touch w*ndows except when paid a lot of money
> for it... But if anybody else manages to port lsh (server and/or
> client) to windows, I'd be happy to include that code in the dist.
>
> > After an hour or so trying to port it, the main
> > problem areas so far include users, groups, and ptys.
>
> I would suspect that a windows port of the server would more or less
> replace io.c, server_session.c and server_password.c. I hope the rest
> of the code should work more or less without changes.
>
> Is that consistent with your experiences?

I haven't figured out which files are required for the server.
But when I try to compile everything, 73 files compile with
no errors.  Something like 30 files do not compile.  I consider
this pretty good.  I can send a copy of the errors to anyone
who wants to see them.  (It is probably too big to send to the
e-mail list.)

>
>
> For a nice windows version of the the client, a w*ndows GUI and a
> terminal emulator is needed as well. If you know of any good free
> terminal emulator that could be reused in lsh, I'd like to know.

I second the vote for tera term pro.  I use it all the time.  It already
has one SSH add-on for ssh1.

>
> I would suspect more interest for a windows client than a server, but
> perhaps that's wrong.
>

We are building a "cluster" type system that will run on both Win/NT
and Linux.  We want an ssh deamon to run on each box to remotely
start programs.  When you have 100 boxes, you really don't want to
login on all of them.

>
> Which development environment are you using on w*ndows? cygwin,
> M$VC++, or something else?

We use MSVC to develope C++ code.  We also use cygwin to access
our favorite UNIX tools under Windows.

>
>
> Which literature are you using? I have (for other reasons) ordered
> "Win32 systems programming" from Addison-Wesley, but I don't have it
> yet.

Actually I have been using Windows for about 4 years.  Before that I used
UNIX for 15 years at Bell Labs.  I haven't a clue how security is done
under
Windows.  Where are the logins and passwords kept?  In the registry?
Is it enough to be Administrator (aka root) to "su" to someone else?

The online documentation that comes with "MSDN Library" is very
extensive.

>
> /Niels

Reply via email to