On Thursday, 19 December 2019 10:18:12 CET Dominique Dumont wrote:
> provided
> $YAML::XS::LoadBlessed is set to 0, which is not a problem for cme
Surprise..
Thanks to this test [1], it turns out that setting LoadBlessed with
a local does not work (i.e. "local $YAML::XS::LoadBlessed = 0;").
Hi Dominique,
> Dear debian-perl team colleagues, do you foresee any problem
> with this change?
None that I'm aware of... +1 to YAML::XS
Cheers!
Alex
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Alex Muntada
⢿⡄⠘⠷⠚⠋ Debian Developer log.alexm.org
⠈⠳⣄
signature.asc
Description: PGP signature
On Thu, 19 Dec 2019 10:18:12 +0100, Dominique Dumont wrote:
> Since the security issue related to YAML::XS has been fixed (provided
> $YAML::XS::LoadBlessed is set to 0, which is not a problem for cme), I see no
> issue to switch libconfig-model-dpkg-perl to YAML::XS instead of YAML::Tiny.
>
>
On Thursday, 19 December 2019 10:06:28 CET you wrote:
> However, I was unable to make pyyaml to generate the YAML format
> YAML::Tiny is always able to read, and apparently ruamel (judging by the
> code) has the same issue.
ok, I understand which instance of YAML::Tiny is causing trouble.
Since
On 15/12/2019 19:30, Dominique Dumont wrote:
> On Fri, 13 Dec 2019 14:23:46 +0100 Andrej Shadura
> wrote:
>> As a temporary workaround, I patched the locally used version to use
>> YAML::XS, but as I see you won?t accept this patch upstream. Is there a
>> solution that would satisfy both
On Fri, 13 Dec 2019 14:23:46 +0100 Andrej Shadura
wrote:
> As a temporary workaround, I patched the locally used version to use
> YAML::XS, but as I see you won?t accept this patch upstream. Is there a
> solution that would satisfy both conditions of how having security
> issues and supporting
On Sun, 05 Nov 2017 18:32:48 +0100 Dominique Dumont wrote:
> On Monday, 30 October 2017 15:27:32 CET you wrote:
> > YAML::XS::Load (and *hopefully* the other implementations of
> > YAML::Any::Load?) expect utf8 octets on input, not perl's internal
> > encoding.
>
> Uh ? I thought I had gotten
On Sun, 05 Nov 2017, Dominique Dumont wrote:
> Anyway, using YAML::Any has several problems:
> - it's deprecated
> - it may load YAML or YAML::XS which have some security issues [1]
Heh; that's a pretty nice bug.
> Instead, I'm going to replace YAML::Any with YAML::Tiny (which is more than
>
On Monday, 30 October 2017 15:27:32 CET you wrote:
> YAML::XS::Load (and *hopefully* the other implementations of
> YAML::Any::Load?) expect utf8 octets on input, not perl's internal
> encoding.
Uh ? I thought I had gotten rid of YAML::Any... Well, after checking, it turns
out that I've updated
Package: libconfig-model-dpkg-perl
Severity: normal
Version: 2.101
Tag: patch
YAML::XS::Load (and *hopefully* the other implementations of
YAML::Any::Load?) expect utf8 octets on input, not perl's internal
encoding.
Thus, slurp_raw should be used instead of slurp_utf8. [Though really,
10 matches
Mail list logo
