keymanager.git/changes, branch 0.4.3

[pkg] fold in changes

2015-10-28T13:21:27+00:00

[feat] self-repair the keyring if keys get duplicated

2015-09-30T22:01:19+00:00

In some cases in the past keys got stored twice in different documents.
Hopefully this issue is solved now, this tries to self-repair the keyring
if encounters that. This is not really solving the problem, if it keeps
happening we need to investigate the source.

- Resolves: #7498

[bug] don't repush a public key with different address

2015-09-24T15:08:59+00:00

During decryption the signing public key was getting repush with a
different address as part of the verify usage flagging.

- Resolves: https://github.com/pixelated/pixelated-user-agent/issues/466
- Related: #7420

[bug] catch request exceptions

2015-09-22T15:42:13+00:00

On fetch_key we were not catching the request exceptions, now they are
returned as failure in the deferred as it should.

- Related: #7410

[pkg] fold in changes

2015-07-10T17:44:19+00:00

[bug] remove the dependency on enum34

2015-06-26T22:39:36+00:00

* Resolves: #7188

[pkg] bump dependencies

2015-06-08T18:33:51+00:00

[pkg] fold in changes

2015-06-08T18:33:51+00:00

[feat] adapt to new events api on common

2015-05-27T15:05:33+00:00

- Related: #6359

[feat] set fetched keys as Weak Chain if they are not from the same domain

2015-03-30T20:58:43+00:00

Nicknym server is authoritative for its own domain, but for others it might
retrieve keys from key servers. On keys from the same domain we set the
validation level to 'Provider Trust'. For other domains in the email
address we set it to 'Weak Chain' as we don't have info about its source.

Resolves: #6815
Related: #6718
Releases: 0.4.0