apache configuration to connect to network adapter via a web application
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
apache configuration to connect to network adapter via a web application
Hi, all.
please help me with this problem.
I want to run snort through a web application with exec("snort -v -i eth0 ") php function.
for example when start button was pressed snort should be run,
but the execution failed with this error:
but when I run snort command via command line as root it will execute successfully.
I think this problem is for that apache user haven't access to network adapter, is my guess correct? I have no experience with apache, should I change apache configuration? what is the configuration for this problem.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
Apache was designed to run with very limited permissions, that is why it is so safe.
You don't want to increase the permissions from a point of security, let alone let it run as root.
If you really want to make your system insecure, you might try to set setuid on snort. (man setuid) But again, I warn you it is a bad idea.
There are other ways to accomplish this, but slightly more complicated. For example, build a script which runs in the background with root privileges, and checks for the contents of a certain flag file. This flag file contains '0' or '1'. When it is '1', the background script executes your snort. The output of snort goes into a temporary file. Your web page displays the contents of this file. You php script only writes '0' or '1' in the flag file. This is perfectly safe.
Most information which is shown to you thru a web page is based on a background process gathering information and storing it somewhere. When the information is retrieved over the web, this information is what you see.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.