[wix-users] Firewall Inbound rule using Wix element

[Phill Hogland]

So in a similar situation I am doing:
<fire:FirewallException Id=" FirewallException_Test" Name="Company Test123 " Protocol="tcp" Scope="any" IgnoreFailure="yes" Profile="all" />

By specifying the app and not the port the OS lets that app listen for anonymous in-bound traffic, and the app listens on the port of its choice.  That is the behavior of the Windows Firewall (WF) in which you could register a port OR an application (but the two were not related to each other).  The Advanced Windows Firewall (AWF) also supports the WF behavior and also allows you to specify a range of ports when registering an application exception (which is not yet implemented in the WixFirewalExtension).


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Marc Beaudry
Sent: Friday, November 20, 2015 2:54 PM
To: 'WiX Toolset Users Mailing List' <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Firewall Inbound rule using Wix element

Ok, not sure what is meant by helping update the existing CA for everyone to benefit, but once I figure this out, I can gladly share and help in any way for everyone to benefit from this.

Here is my initial test: I don't see anything that mention how to state if it an inbound or outbound rule:

I want to open port 23 for a telnet server I have written, but the documentation states if I specify a program or a file then I cannot specify a port.
      
<fire:FirewallException Id=" FirewallException_Test" Name="Test123 "
Port="23" Protocol="tcp" Scope="any" IgnoreFailure="yes" Profile="all" />

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Phill Hogland
Sent: November-20-2015 3:35 PM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Firewall Inbound rule using Wix element

I agree with Rob and my post last week was not intended to imply that the WixFirewallExtension does not work on Vista or later.  I register my apps on
Win8 and Win 10 allowing them to listen for in-bound traffic.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Rob Mensching
Sent: Friday, November 20, 2015 2:31 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Firewall Inbound rule using Wix element

Why not help update the existing custom action so everyone gets the benefit?
I mean we'd have nothing today if we didn't do that originally.

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Marc Beaudry
Sent: Friday, November 20, 2015 12:28 PM
To: wix-users at lists.wixtoolset.org
Subject: Re: [wix-users] Firewall Inbound rule using Wix element

Hello All,

 

Apologies for the post, I just found a post from Phil Hogland from last Tuesday (Nov 17), that  the firewall extension hasn't been updated with the latest firewall setting, therefore I will go the CA approach.

 

Thanks 

Marc

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/