Topic: Question about New Gmail Interface and Encrypt and Sign Options

Excuse my ignorance, but things are not working the way I expect them to.

Using the new gmail interface, I select sign and encrypt.

After sending the mail, I see the ciphertext, but also two attachments at the bottom called:

noname
encrypted.asc

I suppose this isnt the exact behaivor I was looking for.  What I was expecting was for the document to be clearsigned, and then encrypted leaving a result letter with no attachments.  Am I wrong about this?  And isnt the default action of sign supposed to be clearsign in the first place?

Re: Question about New Gmail Interface and Encrypt and Sign Options

Reading more up on the subject - I actually prefer clearsign to sign, however that may just be me.  Is there a way an option can be added to firegpg, to differentiate what sign means?  Meaning either generating a totally binary output or ascii output (if the -a option is used -- which I assume is the default behaivor), or an option which generates a clear signature where the data is left to be human readable and the signature is appended in ascii format.

Re: Question about New Gmail Interface and Encrypt and Sign Options

Sign+Encrypt = Normal sign != clearsign. Because it's encrypted too wink.

The two attachments are a result of OpenPGP/Mime standard :
- noname is the opengpg's version
- Encrytped.asc is not your attachment but the encrypted text (with your attachment as a subpart)

Re: Question about New Gmail Interface and Encrypt and Sign Options

I must stress I am addressing the situation where sign is the only option chosen -- not sign+encrypt.  If I choose sign only (no encryption), shouldn't it default to clearsign?

As I read the man page:

Sign = Letter signature which may contain binary code
Sign + Ascii = Letter Signature which is purely ascii armored
Clearsign = Append the Signature to the Original letter but keep the contents of the letter legible

So if I just wanted to sign a letter -- but not encrypt it, wouldn't I want to just clearsign the letter?  This would keep the letter readable by those who did not use gpg/pgp.  If Im not mistaken I believe enigmail works this way by clearsigning the document.  I'm asking only for the situation where sign is chosen, not sign+encrypted.  But wouldn't it be possible to clearsign and encrypt too, although I guess it really wouldn't matter in this case. 

From the gpg man pages:
Commands to select the type of operation

     --sign

     -s     Make a signature. This command may be  combined  with  --encrypt
            (for  a signed and encrypted message), --symmetric (for a signed
            and symmetrically encrypted message), or --encrypt and --symmet-
            ric  together  (for a signed message that may be decrypted via a
            secret key or a passphrase).

     --clearsign
            Make a clear text signature. The content in a clear text  signa-
            ture  is readable without any special software. OpenPGP software
            is only needed to verify the signature.  Clear  text  signatures
            may  modify end-of-line whitespace for platform independence and
            are not intended to be reversible.

     --detach-sign

     -b     Make a detached signature.

Wouldn't clear sign be the default preference because in this case only OpenGPG is needed to verify the signature if sign is only chosen as an option?


Can you explain the three parts of the letter specifically with the mechanism currently in place.
The contents of the letter represent = ?
Noname = ?
Encrypted.asc = ?

Should all these parts be appended if I just elect to use sign?

Re: Question about New Gmail Interface and Encrypt and Sign Options

About Noname and encrypted: http://www.ietf.org/rfc/rfc3156.txt

Just selecting sign in gmail create a clearsign, in attachments, as rfc linked before says. It's already what you want. Non pgp/gpg users just seen an additional attachments, who is a clear sign, letter is still readable. Without 'noise' of the sign.

I don't understand your problem.

Re: Question about New Gmail Interface and Encrypt and Sign Options

Why do you want a clearsigned attachment?

Re: Question about New Gmail Interface and Encrypt and Sign Options

Why do you want <a> to create link in html ?

It's a standart, point. Same for clearsigned attachement wink