1169032 - UT should not require new permissions (wrt firewalls)

Status: RESOLVED FIXED

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

Description

[Thomas Huelbert]

need to see if restrictive firewall settings require additional permissions 9when the user allowed FHR previously)

Comment 1

[Stuart Philp :sphilp]

To clarify here, what are "restrictive firewall settings"? Are there particular ports other than 80/443 used? 

Steps:
- Set up a firewall with "restrictive" settings (TBD)
- On an older install of Firefox (say 38.0b9), ensure FHR is enabled and functional.
- Update to 39b and ensure FHR is still enabled and functional

Sound about right?

Comment 2

[Thomas Huelbert]

On me to get info by eod friday

Comment 3

[Stuart Philp :sphilp]

Is this still relevant Thomas?

Comment 4

[Stuart Philp :sphilp]

Wrong thuelbert ;)

Comment 5

[Thomas Huelbert]

pinging Syd

Comment 6

[Stuart Philp :sphilp]

After talking it over, we're really only concerned about port 443 here as all pings use SSL, so I did a simple test to verifying that things work correctly when that port is open and then closed without any changes to perms/perfs/whatever by the user. The ping is sent either way by the client, but the request just doesn't go anywhere when 443 is blocked at a firewall.

This probably isn't worth doing for every release, and considering that 443 is basically required for much of the internet to function, I don't see a huge concern here. If we do end up adding other services that use non-standard ports or perhaps do something crazy like switch to UDP or RTC for real time streaming or whatever, then that will definitely require some more testing.