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.
Distribution: Ubuntu, Debian, Devuan, Raspbian, Armbian, Parrot OS
Posts: 11
Rep:
I'm not really familiar with gtk-gnutella, but with the above rules, your client will be able to receive connections, but not able to initiate connections of its own.
Also, please remember that iptables rules by default are for your *system*, not a particular piece of software you run.
A neat trick to apply rules to a particular piece of software only (though this can be done in more than one way), is to run that software under a particular user, and use iptables owner module:
iptables -A OUPUT -m owner --uid-owner <numeric id of the process owner> -j ACCEPT
A good way to debug is changing the rule that drops traffic to a log and drop. The below is from my firewall:
And then just change the target of your rule(s) that drop traffic to -j LnD instead of -j DROP. That way, you can observe what gets dropped in your logfiles.
You can do something similar for accepted connections, though it has to be used cautiously on a system that has many accepted connections.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.