S/MIME signing and verifying by default in Kmail
In large corporations where e-mail encryption and signing are used, S/MIME is more common than PGP. The current complexity associated with getting S/MIME working with Kmail limits the appeal of Kubuntu in these types of organizations. Currently some of the packages required are in Universe.
The action for this spec is to define the minimum application set required for S/MIME sending and verification, file Main Inclusion Requests as necessary, verify that the configurations shipped by Kubuntu support S/MIME, and update documentation.
Blueprint information
- Status:
- Complete
- Approver:
- Jonathan Riddell
- Priority:
- Low
- Drafter:
- Scott Kitterman
- Direction:
- Needs approval
- Assignee:
- Scott Kitterman
- Definition:
- Approved
- Series goal:
- Proposed for gutsy
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Scott Kitterman
- Completed by
- Scott Kitterman
Whiteboard
I have S/MIME working with Kmail. Working to develop the correct minimum change set to support the feature.
MIR for pinentry-qt is approved. Pinentry now in Main.
MIR for gnupg-agent is not needed (source package already in Main).
kdepim changes published:
Add gpgsm to kmail depends
Move gunpg-agent and pinentry-qt from suggests to depends
Bump kleopatra from suggests to recommends
Add use-agent to (probably non-existent) ~/.gnupg/gpg.conf is the remaining issue. Mail asking for doing it by default sent to devel-discuss.
It turns out the non-existant part was another bug. Fix for that and the conf changes is uploaded in gnupg 1.4.6-2ubuntu3.
Is gnupg sufficient or does gnupg2 need to be a dependency? - gnupg is sufficient.
Changes documented in the relevant community docs (official docs don't mention it).
DONE!
Note: Works in Dapper with KDE 3.5.5 packages with use-agent added.
Note: Marked approved as this spec is part of the approved https:/
