Sun, 04 Feb 2018 03:53:41 +0100closing branch ENGINE-352
Krista Bennett <krista@pep-project.org> [Sun, 04 Feb 2018 03:53:41 +0100] rev 2474
closing branch

Sun, 04 Feb 2018 03:52:27 +0100Merged in ENGINE-352 database_change_branch
Krista Bennett <krista@pep-project.org> [Sun, 04 Feb 2018 03:52:27 +0100] rev 2473
Merged in ENGINE-352

Sun, 04 Feb 2018 03:38:28 +0100Merged the mistrust fixes into branch for merging database changes before adding to default database_change_branch
Krista Bennett <krista@pep-project.org> [Sun, 04 Feb 2018 03:38:28 +0100] rev 2472
Merged the mistrust fixes into branch for merging database changes before adding to default

Sun, 04 Feb 2018 03:36:08 +0100A whole horde of trust fixes (mistrust list added, tests fixed, and sneaky null string in elect key removed) mistrust_fixes
Krista Bennett <krista@pep-project.org> [Sun, 04 Feb 2018 03:36:08 +0100] rev 2471
A whole horde of trust fixes (mistrust list added, tests fixed, and sneaky null string in elect key removed)

Sun, 04 Feb 2018 02:05:53 +0100ENGINE-352: added is_pep_user exception in encrypt_message ENGINE-352
Krista Bennett <krista@pep-project.org> [Sun, 04 Feb 2018 02:05:53 +0100] rev 2470
ENGINE-352: added is_pep_user exception in encrypt_message

Fri, 02 Feb 2018 17:15:33 +0100ENGINE-352: we now update the right comm_type in the right place. ENGINE-352
Krista Bennett <krista@pep-project.org> [Fri, 02 Feb 2018 17:15:33 +0100] rev 2469
ENGINE-352: we now update the right comm_type in the right place.

Fri, 02 Feb 2018 11:03:20 +0100ENGINE-352: put in the mechanism to attach an is_pep mechanism for the user; tacking pEp messages is complicated, however, as it seems we've also always fouled up when we checked on that (we don't check what key it's encrypted with before we declare whatever key gets retrieved by update_identity is the same, and then set the comm_type on that, which could be the wrong key.) So that's the next fix. ENGINE-352
Krista Bennett <krista@pep-project.org> [Fri, 02 Feb 2018 11:03:20 +0100] rev 2468
ENGINE-352: put in the mechanism to attach an is_pep mechanism for the user; tacking pEp messages is complicated, however, as it seems we've also always fouled up when we checked on that (we don't check what key it's encrypted with before we declare whatever key gets retrieved by update_identity is the same, and then set the comm_type on that, which could be the wrong key.) So that's the next fix.

Thu, 01 Feb 2018 13:57:04 +0100shelving mistrust investigation and fixes to fry bigger fish mistrust_fixes
Krista Bennett <krista@pep-project.org> [Thu, 01 Feb 2018 13:57:04 +0100] rev 2467
shelving mistrust investigation and fixes to fry bigger fish

Mon, 29 Jan 2018 16:52:54 +0100ENGINE-345: fix to outgoing_message_rating - set to PEP_rating_unencrypted instead of unknown
Krista Bennett <krista@pep-project.org> [Mon, 29 Jan 2018 16:52:54 +0100] rev 2466
ENGINE-345: fix to outgoing_message_rating - set to PEP_rating_unencrypted instead of unknown

Mon, 29 Jan 2018 12:44:56 +0100Ok, now really closing this branch. For real. ENGINE-329
Krista Bennett <krista@pep-project.org> [Mon, 29 Jan 2018 12:44:56 +0100] rev 2465
Ok, now really closing this branch. For real.