Mattia Verga wrote: >The alternative could be a "open approach" from Firewalld, where an >application, when it's executed, can inform firewalld that needs to >open a port, firewalld asks the user if it should grant access to the >application and then opens the port... but this needs to be >implemented in the source of every application, it can eventually be >sponsored to become a standard in the linux world. There is already a way for an application to inform the operating system that it needs to open a port. It's called the Berkeley socket API, and every program that communicates across a network already uses it. Why don't you guys patch GlibC's implementations of bind and connect to notify FirewallD and get it automatically enabled in every program, instead of requiring every communicating program to call a second API in addition to the Berkeley socket API? Alternatively, cut out the packet filter and have GlibC ask the user whether the call to bind or connect shall be allowed to succeed (or automatically allow or deny the call if so configured). This has the advantage that the program is informed that it's not allowed to communicate. -- Björn Persson
Attachment:
signature.asc
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
