develooper Front page | perl.perl5.porters | Postings from July 2020

Re: PERL_PERTURB_KEYS=2

Thread Previous | Thread Next
From:
demerphq
Date:
July 29, 2020 06:51
Subject:
Re: PERL_PERTURB_KEYS=2
Message ID:
CANgJU+VOZD4h0HkPttC=eC=8ygsSNJ+n3bk3fsPEWCz2iuqJ-Q@mail.gmail.com
On Wed, 29 Jul 2020 at 00:00, <hv@crypt.org> wrote:
>
> demerphq <demerphq@gmail.com> wrote:
> :Can you tell me what PERL_HASH_SEED_DEBUG=1 reports for you?
> :
> :I have a feeling your perl is built with hadh seed randomization disabled.
>
> % PERL_HASH_SEED_DEBUG=1 /opt/v5.32.0-d/bin/perl -e 1
> HASH_FUNCTION = SBOX32_WITH_STADTX HASH_SEED = 0x986401ef56ab149158c74ee4062846bd8b8504d92918d2beaf137d90 PERTURB_KEYS = 1 (RANDOM)

Ok,  I get it now. Your perl is /opt/v5.32.0-d/bin/perl. But your
script references the system perl in your $PATH. I think if you change
your test script to use $^X instead of q{perl} you will get the
desired results. I suggest you have the inner perl print $], and
enable PERL_HASH_SEED_DEBUG=1 when you run the test script so you can
see details of both the outer and inner perl separately. My guess is
you have an old perl, maybe pre hash randomization in your system path
and you simply arent testing the perl you think you are.


cheers,
Yves

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About