From: Marta Rybczynska <rybczynska@gmail.com>
To: openembedded-core@lists.openembedded.org, ross.burton@arm.com
Cc: Marta Rybczynska <rybczynska@gmail.com>,
Marta Rybczynska <marta.rybczynska@huawei.com>
Subject: [PATCH 1/2] cve-update-db-native: update the CVE database once a day only
Date: Fri, 29 Apr 2022 08:32:25 +0200 [thread overview]
Message-ID: <20220429063226.22192-1-rybczynska@gmail.com> (raw)
The update of the NVD database was expected to happen once per hour.
However, the database file date changes only if the content was actually
updated. In practice, the check worked for the first hour after the
new download.
As the NVD database changes usually only once a day, we can just
update it less frequently.
Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>
---
meta/recipes-core/meta/cve-update-db-native.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/meta/cve-update-db-native.bb b/meta/recipes-core/meta/cve-update-db-native.bb
index e5822cee58..af39480dda 100644
--- a/meta/recipes-core/meta/cve-update-db-native.bb
+++ b/meta/recipes-core/meta/cve-update-db-native.bb
@@ -43,10 +43,10 @@ python do_fetch() {
if os.path.exists(db_file):
os.remove(db_file)
- # Don't refresh the database more than once an hour
+ # The NVD database changes once a day, so no need to update more frequently
try:
import time
- if time.time() - os.path.getmtime(db_file) < (60*60):
+ if time.time() - os.path.getmtime(db_file) < (24*60*60):
bb.debug(2, "Recently updated, skipping")
return
except OSError:
--
2.33.0
next reply other threads:[~2022-04-29 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 6:32 Marta Rybczynska [this message]
2022-04-29 6:32 ` [PATCH 2/2] cve-update-db-native: allow an option to force the CVE database update Marta Rybczynska
2022-04-29 15:53 ` [OE-core] " Ralph Siemsen
2022-05-02 13:23 ` Marta Rybczynska
2022-05-02 19:43 ` Ralph Siemsen
2022-05-02 19:53 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220429063226.22192-1-rybczynska@gmail.com \
--to=rybczynska@gmail.com \
--cc=marta.rybczynska@huawei.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox