Re: [ros-dev] Using ROS cmd.exe with pipes (SqUe Squarious)

[Jonathan Rennison]

>  Hi I am trying to use the cmd.exe of reactos (on
> Windows!) with redirected 
> stdin/out/err. What I try to make is a remote shell application over 
> internet, and this is an important requirement for me, that it will work 
> with reacto's cmd.exe.
> I have build a test program that will redirect locally. open the process 
> (cmd.exe at least for now) and will forward output on a EditBox. The whole 
> process works quite well with the cmd.exe of M$ >Windows but its buggy with 
> the cmd.exe of reactos. More specifically when I start the redirection I 
> just get the current path and ">" usual prompt, but after that, the 
> communication gets unresponsive. >Whatever I send, there will be no return 
> messages.
> I attached the test project, and I would like to advice me if there is a 
> better approach that will work for ROS cmd.exe too. 
What you have proposed is basically telnet.
Extremely insecure.

You really should consider using SSH or similar.

Also it looks like you are using pipes to do the transferring from the code 
(but I could have misread it), and they only traverse local networks. You'd 
be better off with netcat or similar (if you're OK with low security).
You could just use a command line like:
netcat | cmd | netcat

JGR

_________________________________________________________________
MSN Music http://music.msn.no Finn din favorittmusikk blant nesten 1 million 
låter

[SqUe Squarious]

Ty for your reply :)

I know all this solutions and the security matters, but this is part of a
bigger project and the traffic is encapsulated in safe way.

I am not looking for a command line solution, I am looking for C++ solution
to embed it in my project. I need a way to read data from cmd.exe and sent
data to cmd.exe. So the Pipes seemed me a good way, but they don't wont work
with ROS cmd.exe which is also needed for my project, although they work
just fine with M$ cmd.exe :S

Finaly I should mention once more, that the attached VS project is a "TEST"
on the code that I try to use. As a standalone program it may be useless,
but If there is a way to read/write data directly on a command-line process,
it will be easily to transfer that data over net within "the bigger project"
:P.

Anyway I like you pointed me in your way, that I hadn't clarify what I
really needed, and hope I did it better now :)

On 6/20/07, Jonathan Rennison <jonathan_rennison(a)hotmail.com> wrote:
>  
> >  Hi I am trying to use the cmd.exe of reactos (on
> > Windows!) with 
>  redirected
> >  stdin/out/err. What I try to make is a remote
> > shell application over
> > internet, and this is an important requirement for me, that it will work
> > with reacto's cmd.exe.
> > I have build a test program that will redirect locally. open the process
> > (cmd.exe at least for now) and will forward output on a EditBox. The 
>  whole
> >  process works quite well with the cmd.exe of M$
> > >Windows but its buggy 
>  with
> >  the cmd.exe of reactos. More specifically when I
> > start the redirection I
> > just get the current path and ">" usual prompt, but after that, the
> > communication gets unresponsive. >Whatever I send, there will be no 
>  return
> >  messages.
> > I attached the test project, and I would like to advice me if there is a
> > better approach that will work for ROS cmd.exe too. 
>  What you have proposed is basically telnet.
>  Extremely insecure.
>
>  You really should consider using SSH or similar.
>
>  Also it looks like you are using pipes to do the transferring from the
>  code
>  (but I could have misread it), and they only traverse local networks.
>  You'd
>  be better off with netcat or similar (if you're OK with low security).
>  You could just use a command line like:
>  netcat | cmd | netcat
>
>  JGR
>
>  _________________________________________________________________
>  MSN Music http://music.msn.no Finn din favorittmusikk blant nesten 1
>  million
>  låter
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>