summaryrefslogtreecommitdiffstats
path: root/framework/src
Commit message (Collapse)AuthorAge
...
* Insert spacesChristian Mollekopf2018-05-07
|
* Separate multipart/related formatterChristian Mollekopf2018-05-07
|
* Removed unnecessary includeChristian Mollekopf2018-05-07
|
* Made structure available in debug viewChristian Mollekopf2018-05-07
|
* Avoid running a live query during fulltext search.Christian Mollekopf2018-05-07
| | | | We don't currently filter incoming items properly.
* Port to gpgme only.Christian Mollekopf2018-05-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | QGpgme and Gpgmepp are not readily available, the cmake files buggy, the buildsystem horrendous and generally just difficult to build on windows. Given that all they are is a wrapper around gpgme, we're better of without all the indirections. What we loose is: * QGpgme moved the work to separate threads (but we then blocked anyways), something that we can just do in our own code should we want to. * QGpgme has a function to prettify dn's that was used to show the signer. Also something we could bring back should we need to (don't know where it is useful atm.) Ported messagepart to gpgme Almost there Moved the crypto bits to a separate file All gpg code is in one place. All tests passing Use error codes Cleanup
* And another missing exportChristian Mollekopf2018-05-03
|
* Missing exportChristian Mollekopf2018-05-03
|
* On windows the exports are mandatoryChristian Mollekopf2018-05-03
|
* cmake cleanupChristian Mollekopf2018-05-03
|
* Less direct tinkering with compiler flagsChristian Mollekopf2018-05-03
|
* Windows compatChristian Mollekopf2018-05-02
|
* No need to install a shared library if we only use it internally.Christian Mollekopf2018-05-02
| | | | | And that keeps us from having to export stuff from the library for windows to work.
* windows compatChristian Mollekopf2018-05-02
|
* No need to find those again.Christian Mollekopf2018-05-02
|
* More explicit linking against gpgmeppChristian Mollekopf2018-04-27
|
* More explicit linking against gpgmeppChristian Mollekopf2018-04-27
|
* That's not how you write gpgmeppChristian Mollekopf2018-04-27
|
* Link explicitly against gpgmeppChristian Mollekopf2018-04-27
|
* Remove showOnlyOneMimepart from the public interface.Christian Mollekopf2018-04-26
| | | | That makes it much more obvious where we actually rely on it.
* Removed empty formatterChristian Mollekopf2018-04-26
|
* Removed some more unnecessary includesChristian Mollekopf2018-04-26
|
* Another qgpgme dependency goneChristian Mollekopf2018-04-26
|
* Less gpgme in the interfacesChristian Mollekopf2018-04-26
|
* No more direct GpgMe usage in the interfaces.Christian Mollekopf2018-04-26
|
* Collect gpgme usagesChristian Mollekopf2018-04-26
|
* Starting to isolate our gpgme++ usage.Christian Mollekopf2018-04-25
| | | | So we can destroy it.
* Fixed the case where we have plaintext inside the encrypted part.Christian Mollekopf2018-04-25
| | | | This is triggered when we have encrypted+signed inline parts.
* CleanupChristian Mollekopf2018-04-25
|
* Deal with rfc822 header partsChristian Mollekopf2018-04-25
| | | | As inserted by autocrypt enabled clients.
* Implement PeriodDayEventModelRémi Nicole2018-04-17
| | | | | | | | | | | | | | | | | | Summary: Implements a model to load events. When finished, should fix T8225 TODO: - Use the parent / children model in qml, instead of relying on the ".events" attribute (using DelegateModel I think) Reviewers: cmollekopf Tags: #kube Maniphest Tasks: T8225 Differential Revision: https://phabricator.kde.org/D12089
* Fixed warningsChristian Mollekopf2018-04-09
|
* Match auto css propertiesChristian Mollekopf2018-04-05
|
* The resource has been renamedChristian Mollekopf2018-03-30
|
* Make sure we don't end up with any CRLF'sChristian Mollekopf2018-03-23
|
* An extension mechanism load qml files at generic extension points.Christian Mollekopf2018-03-23
| | | | and forward the email via an extension api.
* CleanupChristian Mollekopf2018-03-23
|
* cleanup contactcontrollerMichael Bohlender2018-03-22
|
* use KubeListController in person pageMichael Bohlender2018-03-22
|
* Require sink 0.6.0Christian Mollekopf2018-03-20
|
* Avoid displaying empty contacts by falling back to the FNChristian Mollekopf2018-03-20
|
* Avoid warning about using c++14 extensions.Christian Mollekopf2018-03-20
|
* No Q_ASSERT in constexpr for nowChristian Mollekopf2018-03-13
|
* Fix expected-related OS X build failureRémi Nicole2018-03-12
| | | | | | | | | | | | | | | | | Summary: I couldn't manage to build the project on my OS X machine, so the fix currently hasn't been tested. Should fix T8185 Test Plan: Ask Christian Mollekopf to test the fix on his OS X machine Reviewers: cmollekopf Tags: #kube Maniphest Tasks: T8185 Differential Revision: https://phabricator.kde.org/D11265
* We started using c++14 in errors.hChristian Mollekopf2018-03-09
| | | | It's widely supported by now, so let's just use it.
* Fixed buildChristian Mollekopf2018-03-09
|
* Automatic key import / export + Expected monadRémi Nicole2018-03-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: There are many things going on here (perhaps a bit much for a single patch): - When an attachment is of mime type "application/pgp-keys", a button is added to import the key to GPG - When sending a mail and crypto is enabled (encryption, signing or both), the public key of the first private key found is sent as an un-encrypted attachment (T6994) - The `mailcrypto.{h,cpp}` was, for the most part, rewritten - Introduction of the expected monad, inspired by what was proposed for C++ [here](https://isocpp.org/files/papers/n4015.pdf), but not at all a strict implementation of this specification. We may want to add some more features of this standard later. The rationale for some of the choices: - I found mailcrypto a bit hard to edit to add new features, and a great part was commented code to prepare for the support the SMIME crypto format, which would (in my current knowledge) not be used for sending emails. - One thing I found that may be missing in the code base was a standardized way of handling errors in C++ code. Since exceptions are disabled I think that the functional way is the way to go. After some research I found the Expected monad / tagged union / sum type, which seemed to suit the problem particularly well. In the long run, I hope we would move the entire code base to use `Expected` to indicate if a function might fail. Of course every choice made here is to be considered as a proposition for doing things / RFC, critics wholeheartedly accepted. Reviewers: cmollekopf Tags: #kube Maniphest Tasks: T6994, T8147, T6995 Differential Revision: https://phabricator.kde.org/D11158
* Support encrypted mails forwardingRémi Nicole2018-03-08
| | | | | | | | | | | | | | | | | | | | Summary: Some notes: - What we do is: if the mail is encrypted, decrypt it and copy its content into a new message (with plaintext, html and attachments, if any), and use this message as attachment for forwarding - The `isEncrypted` function from KMime doesn't seem to detect every kind of encrypted mails. AFAIK this structure is not detected: - `multipart/mixed` - `text/plain` - `application/pgp-encrypted` (attachement, named "ATT00001") - `application/octet-stream` (attachment named "encrypted.asc") Reviewers: cmollekopf Tags: PHID-PROJ-6npnfcmppynqynn7slmv Maniphest Tasks: T8112, T7024 Differential Revision: https://phabricator.kde.org/D10966
* Fixed build on macChristian Mollekopf2018-03-05
|
* Revert "Support encrypted mails forwarding"Christian Mollekopf2018-03-02
| | | | | | This reverts commit f28ec43dca5b2915deb69d54fb942ddf1303f48c. That was pushed by accident.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-19 11:02:41 +0000