(This is relevant: on fixing core modules in place ) Sometimes people change core modules. I've seen this happen too. The core modules could change for different reasons also- this would be a great place to do funny stuff for some malicious persons. Potentially inhouse? (Too paranoid?)
So.. how about we make a module, that checks the integrity of modules on a box, against a cpan repository? Checking.. what? md5sums?
Does the cli cpan tool check integrity of installed modules? No- right? Just the version numbers.. ?
Does anyone see any use to have a http query(able) repository of md5sums of module versions?
Could have a config file, that you tell it what to do if anomalies are found, halt perl, halt system, re-install module.. who knows..
Is there something of this sort already out there ? :) Is this really something that should be in the cpan cli tool instead? - or.. something that really should be done entirely by someone else, like brian d foy? Heehee.
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |