View Issue Details

IDProjectCategoryView StatusLast Update
0007685Kali LinuxGeneral Bugpublic2023-10-10 12:24
Reportervanguard Assigned Tosbrun  
PrioritylowSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Product Version2022.1 
Fixed in Version2022.3 
Summary0007685: gvm / gvmd - way of update confusing
Description

Dear kali-team,

for updating the expoit database, the documentation does not clearly show, how to update the databases. Whilst reading, I discovered several ways, which are historical grown.

This is what I found:

  1. run as root (or with sudo as a normal user):
    greenbone-nvt-sync
    greenbone-certdata-sync
    greenbone-scapdata-sync

  2. run as root (or with sudo as a normal user):
    runuser -u _gvm -- greenbone-nvt-sync
    runuser -u _gvm -- greenbone-feed-sync --type GVMD_DATA
    runuser -u _gvm -- greenbone-feed-sync --type SCAP
    runuser -u _gvm -- greenbone-feed-sync --type CERT

  3. run as root (or with sudo as a normal user):
    greenbone-feed-sync

All three ways seem to work. And different packages are telling different stories in their documentations.

I believe, the third one is a script developed only for kali.

However, as all ways seem to be successfull in its result, despite I would like to know, which is the best and the recommended way, to update the database.

Maybe you might want also to unite the documentation of the related packages.

Thank you very much for reading this and for your help.

Best regards

Hans

Activities

steev

steev

2022-04-29 17:05

manager   ~0016093

When you say documentation, can you please link to which documentation you mean?

vanguard

vanguard

2022-04-30 07:16

reporter   ~0016094

It is here:

/usr/share/doc/gvmd-common/README.Debian

  1. run as root (or with sudo as a normal user):
    greenbone-nvt-sync
    greenbone-certdata-sync
    greenbone-scapdata-sync

/usr/share/doc/gvm/README.Debian

  1. run as root (or with sudo as a normal user):
    runuser -u _gvm -- greenbone-nvt-sync
    runuser -u _gvm -- greenbone-feed-sync --type GVMD_DATA
    runuser -u _gvm -- greenbone-feed-sync --type SCAP
    runuser -u _gvm -- greenbone-feed-sync --type CERT

Last one, I was adviced by you, as this single script shall be a successor to the above commands.
(as far as I believe, it was in a discussion about a bug I reported, relazed to gvm/gvmd)

  1. run as root (or with sudo as a normal user):
    greenbone-feed-sync

As I said, it is just an info.

Best
Hans

sbrun

sbrun

2022-05-02 11:42

manager   ~0016098

In Kali / Debian greenbone-feed-sync or greenbone-nvt-sync must be run as _gvm user.

The README.Debian of gvmd needs to be updated.

vanguard

vanguard

2022-05-02 12:02

reporter   ~0016099

And the README.Debian of gvm-tools.

Your answer did not make clear, if one single command is enough, or if one has to repeat every single command with the tags of CERT, SCAP and GVMD_DATA.

sbrun

sbrun

2022-05-03 10:12

manager   ~0016108

Yes I need to update the README.Debian of gvm-tools too.

If you want to update all the data ( CERT, SCAP and GVMD_DATA), and the NVTs data, you can use:
sudo gvm-feed-update
It's provided by the package gvm.
Or you need to run the 4 commands (greenbone-nvt-sync and greenbone-feed-sync for each type of data)

If you want to update only the NVTs data, you must use:
sudo -u _gvm greenbone-nvt-sync or sudo runuser -u _gvm -- greenbone-nvt-sync
(you must run the command as user _gvm)

If you want to update the other data, you must use one of the following commands (depending on what you want to update). The type of data is required:
sudo greenbone-feed-sync --type GVMD_DATA
sudo greenbone-feed-sync --type SCAP
sudo greenbone-feed-sync --type CERT
Note that now these commands are run by default as user _gvm (thanks to your previous report bug).

FTR the following commands are kept by upstream:
greenbone-certdata-sync
greenbone-scapdata-sync
but the commands just call the command greenbone-feed-sync --type [...]

vanguard

vanguard

2022-05-03 20:31

reporter   ~0016109

Hi sbrun,

yes, that is the answer, I hoped to get. It makes everything crystal clear.

Thank you so much for enlighten me, it was very helpfull.

This issue can safely be closed!

Stay healthy and besgt regards!

Hans

vanguard

vanguard

2022-05-20 15:56

reporter   ~0016180

A note bnefore you close thios bug report:

When the actual command running is:
runuser -u _gvm -- greenbone-feed-sync --type GVMD_DATA
runuser -u _gvm -- greenbone-feed-sync --type SCAP
runuser -u _gvm -- greenbone-feed-sync --type CERT

and for complete feed update the command:

gvm-feed-update

is used today, then the following commands

greenbone-nvt-sync (in package openvas-scanner)
greenbone-certdata-sync (in package gvmd)
greenbone-scapdata-sync (in package gvmd)

should be removed, as they are obsolete.

This would decrease errotations.

Thank you for reading this.

best regards

Hans

sbrun

sbrun

2022-06-21 13:03

manager   ~0016311

the commands
greenbone-nvt-sync (in package openvas-scanner)
greenbone-certdata-sync (in package gvmd)
greenbone-scapdata-sync (in package gvmd)
are obsolete but upstream still provides them. We don't want to create too many differences between the Debian packages and the upstream code.

Issue History

Date Modified Username Field Change
2022-04-29 07:59 vanguard New Issue
2022-04-29 17:05 steev Assigned To => Gamb1t
2022-04-29 17:05 steev Status new => assigned
2022-04-29 17:05 steev Note Added: 0016093
2022-04-30 07:16 vanguard Note Added: 0016094
2022-05-02 11:39 sbrun Assigned To Gamb1t => sbrun
2022-05-02 11:42 sbrun Note Added: 0016098
2022-05-02 12:02 vanguard Note Added: 0016099
2022-05-02 14:54 Yash kc File Added: Screenshot_20220429_200832.jpg
2022-05-03 09:38 sbrun File Deleted: Screenshot_20220429_200832.jpg
2022-05-03 10:12 sbrun Note Added: 0016108
2022-05-03 20:31 vanguard Note Added: 0016109
2022-05-20 15:56 vanguard Note Added: 0016180
2022-06-21 13:03 sbrun Status assigned => resolved
2022-06-21 13:03 sbrun Resolution open => fixed
2022-06-21 13:03 sbrun Fixed in Version => 2022.3
2022-06-21 13:03 sbrun Note Added: 0016311
2023-10-10 12:24 vanguard Status resolved => closed