bitmask-dev.git/src/leap/bitmask/bonafide, branch 0.10a2

use the passed ca_cert

2017-07-18T19:31:31+00:00

if there is no ca_cert passed and the provider is configured, use the
pinned ca cert when the autoconf parameter is true.

[refactor] skip looking for cacert bundle in bitmask

2017-07-14T12:28:08+00:00

leap.common is going to handle this

[bug] fail bonafide bootstrap for self sign certs

2017-06-05T17:42:13+00:00

- Resolves: #8881

[feat] check ca cert fingreprint against provider.json

2017-06-05T17:42:12+00:00

[refactor] cleanup

2017-05-16T17:32:24+00:00

[bug] return ok from a succesful provider delete

2017-05-12T17:16:53+00:00

[bug] make global the provider bootstrap deferreds

2017-05-12T17:10:00+00:00

- Resolves: #8884

[bug] correctly handle authenticate's autoconf parameter

2017-05-04T19:25:51+00:00

This fixes two bugs with handling the autoconf parameter:
 - It looks for "True" instead of "true" in the dispatching code to
   account for json.dumps() converting true into a boolean and str()
   returning the python-style capitalized version "True".
 - It moves the initial definitions of offirst_bootstrap,
   ongoing_bootstrap, and stuck_bootstrap into the class instantiation
   method so they don't get shared between instances of the
   class. Previously, this caused one instance being bootstrapped to
   causes other instances to think they were also actively being
   bootstrapped.

Resolves #8843

[bug] unify logging style using class attr

2017-04-27T17:33:28+00:00

I changed most of the logger statements to use a class attribute, in
this way it's easier to identify which class it's logging them.

in some cases I leave a module-level logger, when we're either using
functions or when the module it's too small.

at the same time I did a general review and cleanup of the logging
statements.

[feat] add bonafide authentication event

2017-04-20T16:15:38+00:00

- Resolves: #8844