Problems with 0.7.2

I will try :

> As said on the Blog here the full message.

???

> Hey thanks, this one works, but i have a little problem. I can not read base64

Ok.

> If i encrypt some text (in html mode or plain text mode) the decrypted text looks like that:

Yes, it's normal. But FireGPG decrypt mail and parse base64.

> And for some reason i dont know is the signature not recognized. "No signature found in this email."
> This is for the old Interface if the signature is in a file. In the new interface this is every time not recognized.

Old interface is old, and don't support sign in files.

> But in Signed + Encypted mail the decrypt window shows that the Signature was found and valid

???

> The old interface make it even worse. It says "The first signature of this email is not valid." if it is an inline signature.

She shouldn't.

> I found a "Decrypt this email" Link in the old interface, why is this one not in the new interface?

Because decryption is automatic (except if you check 'Old old decryption behaviour in option)

> The options window is to large for 800 pix high displays, like in my laptop (1280x800).

Resize it

> But to be not to negative the sign, encrypt, inline button are working as expected
Yhira °o°

> If I encrypt a message and use the rightclick menue -> decrypt than I get only base64 encoded text.

Normal.

> If I sign an mail, with the new Gmail interface, than the signature.asc isn't recognized. "No signature found in this email."

In the old interface ? Normal. If it's with the new there is a problem.

> If it is an inline signature only the old Gmail interface recognize it. But than firegpg says only "The first signature of this email is not valid."

Inline signs fail most of time. Use openpgp/mime (=not inline) to be sure it's works.

> If the mail was Signed and Encrypted and i decrypt it, the decrypt window say "Valid signature from ...". But the mail content is base64 encoded.

Normal.

> Why have I to use the rightclick menue in the new Gmail interface to decrypt a message if the old Gmail interface has an direct link?

Anormal. New gmail interface autodecrypt mail. If they not, (and dosen't reconize sign) there is a problem.

> And last: the FirePGP options window is more than 800 pix high thats to much.

Resize it .

----

Do you have any error, related to firegpg, when you read a mail ?

In the new Interface

So it is, i think the attached "Noname" file is part of the autodecryption, but it does not decrypt

I tryed, but it is not possible, maybe this come from my custom windows skin.

No errors, just warnings:
Warning: The 'charCode' property of a keydown event should not be used. The value is meaningless.
Source File: https://mail.google.com/mail/?ui=2& … gpcgurkovy
Line: 0

I forgot to say all Tests with FF3.1b3pre nightly of 25.1.

I have had problems with the FF3.1b2 too, thats why i use FF3.1b3pre
Its hiding here:
http://ftp.mozilla.org/pub/mozilla.org/ … lla-1.9.1/

Ok, i think i can reuse this thread

Frist thanks for the tip with third party cookies, now firepgp works with FF3.1b3pre

Current Problem:
FF alerts with:
"You have requested an encrypted page that contains some unencrypted information. Information that you see or enter on this page could easily be read by a third party."

Every time, when i compose/reply a mail (when the FireGPG controls are shown).

FF self do a very bad job on this issue, cause it only alerts an does not block such content (even an IE 6.0 asks you if it should load unsave content on a https site). But the actual problem of this message comes from the html, maybe from a missing https somewhere.

This type of alert message have i only found in the 3.1 Version of FF, the 3.0 takes such unsave content without a doubt.

Just after the bunch of code between the Subject Line and attach File line forms into FireGPG Controls. (After this is cached the controls are not shown as code again in the same Session). The problem is still there. Every time, when the FireGPG Controls are shown then FF find that some encryption are broken.

Page info says: Connection Partially Encrypted

It's a firefox3.1 problem.