bitmask_client.git/src/leap/bitmask/services, branch develop

[feat] handle keymanager version errors

2016-07-03T13:56:25+00:00

If the keymanager documents are not supported, mostly because they are
created by a newer version of keymanager, fail gracefully.

- Related: #8165

[feat] Adapt to the new KeyManager API without key types

2016-05-24T18:09:57+00:00

- Related: #8031

[bug] let the failure propagate

2016-04-25T21:55:07+00:00

The failure was processed in start_incoming_mail_service what will make
it return a None when an IncomingMail object was expected. If we
propagate the failure it can be treated properly by the IMAPController.

- Related: #8051

pep8/flake8

2016-04-19T16:07:40+00:00

[style] autopep8

2016-04-18T20:33:26+00:00

[refactor] cleanup helper usage to adapt to new one

2016-04-18T20:17:26+00:00

also cleanups build process

[refactor] cleanup helper usage to adapt to new one

2016-04-18T20:17:11+00:00

also cleanups build process

[feature] privileged bitmask helper

2016-04-18T20:15:21+00:00

This is still quite untested, and a bit hacky, but the main idea behind
let us have a daemonized bitmask helper, that should be installed by the
Bitmask installer. Its responsibilities are to launch the vpn process as
a privileged user, and start/stop the firewall.

[refactor] adapt to the new Account signature

2016-04-16T17:17:50+00:00

[bug] instantiate soledadconfig if needed

2016-03-28T19:10:54+00:00