[wix-users] Firewall Inbound rule using Wix element

Tue Nov 24 05:26:55 PST 2015

Ok I'll look at that too in my solving process... Thanks...

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

I don't know if this is related, but I had a situation where registering my
app with the firewall did not allow anonymous in-bound traffic until I
realized that since the app was hosted in another app I had to register the
host app which was actually listening for the traffic, to get it working.   

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

Thanks for the advice and help, the firewall exception Is working for my
Windows NT Service, but not for my Https server,  but this doesn't seem like
a wix issue, it's more of a config thing.

If I open up my Https port at large in the Firewall everything works great,
if I specify my process in the firewall exceptions with the specific  port I
should be listening on then the inbound traffic is blocked.

Thanks Again,
Marc

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

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/

____________________________________________________________________
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/