[rancid] rancid finding changes that do not exist

[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.

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
***@tmk.com 800-806-NETS

[Simen Stavdal]

Hi Terry,

Thanks for the suggestion. Added the variables to rancid.conf and ran it
again.
It produced the same messages in the log file.

Funny thing. I tried to install rancid3.1, and it worked flawlessly with
the same version of Perl.
Then i tried to go back to 3.2 and the same thing again.

I will go through the compilation logs to see if there is something not
quite right here.

Cheers,
Simon.

Post by Terry Kennedy
This is because Perl 5.18 and newer changed their sort algorithm. You
# 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.
http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-Attacks
http://www.shrubbery.net/pipermail/rancid-discuss/2014-May/007630.html
Terry Kennedy http://www.ispnetinc.net
ISPnet, Inc. New York, NY USA
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo/rancid-discuss

[heasley]

Post by Simen Stavdal
Thanks for the suggestion. Added the variables to rancid.conf and ran it
again.
It produced the same messages in the log file.

i believe terry is responding to a different issue.

Post by Simen Stavdal
Funny thing. I tried to install rancid3.1, and it worked flawlessly with
the same version of Perl.
Then i tried to go back to 3.2 and the same thing again.

I've already replied to you about this, but for other's edification; the
Socket.pm dependency did not appear until 3.2. I do not understand the
problem that you had updating Socket.pm, but suspect that something was
not updated properly by Socket's install process or you have multiple
perl installations. I tested updating Socket.pm and it worked.

[heasley]

Post by Terry Kennedy
This is because Perl 5.18 and newer changed their sort algorithm. You
# 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.

Post by Terry Kennedy
http://perldoc.perl.org/perlsec.html#Algorithmic-Complexity-Attacks
http://www.shrubbery.net/pipermail/rancid-discuss/2014-May/007630.html
Terry Kennedy http://www.ispnetinc.net
ISPnet, Inc. New York, NY USA
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo/rancid-discuss