Delayed Community Feed updates

Community Containers
1

Hi,
I have noticed that the community plugins (and apparently also the enterprise plugins) have not been updated / released since last August 27 at 0610.
I don’t want to complain, be assured, about something you provide for free and I and many others value, but this feed is almost a week old, so was wondering when the new plugins will be released.

I have tried to download an update several times over the past days and today, but the date is always the same…
Can you please advice?

Thanks for your work and your kind reply.

1 Like
2

Hey Niko.

Sorry for late response:
Due to the transition of the Community Container to a self-hosted registry, you may experience missing container updates on the current host!

We will reveal and update the documentation for the Community Container shortly!

And btw.: The “normal” way to update the feed is still working and everything is updated as usual for both enterprise and community feed. Only the data containers on DockerHub are missing some updates!

Thank you for your patience!

P.S.: Greetings from @_OR!

4 Likes
3

Hi Y0urself, and thank you for your reply.

Is the “normal” update that you mentioned the one we download from new URL mentioned in the Github page?

Because based on that URL, the community feed is still at ‘202408270610’.
At least that is what I get when downloading the plugin_feed_info.inc file using

rsync -ltvrP  rsync://feed.community.greenbone.net/community/vulnerability-feed/22.04/vt-data/nasl/plugin_feed_info.inc

I also checked the NVTs on the Greenbone Secinfo. The feed there is also from 27th August 2024.

Am I using the wrong URL, or is the feed present at the URL mentioned in github not updated?
May I ask you what is the date of the latest available community feed?

Thank you for you help and understanding!

Regards, Niko

1 Like
4

Yes!

Thank you again for checking. We identified the problem!

1 Like
5

Hi,
Even I have checked the last update is of 27-August-2024.

From plugin_feed_info.inc file:

# SPDX-FileCopyrightText: 2024 Greenbone AG
#
# SPDX-License-Identifier: GPL-2.0-or-later

PLUGIN_SET = "202408270610";
PLUGIN_FEED = "Greenbone Community Feed";
FEED_VENDOR = "Greenbone AG";
FEED_HOME = "https://www.greenbone.net/en/feed-comparison/";
FEED_NAME = "GCF";
FEED_COMMIT = "ecd6097f9205052c539abfe09dafdd0b9412f1ec";

Command:

rsync -ltvrP rsync://feed.community.greenbone.net:/nvt-feed/plugin_feed_info.inc

Regards,
Divesh

2 Likes
6

Hi y0urself,
I am glad that I could be of help in bringing this up to your attention.
Do you have any idea about when the problem will be solved? Approximately…

Thank you also to Divesh for checking.

2 Likes
7

So actually all feeds have been fixed.

(the feed-data container on docker.hub remain outdated!)

Again: Thank you for noticing this!

Edit: Feel free to verify!

5 Likes
8

I noticed the the SCAP, CERT and DATA Feeds are not up to date. The feeds an my system have the date Greenbone SCAP Data Feed - 20240822T0500 , Greenbone CERT Data Feed - 20240828T0408, Greenbone Data Objects Feed - 20240828T0504.

Only the Community-Feed is up to date.

The updates of the “feeds” and “containers” appear to be running normally, but the feeds continue to be outdated.

9

Hi @pat52538 the feed containers on docker.hub won’t be updated anymore.
This week we switch to the self-hosted registry.
More information shortly.

2 Likes
10

You should now be able to use the new registry and have up-to-date community feed content!

2 Likes
11

thanks - it works fine :grinning:

3 Likes
12

i still can’t update the Feed content.
how can be able to use the new registry to up-to-date the community feed content?

Should i wait until the documentation is updated?

many Thanks!

13

The dokumentation is updated. You must change the repository-url in the yml-file.
after update, everything works fine for me.

1 Like
14

Just download the new docker-compose.yaml file. :slight_smile: