On Sat, Oct 19, 2019 at 2:58 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Fri, 2019-10-18 at 18:03 +0530, Khem Raj wrote:
> >
> >
> > On Fri, Oct 18, 2019 at 4:58 PM Ross Burton
> > wrote:
> > > file will automatically enable seccomp if the seccomp headers are
> > >
On 10/18/19 3:32 PM, Trevor Gamblin wrote:
Note that there are two patch files added for this fix.
Signed-off-by: Trevor Gamblin
---
...cdsa-Fix-use-of-nonce-use-larger-one.patch | 126 ++
...Add-mitigation-against-timing-attack.patch | 68 ++
On Sat, 2019-10-19 at 00:01 +0200, Andreas Müller wrote:
> On Fri, Oct 18, 2019 at 8:50 PM Alexander Kanavin
> wrote:
> > I certainly don't mean to ignore those reports, it's just that due
> > to my ongoing health problems, and having to dedicate most of my
> > energy to the day job
On Fri, Oct 18, 2019 at 8:50 PM Alexander Kanavin
wrote:
>
> I certainly don't mean to ignore those reports, it's just that due to my
> ongoing health problems, and having to dedicate most of my energy to the day
> job (https://mbition.io/en/home/), I am not currently able to work on the
>
On Fri, 2019-10-18 at 18:03 +0530, Khem Raj wrote:
>
>
> On Fri, Oct 18, 2019 at 4:58 PM Ross Burton
> wrote:
> > file will automatically enable seccomp if the seccomp headers are
> > available, but
> > the build will fail on Opensuse Tumbleweed because the include
> > paths are wrong.
> >
> >
On Fri, 2019-10-18 at 20:49 +0200, Alexander Kanavin wrote:
> I certainly don't mean to ignore those reports, it's just that due to
> my ongoing health problems, and having to dedicate most of my energy
> to the day job (https://mbition.io/en/home/), I am not currently able
> to work on the
On 10/18/19 10:58 AM, Alejandro Del Castillo wrote:
>
> On 10/17/19 3:01 PM, Denys Dmytriyenko wrote:
>> On Thu, Oct 17, 2019 at 12:21:11PM -0700, akuster808 wrote:
>>> On 10/17/19 11:42 AM, Denys Dmytriyenko wrote:
Thank you for this revert! I've been pulling my hair out past couple days
Hi,
Updated oe-core from
commit 9973f89dafdf9d21f4021f59f1f4669f4ac13aff
Author: Chen Qi
Date: Fri Sep 27 14:42:51 2019 +0800
systemd: fix NFS regression
To
Author: Khem Raj
Date: Sat Oct 12 17:51:17 2019 -0700
glib-2.0: Fix build with clang compiler
and reverted meson 0.52.0
Note that there are two patch files added for this fix.
Signed-off-by: Trevor Gamblin
---
...cdsa-Fix-use-of-nonce-use-larger-one.patch | 126 ++
...Add-mitigation-against-timing-attack.patch | 68 ++
.../libgcrypt/libgcrypt_1.8.4.bb | 2 +
3 files
Note that there are two patch files added for this fix.
Signed-off-by: Trevor Gamblin
---
...cdsa-Fix-use-of-nonce-use-larger-one.patch | 126 ++
...Add-mitigation-against-timing-attack.patch | 68 ++
.../libgcrypt/libgcrypt_1.8.4.bb | 2 +
3 files
I certainly don't mean to ignore those reports, it's just that due to my
ongoing health problems, and having to dedicate most of my energy to the
day job (https://mbition.io/en/home/), I am not currently able to work on
the upstream issues in a timely manner the way I used to when maintaining
core
On 10/17/19 3:01 PM, Denys Dmytriyenko wrote:
> On Thu, Oct 17, 2019 at 12:21:11PM -0700, akuster808 wrote:
>> On 10/17/19 11:42 AM, Denys Dmytriyenko wrote:
>>> Thank you for this revert! I've been pulling my hair out past couple days
>>> figuring out why BAD_RECOMMENDATIONS stopped working
Backport changes to tinfo/comp_hash.c, tinfo/parse_entry.c,
and progs/dump_entry.c from upstream to fix CVEs.
Signed-off-by: Trevor Gamblin
---
...selective-backport-of-20191012-patch.patch | 169 ++
.../ncurses/ncurses_6.1+20190803.bb | 1 +
2 files changed, 170
Backport changes to tinfo/comp_hash.c, tinfo/parse_entry.c,
and progs/dump_entry.c from upstream to fix CVEs.
Signed-off-by: Trevor Gamblin
---
...selective-backport-of-20191012-patch.patch | 169 ++
.../ncurses/ncurses_6.1+20190803.bb | 1 +
2 files changed, 170
On Fri, Oct 18, 2019 at 4:58 PM Ross Burton wrote:
> file will automatically enable seccomp if the seccomp headers are
> available, but
> the build will fail on Opensuse Tumbleweed because the include paths are
> wrong.
>
> Enabling seccomp is a bad idea because it interacts badly with pseudo
>
file will automatically enable seccomp if the seccomp headers are available, but
the build will fail on Opensuse Tumbleweed because the include paths are wrong.
Enabling seccomp is a bad idea because it interacts badly with pseudo (causing
build failures), so explicitly and globally disable
If the source file is located in a subdirectory of DEPLOY_DIR
rawcopy will currently fail in sparse_copy function on
open(dst_fname, 'wb'), as the parent directory for destination
file does not exist.
This patch helps to avoid that by recursively creating
parent directories.
Signed-off-by:
Backport a patch from upstream to fix CVE-2019-16905
https://github.com/openssh/openssh-portable/commit/a546b17bbaeb12beac4c9aeed56f74a42b18a93a
Signed-off-by: Hongxu Jia
---
...x-integer-overflow-in-XMSS-private-key-pa.patch | 40 ++
18 matches
Mail list logo
