Question

I want “A” computer to responsible for execute the command, and “B” computer will send the command to “A” computer. I have some ideas on the implementation.

Way1:
The “A” computer have a while true loop to listen for “B” computer’s command, when it is received, it execute.

Way2:
Using a FTP Server, that store information that about the command.
The “A” computer have a while true loop to check whether the “B” computer uploaded any new information about the command. if yes, reconstruct the command and execute. After executed, the file on FTP Server will be deleted. And store a copy the “A” computer.

Way3:
this is similar to way2, but using database to store. After the command is executed, it will made as executed.

What is your suggestion about these 3 ways? Is that secure enough?

Answer 1

You’re assuming a trust relationship without giving any clues as to how you know that the payload from computer A is benign. How do you plan to prevent computer A from sending a task that says “reformat your hard drive after plundering it for all bank accounts and passwords?

1. AKA write a socket listener on computer B and let computer A connect to it. No security here.
2. FTP just saves you from having to write the transport protocol.
3. Database for persistence instead of file store – nothing new here.

None of your options have any security, so it’s hard to say which one is more secure. FTP requires that the user know the URL of your FTP server and, if you aren’t allowing anonymous access, a username and password. That makes 2 more secure than 1. 2 and 3 are equally (in)secure.

All can work, but all are risky. I see little or no security here.