Send encrypted mail
Closed, DuplicatePublic

Description

We want to be able to send encrypted mails (ideally oppotunistically).
This involves:

  • Selecting a key for each recepient to encrypt to (a default could be taken from the addressbook?)
  • Encrypting the mail and assembling the encrypted parts (in case of multiple)

Related Objects

StatusAssignedTask
DuplicateNone
DuplicateNone
cmollekopf moved this task from Backlog to Milestore: MailClient on the Kube board.
mbohlender moved this task from Milestore: MailClient to 0.2 on the Kube board.Nov 8 2016, 1:27 PM
mbohlender edited projects, added Kube (0.2); removed Kube.
cmollekopf moved this task from 0.2 to Backlog on the Kube board.Feb 21 2017, 12:43 PM
cmollekopf edited projects, added Kube; removed Kube (0.2).

For key resolution see messagelib/messagecomposer/src/composer/keyresolver.h
For encryption/signing see messagelib/messagecomposer/job/*encrypt*

What needs to happen is roughly this:

  • Select and encryption method; available are pgp inline and pgpgmime as well as smime opaque and and smime. pgpmime is a sane default choice I think, the rest could be ignored for now.
  • Try to find keys for all recipients and show in the composer on the recpient delegate if a key could not be found.
  • If keys for all recipients could be found (otherwise just refuse to send), then encrypt/sign as required and send the message as usual.
cmollekopf moved this task from Backlog to 0.5 on the Kube board.Aug 1 2017, 3:39 AM
cmollekopf edited projects, added Kube (0.5); removed Kube.

key lookup: email address -> fingerprint -> key

The fingerprint could alternatively be configurable to select a specific key to use.

cmollekopf moved this task from Backlog to In Progress on the Kube (0.5) board.Nov 23 2017, 4:20 PM
cmollekopf closed this task as a duplicate of T6992: Composer: Send encrypted mails.

For key resolution see messagelib/messagecomposer/src/composer/keyresolver.h
For encryption/signing see messagelib/messagecomposer/job/*encrypt*

What needs to happen is roughly this:

Select and encryption method; available are pgp inline and pgpgmime as well as smime opaque and and smime. pgpmime is a sane default choice I think, the rest could be ignored for now.
Try to find keys for all recipients and show in the composer on recruitment past questions the recpient delegate if a key could not be found on americainfoblog
If keys for all recipients could be found (otherwise just refuse to send), then encrypt/sign as required and send the message as usual.

For key resolution see messagelib/messagecomposer/src/composer/keyresolver.h
For encryption/signing see messagelib/messagecomposer/job/*encrypt* also on best deals and this is nigerian immigration service recruitment plus latest trending news in america