Do firewalls present a problem for BrowserKey?
No. BrowserKey requires that inbound TCP traffic be allowed on port 11,000 on the server running the BrowserKey Client Key Storage Application. Usually client-end firewall adjustments are not required, however if the client is behind a firewall that blocks outbound TCP traffic on port 11,000 this will need to be changed by the client-end firewall administrator. Future free upgrades to the BrowserKey system may include the ability to run the BrowserKey Client Key Storage Application on a port number selected by the website developer/owner (in theory future versions may be run on port 80 if so elected, eliminating client-end outbound firewall issues as port 80 is typically open for outbound TCP traffic (HTTP protocol traffic)).
