Remotely Accessing a pc in JAVA

[netto thengumpallil]

hi,

i urgently need a help about how to access one pc from network and control it through java

and

for remotely shutting down the pc

mail to me : netto.thengumpallil.sisl.co.in

[SJ Adnams]

install services for unix on the pc.

you can then open a telnet connection & issue a shutdown command.

[Jeroen Wenting]

"I want to write a trojan that can launch a DDOS attack against other computers over the network and cause them to reset. I want to write it in Java. If you don't help me NOW you're ***************".

[Ernest Friedman-Hill]

This isn't Java News. As we have no virus-writer's forum, I'll move to "Sockets and Internet Protocols."

[Theodore Casser]

Originally posted by Jeroen Wenting:
"I want to write a trojan that can launch a DDOS attack against other computers over the network and cause them to reset. I want to write it in Java. If you don't help me NOW you're ***************".

Thanks for the laugh.

Actually, if I had an easy way to do something like this in Java, I'd probably be interested in using it myself. Not for something malicious, but more for managing my home network while I'm at the office. (Right now, I SSH into the network and use virtual desktopping, but there's definitely an alure to having some kind of remote OS-agnostic admin console.)

Still, all things being equal, I think more OS-specific solutions probably fill this space nicely without having to write one in Java.

[Stan James]

I wrote a java client & server ... the client can send any command as a string and the server uses exec() to run the string. It pipes the stdin, stdout and errout over the socket, too, so a user at the client can interact with a program on the server. It was a fun exercise, but too fragile (buggy) and insecure to actually use.

[peter wooster]

Originally posted by Stan James:
I wrote a java client & server ... the client can send any command as a string and the server uses exec() to run the string. It pipes the stdin, stdout and errout over the socket, too, so a user at the client can interact with a program on the server. It was a fun exercise, but too fragile (buggy) and insecure to actually use.

Fragile and insecure? Why am I surprised, we tried out Tivoli Remote Control where I work and rejected it for similar reasons.