|Bandie d0db0a7d94||9 months ago|
|img||3 years ago|
|systemd||10 months ago|
|1_generateCA.sh||3 years ago|
|2_generateServCert.sh||2 years ago|
|3_generateClientCert.sh||2 years ago|
|LICENSE||9 months ago|
|README.md||9 months ago|
|ding||10 months ago|
|ding.cfg||2 years ago|
|ding.win.cfg||2 years ago|
|dingd||10 months ago|
|dingd.cfg||2 years ago|
|dingd.win.cfg||2 years ago|
ding is a client-server thing written in python3. Its aim is to execute a set of commands remotely. The commands can be set in the server's config file.
The server will wait for a command to be sent by a client. If the command is present within the server's config file it will then execute the command, else nothing will happen.
The authentication is done via a SSL Client Certificate signed by an (self generated) Certificate Authority. The scripts for generating a CA and signing the Server/Client Certificates are also included to make it (relatively) easy. [ This involves typing in a few certificate details and entering a previously defined CA password. ]
At every step please read carefully what the generate certificates scripts want from you. The information on the certificates doesn't need to be true and can be totally random. They only need to be different from one another.
Step 1 to 3 can only be run on UNIX or GNU/Linux.
./1_generateCA.shto generate a CA.
./2_generateServCert.shto generate a signed Server Certificate.
./3_generateClientCert.shto generate a signed Client Certificate.
CA.crtto the computer which should be able to send commands to the server.
ding.cfgto that computer.
ding.win.cfgto that computer.
python .\dingdon Windows. (You may want to put this in a tmux session. [Ctrl+B, D] ;) ).
python .\ding <command>on Windows.
It works much better to use (bash) scripts instead of executing the commands directly.
If you want to be sure that this power won't be abused by bad people using your computer, you may want to add a password (saved in cleartext). The password will be sent inside the TLS connection.
You might want to do something like
$ history -c after sending the password via the client or play around with bash's HISTCONTROL variable.
pwtimeout=10for 10 seconds.
If you have a password with special characters as in spaces and the like, you may want to use quotation marks around your password.
./ding "abc def" or
python .\ding "abc def" on Windows.