mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-03-06 15:29:40 +01:00
Code Issues Packages Projects Releases Wiki Activity

classes/sstate: don't use unsigned sstate when verification enabled

Browse Source 
When signature verification of shared state objects is enabled
(SSTATE_VERIFY_SIG) use of an unsigned object, even though it produces a
warning, seems unexpected. Instead skip unsigned objects and force the
non-accelerated task to be run.

(From OE-Core rev: 571235978d98552e3734bf382454dd51272db782)

Signed-off-by: Joshua Lock <jlock@vmware.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Joshua Lock via Openembedded-core
2019-07-26 11:26:49 +00:00
committed by Richard Purdie
parent c985a07e6a
commit f3e2c14850
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
meta/classes/sstate.bbclass
View File

@@ -340,7 +340,8 @@ def sstate_installpkg(ss, d):
if bb.utils.to_boolean(d.getVar("SSTATE_VERIFY_SIG"), False):
signer = get_signer(d, 'local')
if not signer.verify(sstatepkg + '.sig'):
bb.warn("Cannot verify signature on sstate package %s" % sstatepkg)
bb.warn("Cannot verify signature on sstate package %s, skipping acceleration..." % sstatepkg)
return False
# Empty sstateinst directory, ensure its clean
if os.path.exists(sstateinst):