Using a proxy with Corelight-update

If the Corelight-update host requires use of a network proxy to access and download content, you can configure the Corelight-update host service or user session to provide the proxy location using the HTTPS_PROXY or https_proxy environment variables.

Update the service definition

When running Corelight-update as a service, it will automatically use the HTTPS_PROXY or https_proxy environment variables when set. Corelight-update will not use any HTTP proxy variables. The proxy location can be added to the service definition.

Update the service definition using override.conf.

  1. Use systemctl to create an override.conf.

 $ sudo systemctl edit corelight-update.service
  1. Create a [Service] section in the override.conf, and set the HTTPS_PROXY environment variable. For example:

[Service]
Environment="HTTPS_PROXY=https://proxy.example.com:443"
  1. Save the changes. You can review the override.conf in the path /etc/systemd/system/corelight-update.service.d

  2. Reload systemd.

$ sudo systemctl daemon-reload
  1. Restart the Corelight-update service.

$ sudo systemctl restart corelight-update

Update the user environment

The options to set a proxy can vary based on the OS distribution being used. Corelight-update will automatically use the HTTPS_PROXY or https_proxy environment variables when set. Corelight-update will not use any HTTP proxy variables.

In general, you can set the proxy environment variables at the host and user level.

  • In Red Hat, update /etc/profile to set the proxy at the host level for users.

  • In Ubuntu, update /etc/environment to set the proxy at the host level for users.

  • For user accounts, update the user’s shell profile to set the proxy.

For example:

$ sudo vi /etc/profile

export https_proxy="https://proxy.example.com:443"
export HTTPS_PROXY="https://proxy.example.com:443"