Re: [Macgpg-users] trouble figuring out how to import a public key from windows to mac gnugpg

[tombb <sti...@co...>]

Very strange. All versions that I sent over to the Mac were not appropriately
formatted-- was missing the heading and ender info; just gooptext-- no
matter what format I saved it in. I then decided to open on winpc in Word
and save as a Word file--to preserve the formatting as text instead of
gooptext. I could open that Word doc on Mac without problem, so I copied
this text and pasted it into a textwrangler document and saved it as unix
coded document (thanks, Charlie!).  I could then import this into gpg
keychain access without problem-- a bit of a clumsy struggle, I must say. I
was expecting that by using Gnu PGP across platform would ensure easy
compatibility when emailing keys, but apparently this is not the case.

1. Do you guys also see this difficulty when working across platform, or do
do you think I might have a setup issue?

2. Also, even though I have the public key form my wife's windows based
account and can decrypt messages, and the message shows that it is signed,
but it also says "validity:unknown"-- I saw in the windows enigmail plugin
inteerface how to set the trust level of others signatures, but how can I do
this in the Mac environment, either through gpg keychain access or the sente
Mail plugin interface?

Sorry for the length and for burying my 2 last questions, but you guys have
been great in helping me sort this out. I look forward to any suggestions
and comments you have for hte other 2 issues.



Jack Repenning-3 wrote:
> 
> On Apr 13, 2007, at 6:25 AM, tombb wrote:
> 
>> Question here: able to encrypt/sign when I am sending messages back  
>> and
>> forth to self using mac version of gpg, but trouble across platform to
>> another user with windows version of gnu gpg. Their app correctly  
>> received
>> my key, but the mac Mail.app on my computer appears to be having  
>> difficulty
>> with their key. I can't seem to import the key when using GPG Keychain
>> Access app on my mac. the file I receive from the windows pubkey  
>> export is
>> listed as "0x0C0D89A8.asc.pgp" -- even though when I export it on the
>> windows machine it appears to be a text file with a .txt extension  
>> on the
>> windows end before mailing it.
> 
> What you're trying to do should work just fine.  I don't see anything  
> wrong with your procedure.  The file renaming dance is a common side  
> effect of mail handling, but all the names you give should work the  
> same.  So, I'm puzzled.  Let me ask more questions.
> 
> You say "I can't seem to import the key."  What does that mean?  Do  
> you get error messages?
> 
> Open a Terminal window and type "head 0x0C0D89A8.asc.pgp".  The  
> format of this file is pretty rigid; does it look like this?
> 
> The first line should be "-----BEGIN PGP PUBLIC KEY BLOCK-----".   
> Well, that doesn't have to be the very first line, but it's the first  
> line that gpg cares about.  There must be exactly five dashes at the  
> beginning and end of the line.  The beginning dashes must begin at  
> the very beginning of the line, no spaces first or "> " things or  
> anything else.  The ending dashes must end at the end of the line,  
> nothing after them.
> 
> The second line is probably something like "Version: GnuPG v1.4.6  
> (Darwin)".  The actual version info may differ.  actually, since you  
> got this from your windows-using friend, it almost *certainly* won't  
> say "Darwin", because that means "Macintosh" ;-)  But something like  
> this, anyway.
> 
> There may be a third line, something like this: "Comment: PGP- 
> encrypted email preferred"  The comment line is optional, so it may  
> not be there.  If it is there, it might say pretty much anything at  
> all - it's just a ... well ... comment ... provided your friend.
> 
> The next line (third or fourth, depending on whether there was a  
> comment) should be blank, empty, nothing there.
> 
> After that come a bunch of lines containing unreadable goop, like  
> "mQCNAyyg8RgAAAEEALN78k0ovUHn119cm8enD4oaDXWgImkSXPYNJFfo9VFeH14B"
> 
> 
> Does it look like that?  I'm guessing it does not, or it would have  
> worked for you.  So, in what way is it different from that?  Tell me  
> how it's different, and maybe I can tell you how to fix it up,  
> possibly how it got messed up in the first place, and hopefully how  
> to avoid the problem the next time.
> 
> -==-
> Jack Repenning
> Chief Technology Officer
> CollabNet, Inc.
> 8000 Marina Boulevard, Suite 600
> Brisbane, California 94005
> office: +1 650.228.2562
> mobile: +1 408.835.8090
> raindance: +1 877.326.2337, x844.7461
> aim: jackrepenning
> skype: jrepenning
> 
> 
> 
> 
> 
>  
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Macgpg-users mailing list
> Mac...@li...
> https://lists.sourceforge.net/lists/listinfo/macgpg-users
> 
> 

-- 
View this message in context: http://www.nabble.com/trouble-figuring-out-how-to-import-a-public-key-from-windows-to-mac-gnugpg-tf3571613.html#a9986663
Sent from the macgpg-users mailing list archive at Nabble.com.