Opened 9 years ago

Closed 9 years ago

#48951 closed defect (invalid)

Failed to verify signature for MacPorts source!

Reported by: matthew.s.whalley.civ@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.3.3
Keywords: Cc:
Port:

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

I've read through the past tickets trying to solve this problem without any luck. Any help would be appreciated.

af-arp-mac:~ arp$ sudo port -df selfupdate
DEBUG: Copying /Users/arp/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 69 bytes  70.00 bytes/sec
total size is 27013120  speedup is 257267.81
receiving file list ... done

sent 36 bytes  received 76 bytes  44.80 bytes/sec
total size is 512  speedup is 4.57
DEBUG: failed verification with key /opt/local/share/macports/macports-pubkey.pem
DEBUG: openssl output: child killed: segmentation violation
DEBUG: Failed to verify signature for MacPorts source!
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: Failed to verify signature for MacPorts source!
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Failed to verify signature for MacPorts source!

Change History (7)

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Component: portsbase
Description: modified (diff)

"segmentation violation" sounds like another word for "segmentation fault", in other words it sounds like openssl crashed. Any idea why? Did a crash log get written to ~/Library/Logs/DiagnosticReports? Does openssl work if you try to use it on the command line?

comment:2 Changed 9 years ago by matthew.s.whalley.civ@…

I didn't get a crash log. OpenSSL seems to run OK from the command line. The reported version is 1.0.2c --

af-arp-mac:~ arp$ openssl version
OpenSSL 1.0.2c 12 Jun 2015
af-arp-mac:~ arp$ which openssl
/opt/local/bin/openssl
Last edited 9 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

I'm not sure whether MacPorts would use the openssl you installed with MacPorts. Usually, it would use the one included with OS X. Can you test that one by running "/usr/bin/openssl version"?

comment:4 Changed 9 years ago by matthew.s.whalley.civ@…

I get --

af-arp-mac:~ arp$ /usr/bin/openssl version
Illegal instruction: 4
Last edited 9 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Ok, then that's what you'll have to fix. You could check again if a crash report was created this time. If so, it might shed light on what specifically the problem is. If not, I could take some guesses: /usr/bin/openssl might have been corrupted somehow, or might have been replaced with something else by some third-party installer you ran. Or maybe it wasn't /usr/bin/openssl but rather one of the libraries it uses, /usr/lib/libcrypto.0.9.8.dylib or /usr/lib/libssl.0.9.8.dylib. Try restoring any or all of those files from your backups, or reinstalling OS X.

comment:6 Changed 9 years ago by matthew.s.whalley.civ@…

Restoring openssl from backup worked. Thanks for the help!

comment:7 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: newclosed

Great, glad you got it working. Hopefully none of your other system libraries were overwritten by something...

Note: See TracTickets for help on using tickets.