Followup-For: Bug #857546
Hi,
libstrophe has got a fix on 4. July 2017 and I've submitted a
corresponding bug reported [1]. So thanks to Dmitry Podgorny (pasis)
there is no need anymore to make a package for a forked version.
Hopefully development continues on the original libstrophe.
Regar
Hi Tomasz,
Tomasz Buchert writes:
> it seems unlikely that we will be able to fix this for stretch. This
> would require a new package upload and this is already a
> no-go. Personally I think that forking libstrophe in the first place
> was not a great idea, but I may lack some context.
Ok, is t
On 12/03/17 13:53, Wolfgang Wiedmeyer wrote:
> Package: profanity
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Dear Maintainer,
>
> Profanity is not built against libmesode[1]. Libmesode is a fork of
> libstrophe that allows to validate the certificate chain. Upstream
Package: profanity
Severity: grave
Tags: security
Justification: user security hole
Dear Maintainer,
Profanity is not built against libmesode[1]. Libmesode is a fork of
libstrophe that allows to validate the certificate chain. Upstream bug
#280 provides more information[2]. Libmesode doesn't seem
4 matches
Mail list logo
