The token parameter can be obtained from https://auth.contracts.canonical.com/.
The optional --no-auto-enable flag will disable the automatic enablement of recommended entitlements which usually happens immediately after a successful attach.
This shows whether this machine is attached to an Ubuntu Advantage support contract. When attached, the report includes the specific support contract details including contract name, expiry dates, and the status of each service on this system.
The attached status output has four columns:
SERVICE: name of the service
ENTITLED: whether the contract to which this machine is attached entitles use of this service. Possible values are: yes or no
STATUS: whether the service is enabled on this machine. Possible values are: enabled, disabled, n/a (if your contract entitles you to the service, but it isn't available for this machine) or — (if you aren't entitled to this service)
DESCRIPTION: a brief description of the service
The unattached status output instead has three columns. SERVICE and DESCRIPTION are the same as above, and there is the addition of:
AVAILABLE: whether this service would be available if this machine were attached. The possible values are yes or no.
The following configuration options are available:
The following options must be nested under the "ua_config" key:
If needed, authentication to the proxy server can be performed by setting username and password in the URL itself, as in:
http_proxy: http://<username>:<password>@<fqdn>:<port>
Additionally, some configuration options can be overridden in the environment by setting an environment variable prefaced by UA_<option_name>. Both uppercase and lowercase environment variables are allowed. The configuration options that support this are: data_dir, log_file, log_level, and security_url.
For example, the following overrides the log_level found in uaclient.conf:
UA_LOG_LEVEL=info ua attach
The artifacts include a configure script, a tarball with additional packages, and post install scripts. The artifacts will be installed in /usr/lib/common-criteria directory and the README and configuration guide are available in /usr/share/doc/ubuntu-commoncriteria directory.
See https://ubuntu.com/esm for more information.
After successfully enabling FIPS, the system MUST be rebooted. Failing to reboot will result in the system not running the updated FIPS kernel.
Disabling FIPS is not currently supported.
After successfully enabling FIPS with updates, the system MUST be rebooted. Failing to reboot will result in the system not running the updated FIPS kernel.
Disabling FIPS with updates is not currently supported.
See https://ubuntu.com/livepatch for more information.