You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,7 @@ Usage:
29
29
-V, --version show program's version number and exit
30
30
--disable-version-check
31
31
skips checking for a new version
32
+
--offline operate in offline mode
32
33
33
34
CVE Data Download:
34
35
-n {json,api}, --nvd {json,api}
@@ -118,6 +119,8 @@ in the terminal and provide it as an input by running `cve-bin-tool -L pkg-list`
118
119
You can use `--config` option to provide configuration file for the tool. You can still override options specified in config file with command line arguments. See our sample config files in the
Specifying the `--offline` option when running a scan ensures that cve-bin-tool doesn't attempt to download the latest database files or to check for a newer version of the tool.
123
+
121
124
The 0.3.1 release is intended to be the last release to officially support
122
125
python 2.7; please switch to python 3.6+ for future releases and to use the
123
126
development tree. You can check [our CI configuration](https://github.com/intel/cve-bin-tool/blob/main/.github/workflows/pythonapp.yml) to see what versions of python we're explicitly testing.
Copy file name to clipboardExpand all lines: doc/how_to_guides/offline.md
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -15,12 +15,15 @@ NOTE The tool will error with InsufficientArgs because no directory was specifie
15
15
The way of transfer depends on the environment. The files to be transferred are in "~/.cache/cve-bin-tool"
16
16
17
17
## Import the vulnerability database file on the offline system
18
-
The vulnerability database should be copied into ~/.cache/cve-bin-tool
18
+
The vulnerability database should be copied into ~/.cache/cve-bin-tool.
19
19
20
-
## Run cve-bin-tool with --update never and --disable-version-check options
21
-
In an offline environment, when running a scan specify `--update never` so that cve-bin-tool doesn't attempt to download the latest database files and `--disable-version-check` so that the cve-bin-tool doesn't attempt to check for a newer version of the tool.
20
+
The cve-bin-tool will fail to operate in offline mode if a vulnerability database is not present on the system.
21
+
22
+
## Run cve-bin-tool with --offline option
23
+
In an offline environment, specify the `--offline` option when running a scan so that cve-bin-tool doesn't attempt to download the latest database files or check for a newer version of the tool.
24
+
The `--offline` option is equivalent to specifying `--update never` and `--disable-version-check` options.
22
25
23
26
## Maintenance Updates
24
-
In an offline environment, it is important to update the vulnerability database on a regular basis as often as you feel appropriate, so that the scanner can continue to detect recently-identified vulnerabilities. If any changes to CVE data is required (e.g. to remove false positives), you might also want to create and copy over a triage data file for usage.
27
+
In an offline environment, it is important to update the vulnerability database on a regular basis as often as you feel appropriate, so that the scanner can continue to detect recently-identified vulnerabilities. If any changes to CVE data is required (e.g. to remove false positives), you might also want to create and copy over a triage data file for usage. The time of the latest database update is reported whenever a scan is performed.
25
28
26
29
It is important to periodically check if the cve-bin-tool has also been updated as this check cannot be performed within an offline environment.
0 commit comments