Metalinks Code

hash discussion with Nils.

Cryptographic Hashes

Currently, some of the hash types defined in the IANA registry named
"Hash Function Textual Names" are considered insecure. These include
the whole Message Digest family of algorithms which are not suitable
for cryptographically strong verification. Malicious people could
provide files that appear to be identical to another file because of
a collision, i.e. the weak cryptographic hashes match.

Metalink Generators and Processors supporting verification SHOULD at
least implement "sha-1" which is SHA1, as specified in [RFC3174].

Readme GPLv2 to GPLv3

- Updated license to GPLv3+ for all files, including the once missed earlier
- Updated the help message to GPLv3+
- Added dist_man_MANS to automake file (see bootstrap) to install manual page automatically

initial checkin of converter code

Add SHOULD for sha-1 whole file checksums, per Nils suggestion.

0.3.5 packaging cleanup release

started some code for setting pubdate in the future

bugfix to print out url in check results

GPL on eeeeverything, closes bug #2278178

- Metalink in release status 0.3.4
- Added manual
- Store template and style for usenix paper