You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Andrew Chung (JIRA)" <ji...@apache.org> on 2016/03/23 00:25:25 UTC

[jira] [Assigned] (REEF-347) Configure .NET tests to only listen on 127.0.0.1

     [ https://issues.apache.org/jira/browse/REEF-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Chung reassigned REEF-347:
---------------------------------

    Assignee: Andrew Chung

> Configure .NET tests to only listen on 127.0.0.1
> ------------------------------------------------
>
>                 Key: REEF-347
>                 URL: https://issues.apache.org/jira/browse/REEF-347
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET Evaluator
>            Reporter: Markus Weimer
>            Assignee: Andrew Chung
>            Priority: Minor
>
> When running the REEF.NET tests, the Windows firewall kicks in several times asking for {{Evaluator.exe}} to have permission to open a port. These popups are part of the *application* firewall of Windows: Whenever an unknown app wants to open a port, Windows asks for the users permission.
> We don't see these for the JVM tests, as we probably all have given the {{java.exe}} that permission a long time ago, opening a gaping whole in our safety net from java-based malware :-)
> We can't do the same for the {{Evaluator.exe}}, as we create a new one on every build, and the Windows firewall is to distinguish them as new.
> According to [this thread on stackoverflow|http://stackoverflow.com/questions/26626258/disable-windows-firewall-popup-for-automated-tests], we can however get a much cleaner solution: As long as we configure all our processes to listen on {{127.0.0.1}} only, the firewall won't be active. 
> The recent addition of the {{PortProvider}} and {{LocalAddressProvider}} classes should make that feasible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)