It is unlikely that this is an interoperability issue with GPG itself (public keys should be importable anywhere), it almost certainly is something to do with the fact Mac software for GPG is wildly more complicated to setup and use than it ought to be, as well as the many bugs that GPGTools appears to have from the continual outcry we hear about it on here. If you're using Mountain Lion OSX, you need a different version of GPGTools than the one for Lion or Snow Leopard, the "nightly install" I think it's called.This is one advantage of the command line, it's almost identical no matter what operating system you're on. Without meaning to be a jerk, being a Mac user may not be a good idea in general when using SR. There is a bunch of esoteric computer problems that can fuck with you, such as how Mac/Windows/Linux don't use the same newline characters. So if you save a text file with a PGP key created with Mac, and send it to a Linux or Windows user as a plaintext text file attachment, they're not able to import it.One particular bugbear I found recently wasn't an EOL issue although I thought it was at first, but I mean look at this example:http://www.thismachinekillssecrets.com/contact/This journalist wrote an entire book on Cypherpunks and PGP. Now look at his PGP key. You can't import his public key. It's easily solvable using the <pre> tag in the HTML source, but it's not exactly the most intuitive problem, a noob would be utterly poleaxed by something like that.All of the fucked up situations with garbled PGP keys I've seen are correlated to whether the user has a Mac, even when the Mac itself is not the problem. The idea that Macs are easier to use is a total myth from where I'm standing. They give you bad habits and stupid ideas about how computers work. I know people are always having holy wars over non-existent differences between OSes, but I think what I'm saying is an objective fact, it can be measured, Science!