Re: [yocto] CVE patch updates

2022-03-28 Thread Nicolas Jeker 
eck_hostname)
>  1393:
>  1394:    https_request = AbstractHTTPHandler.do_request_
>  1395:
>  1396:    __all__.append('HTTPSHandler')
> File: '/usr/lib64/python3.6/urllib/request.py', lineno: 1351,
> function: do_open
>  1347:    try:
>  1348:    h.request(req.get_method(), req.selector,
> req.data, headers,
>  1349: 
> encode_chunked=req.has_header('Transfer-encoding'))
>  1350:    except OSError as err: # timeout error
> *** 1351:    raise URLError(err)
>  1352:    r = h.getresponse()
>  1353:    except:
>  1354:    h.close()
>  1355:    raise
> Exception: urllib.error.URLError:  CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:877)>
>  
> ERROR: Logfile of failure stored in:
> /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-
> default/tmp/work/x86_64-linux/cve-update-db-native/1.0-
> r0/temp/log.do_populate_cve_db.4499
> ERROR: Task
> (/disk0/scratch/smonsees/yocto/workspace_1/poky/meta/recipes-
> core/meta/cve-update-db-native.bb:do_populate_cve_db) failed with
> exit code '1'
> NOTE: Tasks Summary: Attempted 5772 tasks of which 5228 didn't need
> to be rerun and 1 failed.
>  
> Summary: 1 task failed:
>   /disk0/scratch/smonsees/yocto/workspace_1/poky/meta/recipes-
> core/meta/cve-update-db-native.bb:do_populate_cve_db
> Summary: There was 1 ERROR message shown, returning a non-zero exit
> code.
> 14:41 smonsees@yix465383
> /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>find .
> -name '_ssl.c' -print
> 14:47 smonsees@yix465383
> /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>
>  
>  
>  
> From: yocto@lists.yoctoproject.org On
> Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
> Sent: Thursday, March 24, 2022 2:00 PM
> To: yocto@lists.yoctoproject.org
> Subject: Re: [yocto] CVE patch updates
>  
> External Email Alert This email has been sent from an account outside
> of the BAE Systems network. Please treat the email with caution,
> especially if you are requested to click on a link, decrypt/open an
> attachment, or enable macros.  For further information on how to spot
> phishing, access “Cybersecurity OneSpace Page” and report phishing by
> clicking the button “Report Phishing” on the Outlook toolbar.
>  
>  
> When building in cve-check to see what is reported, it generated all
> blank/empty report files…
> Can someone explain this ?, my local.conf does have the proper
> modification (INHERIT += “cve-check”).
>  
>  
> 10:55 smonsees@yix465383
> /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>
> bitbake -k sbca-defaultfs-full
> Parsing recipes: 100%
> |
> #| Time: 0:01:07
> Parsing of 2555 .bb files complete (0 cached, 2555 parsed). 3769
> targets, 96 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>  
> Build Configuration:
> BB_VERSION   = "1.44.0"
> BUILD_SYS    = "x86_64-linux"
> NATIVELSBSTRING  = "rhel-7.9"
> TARGET_SYS   = "x86_64-poky-linux"
> MACHINE  = "sbca-default"
> DISTRO   = "limws"
> DISTRO_VERSION   = "3.0.4"
> TUNE_FEATURES    = "m64 corei7"
> TARGET_FPU   = ""
> meta 
> meta-poky    =
> "my_yocto_3.0.4:2f9bca440204f9e73158705a4ec04698b1f6ad42"
> meta-perl    
> meta-python  
> meta-filesystems 
> meta-networking  
> meta-initramfs   
> meta-oe  =
> "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"
> meta-virtualization  =
> "zeus:7e5219669ff6f8e9c8c33ffd230e95a6b2b025f4"
> meta =
> "master:a32ddd2b2a51b26c011fa50e441df39304651503"
> meta-clang   =
> "zeus:f5355ca9b86fb5de5930132ffd95a9b352d694f9"
> meta-intel   =
> "zeus:d9942d4c3a710406b051852de7232db03c297f4e"
> meta-intel   = "LIMWSSWARE-682-oews-meta-bae-clean-
> up:99f116056452f1fefe83fe458f533b48f52fe4ba"
>  
> Initialising tasks: 100%
> |
> ##| Time: 0:00:04
> Checking sstate mirror object availability: 100%
> |##|
> Time: 0:00:02
> Sstate summary: Wanted 2258 Found 15 Missed 2243 Current 0 (0% match,
> 0% complete)
> NOTE: Executing Tasks
> NOTE: Setscene tasks

Re: [yocto] CVE patch updates

2022-03-25 Thread Monsees, Steven C (US) via lists.yoctoproject.org 

Thanks Tim,  subscribed…

From: Tim Orling 
Sent: Thursday, March 24, 2022 9:03 PM
To: Richard Purdie 
Cc: Monsees, Steven C (US) ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] CVE patch updates

External Email Alert

This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click 
on a link, decrypt/open an attachment, or enable macros.  For further 
information on how to spot phishing, access “Cybersecurity OneSpace Page” and 
report phishing by clicking the button “Report Phishing” on the Outlook toolbar.




On Thu, Mar 24, 2022 at 2:45 PM Richard Purdie 
mailto:richard.pur...@linuxfoundation.org>> 
wrote:
On Thu, 2022-03-24 at 16:56 +, Monsees, Steven C (US) via
lists.yoctoproject.org<http://lists.yoctoproject.org> wrote:
>
> I am currently building in cve-check to see what is reported, and I was 
> curious
> if Yocto might provide any CVE based patch repositories ?
>
> Is there a yocto page somewhere that goes over this side of things ?,
> I did not see much in the mega-manual… I am running on zeus based platforms 
> (for
> both armarch64 and x86_64).
>

You'll see output of cve-check on the yocto-security list for layers that are
still in maintenance:

https://lists.yoctoproject.org/g/yocto-security/messages

although zeus is out of maintenance.

We merge CVE fixes to the branches that are in maintenance.

A graph showing the data over time:

https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488=interactive

Steven, if you haven’t already, you should subscribe to
https://lists.yoctoproject.org/g/yocto-security

Emails are sent out, usually on Sunday. If you see a CVE that interests you… 
grab it and fix it.

This is mostly a community effort. There is no special dedicated squad of 
security champions.


Cheers,

Richard






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56562): https://lists.yoctoproject.org/g/yocto/message/56562
Mute This Topic: https://lists.yoctoproject.org/mt/90004034/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] CVE patch updates

2022-03-25 Thread Monsees, Steven C (US) via lists.yoctoproject.org 

Thanks Richard, will do…

From: Tim Orling 
Sent: Thursday, March 24, 2022 9:03 PM
To: Richard Purdie 
Cc: Monsees, Steven C (US) ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] CVE patch updates

External Email Alert

This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click 
on a link, decrypt/open an attachment, or enable macros.  For further 
information on how to spot phishing, access “Cybersecurity OneSpace Page” and 
report phishing by clicking the button “Report Phishing” on the Outlook toolbar.




On Thu, Mar 24, 2022 at 2:45 PM Richard Purdie 
mailto:richard.pur...@linuxfoundation.org>> 
wrote:
On Thu, 2022-03-24 at 16:56 +, Monsees, Steven C (US) via
lists.yoctoproject.org<http://lists.yoctoproject.org> wrote:
>
> I am currently building in cve-check to see what is reported, and I was 
> curious
> if Yocto might provide any CVE based patch repositories ?
>
> Is there a yocto page somewhere that goes over this side of things ?,
> I did not see much in the mega-manual… I am running on zeus based platforms 
> (for
> both armarch64 and x86_64).
>

You'll see output of cve-check on the yocto-security list for layers that are
still in maintenance:

https://lists.yoctoproject.org/g/yocto-security/messages

although zeus is out of maintenance.

We merge CVE fixes to the branches that are in maintenance.

A graph showing the data over time:

https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488=interactive

Steven, if you haven’t already, you should subscribe to
https://lists.yoctoproject.org/g/yocto-security

Emails are sent out, usually on Sunday. If you see a CVE that interests you… 
grab it and fix it.

This is mostly a community effort. There is no special dedicated squad of 
security champions.


Cheers,

Richard






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56561): https://lists.yoctoproject.org/g/yocto/message/56561
Mute This Topic: https://lists.yoctoproject.org/mt/90004034/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] CVE patch updates

2022-03-24 Thread Tim Orling 
On Thu, Mar 24, 2022 at 2:45 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Thu, 2022-03-24 at 16:56 +, Monsees, Steven C (US) via
> lists.yoctoproject.org wrote:
> >
> > I am currently building in cve-check to see what is reported, and I was
> curious
> > if Yocto might provide any CVE based patch repositories ?
> >
> > Is there a yocto page somewhere that goes over this side of things ?,
> > I did not see much in the mega-manual… I am running on zeus based
> platforms (for
> > both armarch64 and x86_64).
> >
>
> You'll see output of cve-check on the yocto-security list for layers that
> are
> still in maintenance:
>
> https://lists.yoctoproject.org/g/yocto-security/messages
>
> although zeus is out of maintenance.
>
> We merge CVE fixes to the branches that are in maintenance.
>
> A graph showing the data over time:
>
>
> https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488=interactive
>

Steven, if you haven’t already, you should subscribe to
https://lists.yoctoproject.org/g/yocto-security

Emails are sent out, usually on Sunday. If you see a CVE that interests
you… grab it and fix it.

This is mostly a community effort. There is no special dedicated squad of
security champions.


> Cheers,
>
> Richard
>
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56558): https://lists.yoctoproject.org/g/yocto/message/56558
Mute This Topic: https://lists.yoctoproject.org/mt/90004034/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] CVE patch updates

2022-03-24 Thread Richard Purdie 
On Thu, 2022-03-24 at 16:56 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
>   
> I am currently building in cve-check to see what is reported, and I was 
> curious
> if Yocto might provide any CVE based patch repositories ?
>  
> Is there a yocto page somewhere that goes over this side of things ?,
> I did not see much in the mega-manual… I am running on zeus based platforms 
> (for
> both armarch64 and x86_64).
> 

You'll see output of cve-check on the yocto-security list for layers that are
still in maintenance:

https://lists.yoctoproject.org/g/yocto-security/messages

although zeus is out of maintenance.

We merge CVE fixes to the branches that are in maintenance.

A graph showing the data over time:

https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488=interactive

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56555): https://lists.yoctoproject.org/g/yocto/message/56555
Mute This Topic: https://lists.yoctoproject.org/mt/90004034/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] CVE patch updates

2022-03-24 Thread Monsees, Steven C (US) via lists.yoctoproject.org 
/yocto/workspace_1/poky/meta/recipes-core/meta/cve-update-db-native.bb:do_populate_cve_db
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
14:41 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>find . -name 
'_ssl.c' -print
14:47 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>



From: yocto@lists.yoctoproject.org  On Behalf Of 
Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Thursday, March 24, 2022 2:00 PM
To: yocto@lists.yoctoproject.org
Subject: Re: [yocto] CVE patch updates

External Email Alert

This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click 
on a link, decrypt/open an attachment, or enable macros.  For further 
information on how to spot phishing, access “Cybersecurity OneSpace Page” and 
report phishing by clicking the button “Report Phishing” on the Outlook toolbar.



When building in cve-check to see what is reported, it generated all 
blank/empty report files…
Can someone explain this ?, my local.conf does have the proper modification 
(INHERIT += “cve-check”).


10:55 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default> bitbake -k 
sbca-defaultfs-full
Parsing recipes: 100% 
|#|
 Time: 0:01:07
Parsing of 2555 .bb files complete (0 cached, 2555 parsed). 3769 targets, 96 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.44.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "rhel-7.9"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "sbca-default"
DISTRO   = "limws"
DISTRO_VERSION   = "3.0.4"
TUNE_FEATURES= "m64 corei7"
TARGET_FPU   = ""
meta
meta-poky= "my_yocto_3.0.4:2f9bca440204f9e73158705a4ec04698b1f6ad42"
meta-perl
meta-python
meta-filesystems
meta-networking
meta-initramfs
meta-oe  = "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"
meta-virtualization  = "zeus:7e5219669ff6f8e9c8c33ffd230e95a6b2b025f4"
meta = "master:a32ddd2b2a51b26c011fa50e441df39304651503"
meta-clang   = "zeus:f5355ca9b86fb5de5930132ffd95a9b352d694f9"
meta-intel   = "zeus:d9942d4c3a710406b051852de7232db03c297f4e"
meta-intel   = 
"LIMWSSWARE-682-oews-meta-bae-clean-up:99f116056452f1fefe83fe458f533b48f52fe4ba"

Initialising tasks: 100% 
|##|
 Time: 0:00:04
Checking sstate mirror object availability: 100% 
|##| Time: 
0:00:02
Sstate summary: Wanted 2258 Found 15 Missed 2243 Current 0 (0% match, 0% 
complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
Image CVE report stored in: 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/core-image-minimal-initramfs-sbca-default-20220324145629.rootfs.cve
Image CVE report stored in: 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/aiox_orange-sbca-default-20220324145629.rootfs.cve
NOTE: Tasks Summary: Attempted 6753 tasks of which 77 didn't need to be rerun 
and all succeeded.


13:33 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>ls -l 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/core-image-minimal-initramfs-sbca-default-20220324145629.rootfs.cve
-rw-r--r--. 1 smonsees none 0 Mar 24 13:16 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/core-image-minimal-initramfs-sbca-default-20220324145629.rootfs.cve
13:33 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>ls -l 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/aiox_orange-sbca-default-20220324145629.rootfs.cve
-rw-r--r--. 1 smonsees none 0 Mar 24 13:17 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/aiox_orange-sbca-default-20220324145629.rootfs.cve
13:33 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>


13:27 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/cve>ls
 -l
total 0
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 binutils
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 binutils-cross-x86_64
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 binutils-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 bluez5
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:12 boost
-rw-rw-r--. 1

Re: [yocto] CVE patch updates

2022-03-24 Thread Monsees, Steven C (US) via lists.yoctoproject.org 

When building in cve-check to see what is reported, it generated all 
blank/empty report files...
Can someone explain this ?, my local.conf does have the proper modification 
(INHERIT += "cve-check").


10:55 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default> bitbake -k 
sbca-defaultfs-full
Parsing recipes: 100% 
|#|
 Time: 0:01:07
Parsing of 2555 .bb files complete (0 cached, 2555 parsed). 3769 targets, 96 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.44.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "rhel-7.9"
TARGET_SYS   = "x86_64-poky-linux"
MACHINE  = "sbca-default"
DISTRO   = "limws"
DISTRO_VERSION   = "3.0.4"
TUNE_FEATURES= "m64 corei7"
TARGET_FPU   = ""
meta
meta-poky= "my_yocto_3.0.4:2f9bca440204f9e73158705a4ec04698b1f6ad42"
meta-perl
meta-python
meta-filesystems
meta-networking
meta-initramfs
meta-oe  = "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"
meta-virtualization  = "zeus:7e5219669ff6f8e9c8c33ffd230e95a6b2b025f4"
meta = "master:a32ddd2b2a51b26c011fa50e441df39304651503"
meta-clang   = "zeus:f5355ca9b86fb5de5930132ffd95a9b352d694f9"
meta-intel   = "zeus:d9942d4c3a710406b051852de7232db03c297f4e"
meta-intel   = 
"LIMWSSWARE-682-oews-meta-bae-clean-up:99f116056452f1fefe83fe458f533b48f52fe4ba"

Initialising tasks: 100% 
|##|
 Time: 0:00:04
Checking sstate mirror object availability: 100% 
|##| Time: 
0:00:02
Sstate summary: Wanted 2258 Found 15 Missed 2243 Current 0 (0% match, 0% 
complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
Image CVE report stored in: 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/core-image-minimal-initramfs-sbca-default-20220324145629.rootfs.cve
Image CVE report stored in: 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/aiox_orange-sbca-default-20220324145629.rootfs.cve
NOTE: Tasks Summary: Attempted 6753 tasks of which 77 didn't need to be rerun 
and all succeeded.


13:33 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>ls -l 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/core-image-minimal-initramfs-sbca-default-20220324145629.rootfs.cve
-rw-r--r--. 1 smonsees none 0 Mar 24 13:16 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/core-image-minimal-initramfs-sbca-default-20220324145629.rootfs.cve
13:33 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>ls -l 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/aiox_orange-sbca-default-20220324145629.rootfs.cve
-rw-r--r--. 1 smonsees none 0 Mar 24 13:17 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/images/sbca-default/aiox_orange-sbca-default-20220324145629.rootfs.cve
13:33 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default>


13:27 smonsees@yix465383 
/disk0/scratch/smonsees/yocto/workspace_1/builds2/sbca-default/tmp/deploy/cve>ls
 -l
total 0
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 binutils
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 binutils-cross-x86_64
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 binutils-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 bluez5
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:12 boost
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 cairo
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:12 cairo-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:16 cpio-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 curl
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:05 curl-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:05 dbus
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:05 dbus-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 e2fsprogs
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 e2fsprogs-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:05 file-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 flex
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 flex-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:05 gcc-source-9.2.0
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 gettext-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 glib-2.0
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:05 glib-2.0-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:06 glibc
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 gnutls
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 go-cross-corei7-64
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 go-native
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:13 go-runtime
-rw-rw-r--. 1 smonsees none 0 Mar 24 13:12

[yocto] CVE patch updates

2022-03-24 Thread Monsees, Steven C (US) via lists.yoctoproject.org 


I am currently building in cve-check to see what is reported, and I was curious 
if Yocto might provide any CVE based patch repositories ?

Is there a yocto page somewhere that goes over this side of things ?,
I did not see much in the mega-manual... I am running on zeus based platforms 
(for both armarch64 and x86_64).

Thanks,
Steve

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56552): https://lists.yoctoproject.org/g/yocto/message/56552
Mute This Topic: https://lists.yoctoproject.org/mt/90004034/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-