Replies: 3 comments 2 replies
-
|
Hi James, on the one hand we have the docker image. Within the docker image the cve-bin-tool is located in /external/cve-bin-tool. If you are updating the cve database on your host it is usually somewhere in your pip environment. If you have updated your cve database on your host and you copy it to the EMBA config directory then EMBA is using your database from your host. With this little trick you are able to update your cve database without loosing your fallback in your docker base image. Hope this helps |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @m-1-k-3 ! So for copying the cve database on my host to the EMBA config directory, I just need to do the followings? cve-bin-tool --export /config/cve-database.db Best regards |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, @m-1-k-3 , for your help! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In the EMBA Wiki "Installation -- EMBA update" section, it said:
while in F17_cve_bin_tool.sh
cve-bin-tool is referenced as below
My questions is which cve-bin-tool is used in emba for generating the cve-list? If the local installation, how was it linked to the definition in F17_cve_bin_tool.sh? If "/external/cve-bin-tool/cve_bin_tool/cli.py" is used, I did not see it in "emba/external" directory after installation. Did I miss any steps ?
Thanks
James
Beta Was this translation helpful? Give feedback.
All reactions