Salvatore Bonaccorso, le ven. 25 mai 2018 19:33:46 +0200, a ecrit:
> (although it's alowed to already upload, the release team still would
> like to have a bug for the update, cf. [1])
Sure, I was just wondering whether such security uploads would go
through the security team, or just the normal
Hello Samuel,
On Fri, May 25, 2018 at 01:15:55PM +0200, Samuel Thibault wrote:
> Hello,
>
> Salvatore Bonaccorso, le ven. 25 mai 2018 12:24:28 +0200, a ecrit:
> > On Fri, May 25, 2018 at 11:00:49AM +0200, Samuel Thibault wrote:
> > > Hello
> > >
> > > Salvatore Bonaccorso, le jeu. 24 mai 2018
Hello,
Salvatore Bonaccorso, le ven. 25 mai 2018 12:24:28 +0200, a ecrit:
> On Fri, May 25, 2018 at 11:00:49AM +0200, Samuel Thibault wrote:
> > Hello
> >
> > Salvatore Bonaccorso, le jeu. 24 mai 2018 16:16:16 +0200, a ecrit:
> > > The following vulnerability was published for liblouis, it was
>
Hi Samuel,
On Fri, May 25, 2018 at 11:00:49AM +0200, Samuel Thibault wrote:
> Hello
>
> Salvatore Bonaccorso, le jeu. 24 mai 2018 16:16:16 +0200, a ecrit:
> > The following vulnerability was published for liblouis, it was
> > reported at [1], not sure if it was forwarded to upstream, can you
> >
Hello
Salvatore Bonaccorso, le jeu. 24 mai 2018 16:16:16 +0200, a ecrit:
> The following vulnerability was published for liblouis, it was
> reported at [1], not sure if it was forwarded to upstream, can you
> double check that?
I reported it to upstream and is now fixed there. I have uploaded a
Source: liblouis
Version: 3.5.0-1
Severity: important
Tags: security upstream
Hi,
The following vulnerability was published for liblouis, it was
reported at [1], not sure if it was forwarded to upstream, can you
double check that?
CVE-2018-11410[0]:
| An issue was discovered in Liblouis 3.5.0.
6 matches
Mail list logo
