Am 09.12.2014 um 19:33 schrieb Chuck Anderson:
On Tue, Dec 09, 2014 at 11:16:54AM -0700, Pete Travis wrote:But seriously, there's an implication in this thread that there will be work happening to give stuff a path to ask for an open port. Where can we follow along with that effort? Starting with, say, how I might change `nikola runserver` or `django-admin runserver` to ask for the port, and ending with the resulting UI that asks me for approval?The functionality for a program to ask for an open port already exists. It is called bind(2)
yes, but the problem is that you won't forbid a program to listen on a port even if it is designed to listen on 0.0.0.0 instead 127.0.0.1 *but* you want and need to restrict from where it is accessable
if you disallow the bind-call it failswhenever i play around with a network-aware software the first step is test it#s behavior on localhost and later decide if i want to have it reachable over the netwok and over wich network
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
