[rancid] rancid finding changes that do not exist

Terry Kennedy TERRY at tmk.com
Tue Mar 24 02:04:34 UTC 2015


  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.

  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


More information about the Rancid-discuss mailing list