Topic: Confused if non-inline sign worked

Hi, I am new to FireGPG and using version 0.7 with Firefox 3.0.5.

I want to be able to sign my email, without encrypt. I am able to do inline sign by clicking both the "Sign" and "Inline" icon. When doing this, when I click 'Send' I am asked for private-key passphrase, and it works.

However if I only click the "Sign" icon, nothing seems to happen .. I am not asked for passphrase and the received email has no inline or attached signature. Is it possible to use FireGPG to attach the signature like signature.asc?

Thank you for producing this software!!

Re: Confused if non-inline sign worked

Hi,

Last release is the 0.7.2, please upgrade first and check if it's happen again wink

Regards,

Re: Confused if non-inline sign worked

Hi, thank you for the quick reply!!
I will try it and get back smile

Re: Confused if non-inline sign worked

same here with 0.7.2
how can i help?

Re: Confused if non-inline sign worked

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just updated to 0.7.2 and can report this same problem still exists for me. I can click [Sign] and [Inline] and am asked for the passphrase for my private key. The inline signature is generated and mail sent normally. However, like the other user, if I choose only [Sign] (this generates a PGP/MIME formatted signature?), when I next push either [Send] button, the mail is sent immediately w/o a signature of any kind, and no prompt for my key's passphrase.

(I understand this must be a very difficult operation, as it appears to achieve generation of a PGP/MIME message, you have to lift the whole mail out of the Gmail interface, generate the proper formatting yourself, and send it internally via Gmail's SMTP facility. Seems like plenty could go wrong with this. You're very vulnerable to Gmail site and interface changes. While FireGPG is very usable and has accomplished much, it seems to me that perfect ongoing Gmail integration would require close, continual support from Google.

In spite of those difficulties, FireGPG is very valuable as an easy interface to GnuPG from within Firefox, making use of GnuPG practical in almost any web application.

Thanks for your efforts!)

- --
[You may obtain my PGP key for signature verification below:]
http://andrewskretvedt.blogspot.com/200 … c-key.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.2)

iD8DBQFJfebwRTNjCmtFEDURAvw0AJ4xkXIPxkLTawYP/843sIYpptd4pACeO5mG
q4bTromCkjVl2Fvz2EfypCk=
=3Gdi
-----END PGP SIGNATURE-----

Re: Confused if non-inline sign worked

Both send buttons ? Errors in firefox's console ?

Re: Confused if non-inline sign worked

yes both buttons (before and after the message).

For a short file I can see the message on the top - "sending with firegpg"

there are errors on firefox console.

Error: Permission denied to create wrapper for object of class UnnamedClass
Source File: https://mail.google.com/mail/?ui=2& … f1i2HehpJE
Line: 644
Error: Permission denied to create wrapper for object of class UnnamedClass
Source File: https://mail.google.com/mail/?ui=2& … f1i2HehpJE
Line: 644

the message is not MIME encoded.
==============================================
MIME-Version: 1.0
Received: by 10.143.32.2 with HTTP; Mon, 26 Jan 2009 10:46:39 -0800 (PST)
Date: Mon, 26 Jan 2009 18:46:39 +0000
Delivered-To:
Message-ID: <383357750901261046u42734455w70cd25ae79a0b9b8@mail.gmail.com>
Subject: bbbb
From: =?ISO-8859-2?Q?Mateusz_
To: Mateusz
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

bbbbbbb

==============================================

on another machine I still have 0.7 which is working fine (this problem does not appear to happen).


PS Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5

$ gpg --version
gpg (GnuPG) 1.4.9
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2



HTH

Last edited by blahu77 (2009-01-26 20:02:03)

Re: Confused if non-inline sign worked

Ok, another error ? (Install console² addon if it's possible)

Update your another machine and test is the problem occur too, in a new firefox's profile if you want to keep the 0.7

I don't need mime message as there are not signed wink

Thanks

Re: Confused if non-inline sign worked

I did update the other machine, new profile with console^2



Error: Permission denied to create wrapper for object of class UnnamedClass
Source file: https://mail.google.com/mail/?ui=2& … f1i2HehpJE
Line: 644
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: aRequest is null
Source file: chrome://firegpg/content/cgmail.js
Line: 82
----------
Error: Permission denied to create wrapper for object of class UnnamedClass
Source file: https://mail.google.com/mail/?ui=2& … f1i2HehpJE
Line: 644
----------
Error: line is undefined
Source file: chrome://firegpg/content/mime.js
Line: 2251
----------
Error: Permission denied to create wrapper for object of class UnnamedClass
Source file: https://mail.google.com/mail/?ui=2& … f1i2HehpJE
Line: 644
----------
Error: FireGPG-debug: [cgmail.listenerLoad][Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMLocation.host]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: XPCSafeJSObjectWrapper.cpp :: anonymous :: line 445"  data: no]
Source file: chrome://firegpg/content/misc.js
Line: 133
----------
Failed to load XPCOM component: /usr/lib/xulrunner-1.9.0.5/components/pyabout.py
----------
Failed to load XPCOM component: /usr/lib/xulrunner-1.9.0.5/components/libpyloader.so


HTH

Last edited by blahu77 (2009-01-26 20:34:02)

Re: Confused if non-inline sign worked

Ok, here we have error wink

You another pc works with the update ?

Re: Confused if non-inline sign worked

the_glu wrote:

Ok, here we have error wink

You another pc works with the update ?

no, it doesnt ask for password and it doesnt sign

Re: Confused if non-inline sign worked

Ok.

Can I have a contact with you by IM ? I haven't the problem and I need a tester wink

Re: Confused if non-inline sign worked

Ok, so I fix the problem in svn, and there is a workaround for people having the problem :

In options, set the field to force the form value (last input box / gmail tab) to something like this : Your Name <your@email>

FireGPG seem to have a problem to find the form values...

Thanks to blahu77 for his help.

14

Re: Confused if non-inline sign worked

Sorry, I went to work, just got home and tried this.
With version 0.7.2, I got the same error, and also saw in Javascript console:

Error: Permission denied to create wrapper for object of class UnnamedClass

The best is, the_glu's fix works!! I am able to send emails with signature.asc now. You're so fast, thank you so much!

Re: Confused if non-inline sign worked

Thank God, someone else had this issue. I thought I was going crazy until you mentioned 0.7 and 0.7.2

I have 0.7 on one machine working fine, but my other one (with 0.7.2) stopped sending attached signatures or encrypting messages unless you send them as inline.

For example, if I enable the signature and disable the inline icon, the message is sent without any sigantures.

If I enable encryption and disable the inline icon, the message is also sent without any encryption.

It's only working with the inline icon enabled.

I hope this is easily fixed. I really love FireGPG. It's part of my essential Firefox tools.

Congrats on the awsome project!

Julio

Re: Confused if non-inline sign worked

@juliohm : read my message...

In options, set the field to force the form value (last input box / gmail tab) to something like this : Your Name <your@email>

Re: Confused if non-inline sign worked

the_glu wrote:

@juliohm : read my message...

In options, set the field to force the form value (last input box / gmail tab) to something like this : Your Name <your@email>

Sorry, my bad. But still no luck.

Here are the Firefox console with errors and my current settings.

http://juliohm.com.br/screenshot.5.jpeg

http://juliohm.com.br/screenshot.6.jpeg

While sending the message I can see the yellow alert on top "FireGPG is sending your mail...", but after sometime it goes away and this error shows up on the Firefox console. The message is never sent.

Last edited by juliohm (2009-01-27 13:52:42)

Re: Confused if non-inline sign worked

Ok, it's an another error...

Your firewall (at work | from your provider) autorisze connexions to smtp.gmail.com ?

Re: Confused if non-inline sign worked

I was having the same problem as posts above.
Problem was that opendns was blocking smtp.gmail.com
Onced allowed, sign and encryption worked.

Thanks for FireGPG

Re: Confused if non-inline sign worked

the_glu wrote:

Ok, it's an another error...

Your firewall (at work | from your provider) autorisze connexions to smtp.gmail.com ?

Yes, I am behind a corporate firewall, which requires my domain user/password for access. I can start imagining how this works in the source code. I guess it won't work on some scenarios, like mine. This might already be in the wishlist, but using Firefox's proxy settings might be a good idea in the future smile

Thanks for the help!