Execute commands remotely in a secure way
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Bandie d0db0a7d94
Name, mail
1 month ago
img Optional password function added 2 years ago
systemd systemd example file 2 months ago
1_generateCA.sh There it is. 2 years ago
2_generateServCert.sh Renaming 2 years ago
3_generateClientCert.sh Renaming 2 years ago
LICENSE Name, mail 1 month ago
README.md Screenshot, a word about commands 1 month ago
ding ding client with -c <CONFIGFILE> option 2 months ago
ding.cfg Renaming 2 years ago
ding.win.cfg Renaming 2 years ago
dingd Using actual ConfigParser call; dingd has -c for config file 2 months ago
dingd.cfg Renaming 2 years ago
dingd.win.cfg Renaming 2 years ago



What is ding?

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.

How does it work?

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.

What about ding's security?

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. ]

Pic or didn't happen

Screenshot of ding


  • Install python3 on your target computers.


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. Run ./1_generateCA.sh to generate a CA.
  2. Run ./2_generateServCert.sh to generate a signed Server Certificate.
  3. Run ./3_generateClientCert.sh to generate a signed Client Certificate.
  4. Move ding, ding.cfg, ding.crt, ding.key and CA.crt to the computer which should be able to send commands to the server.
    • UNIX or GNU/Linux: Also move ding.cfg to that computer.
    • Windows: Also move ding.win.cfg to that computer.
  5. Do some configuration on the server and client (dingd.cfg, ding.cfg or dingd.win.cfg, ding.win.cfg on Windows).
  6. Start the server using ./dingd or python .\dingd on Windows. (You may want to put this in a tmux session. [Ctrl+B, D] ;) ).
  7. Try out the client using ./ding <command> òr python .\ding <command> on Windows.

A word about the commands

It works much better to use (bash) scripts instead of executing the commands directly.

Optional: Cleartext password with timeout

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.

Warning! Beware of the shell history!

You might want to do something like $ history -c after sending the password via the client or play around with bash's HISTCONTROL variable.

How to enable the password

  1. Open your dingd.cfg or dingd.win.cfg.
  2. Set pw_on=true.
  3. Set a password, like password=abc def.
  4. Set a password timeout: pwtimeout=10 for 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.