cvdupdate 1.1.2

➕ Added a Docker Compose file to make it easier to host a private mirror.
The Docker Compose environment runs two containers:

1. CVD-Update.
2. An Apache webserver to host the private mirror.

Improvement courtesy of Mark Petersen.

• GitHub Pull-Request: #61

🐛 Fixed the CVD-Update Python package so it installs the setuptools
dependency. This fixes a runtime error on some systems.
Fix courtesy of Craig Andrews.

• GitHub Pull-Request: #59

🐛 Added missing documentation for cvd add command to the Readme.
Fix courtesy of Kim Oliver Drechsel.

• GitHub Pull-Request: #58

➕ Added retries in case the DNS TXT query fails.
Fix courtesy of backbord.

• GitHub Pull-Request: #50

cvdupdate 1.1.1

🐛 Fixed an issue where the .cdiff files were only downloaded when updating a
.cvd and not when downloading the .cvd for the first time.

🐛 Fixed an issue where cvd update crashes if the DNS query fails, rather
than printing a helpful error message and exiting.

🐛 Fixed support for CVD Update on Windows 🪟. In prior versions, the DNS query
was failing if a DNS server was not specified manually. Now it will try to use
OpenDNS servers if no DNS server is specified.

➕ Added Python dependencies to the Readme to help users that are unable to
install using pip.

cvdupdate 1.1.0

➕ CVD-Update can now get the DNS nameserver IP from an environment variable.

Specify the IP address of the nameserver in the environment variable
CVDUPDATE_NAMESERVER to ensure said nameserver is used when querying the
TXT record containing the current database definition version available.

Using this environment variable will take precedence over any option specified
in the config file.

Feature courtesy of Philippe Ballandras.

➕ CVD-Update can now accept multiple DNS nameservers from the nameserver
config option, or from the CVDUPDATE_NAMESERVER environment variable.

To set multiple DNS nameservers, specify the nameserver config option or the
CVDUPDATE_NAMESERVER environment variable as a comma separated list.

E.g.:

CVDUPDATE_NAMESERVER=1.1.1.1,8.8.8.8 cvd update

Feature courtesy of Michael Callahan.

🐛 In prior versions, CVD-Update would assume that a CVD file exists because it
is listed in the config.json "dbs" record. So if you delete that file by
accident and try to update, it would not notice and would instead claim that
it is up-to-date. In this release, CVD-Update will detect that a deleted file
is missing from the database directory and will re-download it.

Fix courtesy of Brent Clark.

🌌 CVD-Update will no longer remove extra files from the database directory
when you run cvd clean dbs. It will only remove those file managed by the
CVD-Update tool.

This means that you can now store third-party extra signature databases in the
CVD-Update database directory and CVD-Update will not delete them if you run
the clean command.

Improvement courtesy of Brent Clark.

🌌 CVD-Update now stores the database state information separately from the
configuration information. If you're upgrading from CVD-Update version 1.0.2,
your config.json file will be migrated automatatically when you run
cvd update to split it into config.json + state.json.

This change allows you to administrate the CVD-Update config files with a
config management tool.

Improvement courtesy of Bill Sanders.

Special thanks to:

• Bill Sanders
• Brent Clark
• Michael Callahan
• Philippe Ballandras

cvdupdate 1.0.2

🐛 Fixed a Python 3.6 compatibility issue in the package version check.

cvdupdate 1.0.1

🐛 Fixed a bug where the CVD-Update PyPI package version check prints an
error message on some systems where pip doesn't return the available
package versions.