sha1 and rmd160

[Blair Zajac]

On 4/5/12 9:53 PM, Arno Hautala wrote:
> On Fri, Apr 6, 2012 at 00:15, M. Daniel Becque<mdbecque at gmail.com>  wrote:
>> I'm working on upgrading the port of Proftpd from 1.3.3c to 1.3.3g as a
>> first step. From the binary file repository i see where the md5 #  comes
>> from but how do you get the sha1 and rmd160 numbers to place in the port
>> file? There is another file with each release, .asc, in the repository.
>
> sha1 and rmd160 can be generated with openssl:
>
> openssl sha1 path/to/file
> openssl rmd160 path/to/file
>
> The .asc file is a PGP signature that can be used to verify the
> integrity and authenticity of the source file. You don't need to worry
> about that for the Portfile.
>
> Also, I think md5 in Portfiles is deprecated. The preferred hashes are
> rmd160 and sha256.

If upstream provides a md5, I like to use it, as it makes double checking the 
port easier.

Blair