Home → Stable →

GPG mail uses sMime but won't allow existing sMime encryption

• Edit

Steve

17 Nov, 2011 08:56 PM

It seems if I turn on PGP in system preferences that I then can't use any of my existing certificates but only the PGP ones.
It's a complete either or proposition.
Previously I could use existing sMime certificates and then additionally layer PGP inside of them as well.

I could choose 1 or the other or both on the mail screen.
Now if I enable sMime for composition I can't use any of my existing non PGP certificates EVER.
This is not good...

1. Support Staff 1 Posted by Luke Le on 17 Nov, 2011 09:00 PM

   

   Hi Steve,

   it's true, at the moment GPGMail 2.0 is not capable of coexisting peacefully with S/MIME. It's an either/or situation you described.
   This is due to the fact the 2.0 version is a complete rewrite and the version you're running still an alpha version.
   The final version will work seamlessly with S/MIME.

   • Edit

2. 2 Posted by Stephen Clayton on 17 Nov, 2011 09:05 PM

   

   Luke,

   PuuRrrfect!!!
   Just wanted be sure I wasn't doing something stupid... :)
   Love what you're doing by the way. I know it's a huge effort.
   It is appreciated.

   I still can't believe Apple is not making this easier.

   Steve

   • smime.p7s 1.75 KB
   • Edit

3. Support Staff 3 Posted by Luke Le on 17 Nov, 2011 09:08 PM

   

   Thanks, we're really trying our best, it only takes time as the team
   is very very small.
   Apple sure doesn't make it easy, but the new version of GPGMail will be very nice and easy to use and it should be easier to update it along with system updates, so it's all worth it.

   Have fun, and just ask when you run into problems.

   • Edit

4. Luke Le closed this discussion on 17 Nov, 2011 09:08 PM.

5. Luke Le re-opened this discussion on 28 Feb, 2012 03:48 PM

6. Support Staff 4 Posted by Luke Le on 28 Feb, 2012 03:48 PM

   

   Hi Steve,

   as promised, we've worked on better S/MIME | OpenPGP switching.
   It would be great if you could test the current dev version:

   http://nightly.gpgtools.org/GPGMail-trunk.dmg

   And let us know what you think.
   Be aware that this version could show other issues, so use it with caution.

   Thanks for the help

   • Edit

7. 5 Posted by Henrich on 02 Mar, 2012 11:09 AM

   

   Hi Luke,

   your doing a great job!
   Tested it ... works fine !!!!
   Just a minor:
   Current Workflow was a little unintuitive, as follows:
   1) enabled Signature by Star Button in Mail.app()
   2) Got blue SMIME (nice)
   3) Switched to PGP (got gray PGP)
   4) AGAIN !!! had to enable Signature by Star Button in Mail.app()
   5) Got green PGP (nice)

   So the re-enabling is a little unintuitve, as I already indicated that I want it signed :-)
   But, nevertheless GREAT WORK !!!

   • Edit

8. Support Staff 6 Posted by Luke Le on 02 Mar, 2012 11:13 AM

   

   Hi Henrich,

   the next release will keep the star button active, if so chosen before, BUT
   we've added a "intelligent" way of determining what security method, sign status, and encrypt status should be set for new messages.
   The method works by tracking the security method, sign status, encrypt status used for each method and making the decision based on that information for you.

   So if you signed more often from a sender address to a recipient, than not sign, the next message to the recipient(s) will be signed as well.
   If you have S/MIME and PGP for a key and you've used one of the two methods more often, based on recipients and sender, the method is chosen which was used more often.
   And so on.
   We're still working out some kinks but this should really improve your workflow and in the best case you should have to press either of those buttons again.

   • Edit

9. 7 Posted by Henrich C. Pöhl... on 02 Mar, 2012 01:35 PM

   

   Hi Luke,

   as much as I like automatic behaviour, and as much as this would increase the usage of signature on the Internet,
   could you include a command line that deactivates the automatic decision ;-)
   By the way, what kind of statistics (sender, receiver, used enc) do you need to store locally on the machine, and is there way of prohibiting this background logging, at the cost of loosing the automation of course?

   Thanks again for the great PlugIn.

   Best Regards,
   Henrich

   • Edit

10. Support Staff 8 Posted by Luke Le on 02 Mar, 2012 01:55 PM

    

    Hi Henrich,

    that's exactly what we plan to do if more people request it.
    Please add a reply to this ticket:
    http://gpgtools.lighthouseapp.com/projects/65764/tickets/457-if-nee...

    I know tracking and statistics are bad words with all the privacy issues being brought to light, but don't worry, we're saving the email address in a hashed way and other than that only the date and sign/no-sign, encrypt/no-encrypt status and security method.
    There should not be a need to prohibit this.
    If you still feel disabling that should be possible, please add that suggestion to the ticket mentioned above.

    2.0 is being released soon, as this one is gonna be a hit :D

    • Edit

11. Alex closed this discussion on 04 Mar, 2012 09:57 PM.