[rancid] rancid finding changes that do not exist

[heasley]

Mon, Mar 23, 2015 at 10:04:34PM -0400, Terry Kennedy:
>   This is because Perl 5.18 and newer changed their sort algorithm. You
> should be able to fix it by adding:
> 
> # TMK - Deal with Perl 5.18's new random hashing (by nuking it)
> #PERL_HASH_SEED_DEBUG="1"; export PERL_HASH_SEED_DEBUG
> PERL_HASH_SEED="0123456789ABCDEF"; export PERL_HASH_SEED
> PERL_PERTURB_KEYS="0"; export PERL_PERTURB_KEYS
> 
>   near the top of your rancid.conf file. You can pick some random hex
> string for PERL_HASH_SEED if you like.

I do not believe that the problem Humes is having is related to this.

I also believe that changes have made setting these variables unnecessary
by 3.2.  If I am wrong, please let me know and I'll add them for 3.3.

>   For a more complete explanation of what Perl is doing by default, see:
> http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-Attacks
> 
>   There's some earlier discussion of the issue (without resolution) here:
> http://www.shrubbery.net/pipermail/rancid-discuss/2014-May/007630.html
> 
>         Terry Kennedy             http://www.ispnetinc.net
>         ISPnet, Inc.              New York, NY USA
>         terry at tmk.com             800-806-NETS
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss