3 ms·
RVM's installation is similar: https://rvm.io/rvm/install/ https://rvm.io/rvm/install/ A far cry from the safer/verified "download this and check it's MD5 che
by zdw 14y ago
RVM's installation is similar:
https://rvm.io/rvm/install/ https://rvm.io/rvm/install/
A far cry from the safer/verified "download this and check it's MD5 checksum" method that I'd prefer.
Seriously, fixing package management so we can continuously integrate arbitrary code would be great. Getting arbitrary OS package creation to be almost as easy as pushing code to GitHub seems like a very worthy goal.
- anthonyb 14y agomd5 is not going to protect you from much, especially if the md5 checksums are hosted on the same server. Also, pushing random code via apt-get is not going to win you any sysadmin friends. They like their servers to be stable, and their packages to be well tested.
- zdw 14y agoSeeing as you can remove said code via apt, you'd likely win them over compared to the alternative of being told to install compilers or some other non package managed software bundler like cpan/rvm/npm that can't be canned and easily deployed.
- mark_story 14y agoFor the longest time the installation instructions for NPM were almost exactly the same. But its worse when PHP does it :)
- brohee 14y agoIt's not the nineties anymore, MD5 doesn't protect you from much, and especially not from the author of the original package creating an alternate version. Viable verification is based on an unbroken hash (preferably SHA-(256|384|512), but SHA1 still not broken even it it's definitely too short nowadays. And the hashes need to be distributed properly, either PGP signed or hosted on a trusted TLS protected site... Yet many projects still distribute MD5 hashes, thinking it got any value.