PHP, Perl, Python connector for Shadow Daemon

[samrao79]

I am confused as to how install the connectors, the guide is not clear at all. Am I supposed to install PHP, Perl and Python?

[zit-hb]

Could you please clarify which part of https://shadowd.zecure.org/overview/php_connector/ is not clear? If you want to protect a PHP application you install the PHP connector, if you want to protect a Perl application you install the Perl connector, if you want to protect a Python application you install the Python connector.

[samrao79]

The whole document is not clear for me, I can't understand how to actually install the connectors, I am following the guide but don't understand what to do, I am not a linux expert and only dealt with it briefly.

Am I supposed to install PHP, Perl, Python on the server? and where do I get the auto_prepend_file from?

[zit-hb]

Ah, okay, I understand. Please answer the following questions, so that I can give a more detailed response:

• What application are you trying to protect?
• What web server are you using?
• Do you have SSH root access to your server?

Thanks!

[samrao79]

I am a System admin and this is my first time learning about Web Application Firewalls.

Right now I don't know but the guide talked about setting up PHP, Perl and Python Connectors. Are you talking about the server where the Shadow Daemo is installed I installed it on Ubuntu server and I have SSH access to the server

[zit-hb]

Shadow Daemon is used to protect web applications from certain types of hacking attempts. So if you are not hosting any web applications there is not too much that you can do with Shadow Daemon.

You can find an overview of the general structure here: https://shadowd.zecure.org/documentation/architecture/

First you install shadowd through shadowdctl. This does nothing but starting the analysis server and the administration interface. Nothing is protected yet from attacks.

Afterwards you install the connector for every web application that you want to protect. The web application can run on the same host as shadowd, but it can also be a different host. The latency should just not be too high. The connectors intercept requests to the web applications and send them to shadowd. shadowd analyses the request and tells the connector what to do with it (block it, modify it, let it pass).