1

(1 replies, posted in Bugs & problems)

On the "general web" FireGPG hides crypto noise and gives me the option to verify content.  On GMail, it auto verifies (nice) but does not hide the crypto noise.  Is there a reason for this?

2

(3 replies, posted in Requests)

@the_glu there's no real error console in prism I don't think, I'll look into it though if I can

3

(3 replies, posted in Bugs & problems)

If you had a link to a proper bugtracker it might have been easier to find.  Searches on the forums turned up people talking about stuff, but no definitive answer.  You really should list that MME is not supported somewhere on the main site.

4

(3 replies, posted in Bugs & problems)

I am using mutt and gpg from Ubuntu Linux.  When I send to people using Thunderbird they can verify my signature fine.  Other mutt users can as well.  I can always verify my own signature in mutt if I send a signed email to myself.  If I send an inline-signed email to myself, I can verify it from the Gmail interface with FireGPG - but if I use the standard MIME-based signing, it fails.  Does FireGPG not support MIME signing?  If this is the case it should be so documented and it should not try to verify MIME-signatures (because it gives red text and says the signature is bad when it is in fact good.

5

(3 replies, posted in Requests)

I would really love to see this extension work in Prism.  I can get it to run, but none of the functionality shows up.  Many people I know are using Prism for Gmail SSB now.