summaryrefslogtreecommitdiff
path: root/tests/integration
AgeCommit message (Collapse)Author
2017-12-03[refactor] rename key extension to expirationTulio Casagrande
This changes reflect python-gnupg naming. With @aarni
2017-12-03[bug] fix expected new_expiry_dateTulio Casagrande
Previously, new_expiry_date was calculated by the key creation date + 1 week, but the proper behavior is today + 1 week, accordingly with gpg behavior.
2017-12-03[feat] expired public key are remotely fetched if expiredNavaL
- private key is not allowed to be fetched remotely - fetch_remote needs to be specifically set - if a new key is fetched (ie different KeyID), the validation rule applies
2017-12-03[bug] sign_used flag is reset for all public keys when the key expiration ↵NavaL
date is extended - this is required so that the key is re-attached to the first outgoing email to all users who already have the expired key.
2017-12-03[feat] expired public key are remotely fetched if expiredNavaL
- private key is not allowed to be fetched remotely - fetch_remote needs to be specifically set - if a new key is fetched (ie different KeyID), the validation rule applies
2017-12-03[bug] decryption will be tried for all inactive keysNavaL
2017-12-03[feat] decryption interoperability, when the current key pairNavaL
is renewed - there is only one private inactive key that is the key expiring last among all inactive keys - if there is an inactive key, decryption with it, is tried if it fails with the current active key.
2017-12-03[feat] reset sign_used flag after regenerating key pairNavaL
- this flag is used by leap.mail to attach the new key
2017-12-03[feat] first phase of key regenerationNavaL
- if current key pair is expired, it'll be extended for a day first - new key pair will be signed by the old key
2017-12-03[feat] add key expiry date extension in keymanagerNavaL
- extends key pair (unlocked from soledad) - extension period is counted from key creation date
2017-10-26[test] update imap flag listRuben Pollan
2017-10-26[bug] strip leap headers before processing the icnomming mailsRuben Pollan
- Resolves: #9030
2017-10-26[feat] add fetch key by fingerprint to keymanagerRuben Pollan
- Resolves: #9023
2017-10-26[bug] make nicknym return key dataRuben Pollan
There was a mismatch on the return values of Nicknym class and the expectations. As most of the code was expecting an OpenPGPKey, but it was returning the json as it came from the nickserver. Now is just returning the key data.
2017-10-06[feat] use bonafide Provider object as a singletonRuben Pollan
There was common situations where two provider instances where running in parallel. And was creating weird errors (like getting wrong api_uri) because the bootstrap deferreds were global but the Provider objects not. I don't like much singletons, but I think now is simpler than before. - Resolves: #9073
2017-09-13[bug] send UIDNEXT on selectKali Kaneko
node-mail chokes if we don't.
2017-08-25[bug] replace content-type after removing the signatureRuben Pollan
- Resolves: #9003
2017-07-18[test] ca_cert_path can not be an empty stringRuben Pollan
2017-06-12[feat] push private key updates into nicknymRuben Pollan
Deal as well with sending key if key is outdated in the providers nicknym. - Resolves: #8819, #8832
2017-06-05[test] validate the CA cert fingerprint checkRuben Pollan
2017-06-05[bug] fail bonafide bootstrap for self sign certsRuben Pollan
- Resolves: #8881
2017-05-24[tests] fix testsKali Kaneko (leap communications)
2017-05-16[tests] remove listener testKali Kaneko (leap communications)
I've removed the add_listener method because it's not used anywhere.
2017-05-16[bug] fix notification for incoming mail with several listeners registeredKali Kaneko (leap communications)
When setting the listeners in the IMAP Folder, we avoid setting more than one listener for the same imap mailbox (because in some situations we were registering way too many listeners). this was making the pixelated inbox registering the notification and therefore the imap mailbox not being registered. this MR also refactors the way pixelated is initialized, so that it avoid creating a second Account instance. In this way, we make sure that the pixelated mua and the imap server share the same collections for a given mailbox, and therefore any of the two is able to get a notification whenever the other adds a message to the mailbox. - Resolves: #8846, #8798
2017-04-27[tests] fix testsKali Kaneko (leap communications)
mock a renamed method.
2017-04-03[test] remove randomness testerRuben Pollan
There was a test in the Keymanager refresher that was testing the randomness of the refreshing intervals. It was producing a bunch of intervals and checking that all of them where different. This test (rarelly) fails some times, but this is not a sign of bad randomness. - Resolves: #8813
2017-03-31[bug] Log error in case JSON parsing fails for decrypted docSriram Viswanathan
In addition to the UnicodeError exception in _process_decrypted_doc function, we have added ValueError to the exception list so that we can catch any error in JSON parsing, specially a 'NODATA' error that we were getting with some of the emails. This is in reference to issues - https://github.com/pixelated/pixelated-user-agent/issues/908 & https://github.com/pixelated/pixelated-user-agent/issues/981 - to ignore documents that have this problem and not have Soledad try to sync them again and again. with @deniscostadsc
2017-03-31[bug] fix errBack in _decrypt_doc in incoming mail serviceSriram Viswanathan
with @deniscostadsc
2017-01-26Check validity of key signatureZara Gebru
Check if a new fetched key was signed by a old key with the same address. Please do not merge before: https://github.com/isislovecruft/python-gnupg/pull/150 - Resolves #8112
2016-12-26[test] add script for checking the mailKali Kaneko (leap communications)
2016-11-22[tests] fix keymanager tests after refactor and mergeZara Gebru
- some pep8 problems - some confusion with old and new code after merging from old keymanager
2016-11-22[tests] fix some refresher tests after the refactorKali Kaneko (leap communications)
disabled some tests that were failing, for some reason the twisted logger doesn't want to be patched? besides, I don't think it's a good idea to rely on log information for tests. what is it really that we were trying to test there?
2016-11-22[feature] keymanager: background update keysZara Gebru
Port of the original commit: 8f1fe8dd4a54fd2bdda2fc78c339ce9b3d0fc331 by Zara Gebru that introduced updating keys in the background. This was made in the legacy leapcode/keymanager repo, but was lost in the merge to the unified bitmask-dev. Original commit message follows: -------------------------------- - refresh random key in random time - add get key by fingerprint - refactor nicknym methods to own file - tests - note this do not include a check for revoked key, since that need some changes in gnupg - Related: #6089
2016-11-03[tests] _insert_key_docs is a deferredVictor Shyba
Missing yield from _insert_key_docs, which returns a Deferred, was causing tests to fail.
2016-10-19[feat] leap.mail: expose content charset as a separated attributeNavaL
Before we used to have content_doc.content_type = 'text/plain; charset="utf-8"'. Currently, we have content_doc.content_type = 'text/plain'. This change will give us, on top of that: content_doc.charset = 'utf-8'. One can reconstruct the original one using .content_type and .charset.
2016-10-07[tests] remove assertion, bundles are not deleted on exitKali Kaneko (leap communications)
2016-09-06[tests] factor out the common pieces to keymanager.testingKali Kaneko (leap communications)
2016-09-06[test] add speed tests for gpg/wrapper init/enc/decdrebs
this is a port of commit 2d9bec78f in the legacy keymanager repo. Additionally, I'm here separating benchmarking tests from the main tox run. In my machine several of these benchmarking tests seem to be broken, due to issue https://github.com/isislovecruft/python-gnupg/issues/157
2016-09-01[tests] move tests to root folderKali Kaneko (leap communications)