[SOLVED] Restricting networking connections by executable file path?
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Restricting networking connections by executable file path?
Hello, I use iptables to restrict connections by IP, protocol, and port. However, it doesn't seem to support the creation of rules based on executable file paths. The Windows 7/8 and 10 come with a native firewall that lets the user to select a file path and to create rules for it. I've found various answers on Stackoverflow and similars, but all of them give a solution that only works with old versions of iptables. I really need to know how to use iptables or netfilter to accomplish this task, because I want to create a white list of allowed executables that can access remote servers.
If your distro has apparmor, then you can use it to a certain extent. It has limited capabilities to restrict networking but it does have something. The apparmor profiles are applied based on the application's path. The newer versions of apparmor have more capabilities. Apparently there's a long-standing ticket open in the bug tracker in regards to more fine-grained networking restrictions, but do check to see what your distro has.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.