Bandie
/
ding
1
0
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity
Execute commands remotely in a secure way
7 Commits 1 Branch 6 Tags 1.1 MiB
Python 72.7%
Shell 27.3%
Go to file
Bandie Canis 03635184ae Now speaks IPv6, if config contains a ":" in host 2017-10-03 00:05:23 +02:00
img Added a screenshot 2017-10-02 13:31:14 +02:00
1_generateCA.sh There it is. 2017-09-30 14:51:23 +02:00
2_generateServCert.sh There it is. 2017-09-30 14:51:23 +02:00
3_generateClientCert.sh There it is. 2017-09-30 14:51:23 +02:00
LICENSE Initial commit 2017-09-30 14:39:31 +02:00
README.md Link to raw image 2017-10-02 13:47:12 +02:00
ding_client Now speaks IPv6, if config contains a ":" in host 2017-10-03 00:05:23 +02:00
ding_client.cfg There it is. 2017-09-30 14:51:23 +02:00
ding_server Now speaks IPv6, if config contains a ":" in host 2017-10-03 00:05:23 +02:00
ding_server.cfg There it is. 2017-09-30 14:51:23 +02:00

README.md

ding

What is ding?

ding is a client-server thing written in python. Its aim is to execute a set of commands remotely which can be set in the server's config file.

How does it work?

The server awaits commands sent by the client. A command must be defined in the server's config file, else the server won't do anything.

What about ding's security?

The authentication is done by an SSL Client Certificate signed by an (own generated) Certificate Authority. The scripts for generating a CA and signing a Server/Client Certificate are also in here to make it (relatively) easy. [ You need only to press enter in the most cases, type in some certificate information and entering a previously defined CA password. ]

Pic or didn't happen

Screenshot of CircleArt Can't read a thing?

Installation

In all steps please read carefully what the certification generate scripts want from you. The certificate information needn't to be true at all and can be random. They only need to be different from each other.

  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_client, ding_client.cfg, ding_client.crt, ding_client.key and CA.crt to the computer which should be able to send commands to the server.
  5. Do some configuration on the server and client (ding_server.cfg, ding_client.cfg).
  6. Start the server using ./ding_server. You may want to put this in a tmux session ([Ctrl+B, D] ;) ).
  7. Try out the client using ./ding_client <command>.