Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
Can we use HTTP proxy to install Linux Security 64?
Last updated
Issue:
Linux Security 64 and Policy Manager Server are located on different networks, therefore HTTP proxy would be needed during installation. How to set HTTP proxy when installing Linux Security 64?
Resolution:
Linux Security 64 product has a single, global HTTP proxy setting, which is always used when the product makes HTTP requests to external services.
You can configure the global HTTP proxy setting using a command line option either when activating the product or with the lsctl utility after you have activated the product.
If you use the command line option to define the product settings, the product saves the configuration as a local setting override. This means that once you have finished activating the product, you can view the settings with the following command: lsctl get http_proxy.
Local overrides take precedence over the configuration that is retrieved from remote management services (WithSecure Elements Endpoint Protection or Policy Manager). To configure the proxy settings remotely, you have to mark the setting as locked in the management service. When the setting is locked, the value set in the profile or policy that is distributed from the management service is always used, even if a local configuration exists.
You can also change the proxy settings in the Policy Manager Console. The global HTTP proxy setting does not affect communication with Policy Manager.
When you use Policy Manager to manage the product, updates are downloaded from Policy Manager Server. The global HTTP proxy setting does not affect this communication either.
You can define one or more Policy Manager Proxies in Policy Manager Console. If you have defined a Policy Manager Proxy, this is used to handle the communication with Policy Manager. If you configure multiple Policy Manager Proxies, the product automatically switches to using the next available proxy if the connection with one proxy fails.
As the product must retrieve the Policy Manager Proxy configuration from Policy Manager Server, it must be able to make an initial connection to the main Policy Manager Server to get the proxy configuration.
If the product cannot connect to Policy Manager Server when trying to download updates, it falls back to using the WithSecure update servers directly. This communication does not use a HTTP proxy.
- 1. Set the HTTP proxy:
- To set the proxy when you run the activation or installer command, include the –http-proxy option in the command:
–http-proxy=<host address>:<host port number>
-
Note: The product supports basic authentication for HTTP proxies. If the specified proxy requires authentication, use the –http-proxy=username:password@host:port format to specify the credentials for the proxy.
- To set the proxy after activation, run the following lsctl commands:
/opt/f-secure/linuxsecurity/bin/lsctl set http_proxy host <host address>
/opt/f-secure/linuxsecurity/bin/lsctl set http_proxy port <host port number>
/opt/f-secure/linuxsecurity/bin/lsctl set http_proxy enabled true - Run the following command to check the proxy setting: /opt/f-secure/linuxsecurity/bin/lsctl get http_proxy
This returns the current settings:
{
"enabled": true,
"host": <host address>,
"port": <host port number>
}