WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: rexec (remote execution)  (Read 2142 times)

Offline brian-au

  • Newbie
  • *
  • Posts: 19
rexec (remote execution)
« on: February 19, 2014, 04:40:14 AM »
rexec allows user on a local system (tinycore) to execute a command on a remote system (server)

In the case requested a tinycore client running as a "kiosk" will request an x-application running on a remote server to send an x-session and associated application over the network making the tinycore client a dumb-x-terminal not required to hold any application data.

I searched the apps/provides and noted that the nmap package has some reference to rexec but it looks cut-down?  Happy to be told otherwise...

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11044
Re: rexec (remote execution)
« Reply #1 on: February 19, 2014, 05:01:16 AM »
You usually use SSH for this, the old rexec is very insecure.
The only barriers that can stop you are the ones you create yourself.

Offline brian-au

  • Newbie
  • *
  • Posts: 19
Re: rexec (remote execution)
« Reply #2 on: February 19, 2014, 05:15:21 AM »
Yes we are aware of the old and insecure nature of rexec, but our server-side is SCO unix and sadly does not support any SSH.

The server runs some old software and drivers that are not ported to linux or other O/S of choice, probably never will be ported as the engineering cost is too high.

So we have a need for rexec (we think)

Also we will be running this on a fully private network (not over the web), and so security is of less concern

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11044
Re: rexec (remote execution)
« Reply #3 on: February 19, 2014, 05:21:18 AM »
Perhaps telnet?

You can of course build the old rexec yourself.
The only barriers that can stop you are the ones you create yourself.