Opened 13 years ago

Last modified 13 years ago

#29392 closed defect

metasploit3: checksum mismatch — at Version 1

Reported by: rhizome23@… Owned by: opendarwin.org@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc: ryandesign@…
Port: metasploit3

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I suspect the hash values just need updating. 

--->  Fetching metasploit3
--->  Attempting to fetch framework-3.0.tar.gz from http://framework.metasploit.com/releases/
--->  Verifying checksum(s) for metasploit3
Error: Checksum (md5) mismatch for framework-3.0.tar.gz
Error: Checksum (sha1) mismatch for framework-3.0.tar.gz
***
The non-matching file appears to be HTML. See this page for possible reasons
for the checksum mismatch:
<http://trac.macports.org/wiki/MisbehavingServers>
***
Error: Target org.macports.checksum returned: Unable to verify file checksums
Log for metasploit3 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_security_metasploit3/main.log
Error: Status 1 encountered during processing.

Change History (1)

comment:1 in reply to:  description Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Description: modified (diff)
Keywords: metasploit3 hashmismatch removed
Owner: changed from macports-tickets@… to opendarwin.org@…
Priority: Low → Normal
Summary: MD5 and SHA1 Mismatch for metasploit3 → metasploit3: checksum mismatch

Replying to rhizome23@…:

I suspect the hash values just need updating.

Unlikely. See where it says "The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: MisbehavingServers". Did you read that page? In this case, it is actually metasploit's own web server that is misconfigured, and delivers a "200 OK" response even for documents which should be reported as "404 Not Found".

See also #24103. The port is years out of date.

Note: See TracTickets for help on using tickets.