OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: MS vs. Unix Remote Access
From: Vandenbranden Geert (Geert.VandenbrandenCAPCO.COM)
Date: Tue May 30 2000 - 06:06:30 CDT

Eric

The NT resource kit contains a remote command service. It does exactly what
it says. It allows a workstation running the client (also in the NT
resource kit) to connect to the server and run a command shell on the target
server. The command ,rcmd <servername/address> is very comparable to the
rsh (I think) UNIX command, except that rsh spawns a new window in the GUI
(at least in HP Vue), while NT stays in the same cmd box.
Install this service in Control Panel | Network Settings | Services | Add
... . The client is just a small executable..
Works like charm, and is very fast. However, beware that executing a GUI
application using the rcmd shell will result in a pending shell, since only
cmd line output is returned to the client (obvious, but the interface is
that easy that you often forget you're working on a remote server...)

And please, don't us BackOrifice. You don't need another security hole in
your setup ...

Geert Vandenbranden

-----Original Message-----
From: Focus on Microsoft Mailing List [mailto:FOCUS-MSSECURITYFOCUS.COM]On
Behalf Of Eric Lecht
Sent: Tuesday, May 23, 2000 2:37 PM
To: FOCUS-MSSECURITYFOCUS.COM
Subject: MS vs. Unix Remote Access

I *know* i've seen this discussion come and go, but our Solaris guru is once
again pissing and moaning that there are no tools for NT that'll allow him
to securely establish a command-line shell to an NT server a' la telnet
across a private yet insecure frame network using something akin to a
virtual console such as *NIX systems offer, and then stop/start services
that have choked?

He says it can't be done. I realize this may have been addressed before on
this forum, but I *cannot* come up with anything to refute him. I'm not
trying to proponent of one OS over the other here...but when someone tells
me something can't be done, i'm always suspicious....esp. when the source is
less-than-accomodating when it comes to MS products, however right he may or
may not be...

Like many state governments, we run a point-to-point frame network; Lots of
state agencies are linked back across the network to our core, so the
connections *must* be secure, from workstation to server.

So...what do other sysadmins use who must, oh, say, securely connect to a
remote NT box across a private, yet in fact insecure, frame network to a
machine running a firewall, and stop/start services? Preference is
command-line shell.
Or is he right, and in fact can't be done? PCAnywhere is not an
option....=>8 P.

Eric Lecht
************************************************************************
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, you must not read, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
The Capital Markets Company.

http://www.capco.com
***********************************************************************