bitmask_client.git, branch 0.8.2

[bug] fix concatenation of full_user_id to make mail work

2015-03-09T18:47:56+00:00

At some moment, the semantics of the username that we pick from the
login widget changed, so that there's a duplication of the domain part
in the full_user_id that we were passing to the keymanager and the mail
services.

This fix has already been done in the current develop branch (for next
release 0.9.0), so there's no need to port it when merging it back.

While it is true that there's no official release of the client supporting
mail yet, this was an easy fix to port so we will do a 0.8.2
bugfix release so that the 0.8 branch can be used experimentally to test
against development providers. This doesn't mean that you can expect
support on the 0.8.x branch yet, it's only that there is one less bug in
here :)

Resolves: #6759
Releases: 0.8.2

Update release notes.

2015-02-25T17:25:03+00:00

Fold in changes.

2015-02-25T15:51:49+00:00

Merge remote-tracking branch 'leapcode/pr/826' into release/0.8.x

2015-02-23T18:45:48+00:00

Update changes file to reflect tcp->ipc change.

2015-02-23T18:36:38+00:00

Use unix sockets for the fallback, and set permissions

2015-02-23T18:34:36+00:00

... on them, to user-writeable only.

I think we could consider ipc for the curve-case too, at least for the
platforms that support them.

Regression fix: Use the right provider to log in.

2015-02-23T16:08:03+00:00

FIX: Login attempt is made against previously selected provider.

Closes #6654.

Fall back to plain ZMQ if Curve is not available.

2015-02-20T17:23:05+00:00

Use global flag for ZMQ_HAS_CURVE.
Closes #6646

Split changelog into recent changes and history.

2015-02-12T14:47:21+00:00

Closes #6717.

Fix Changelog markup

2015-02-09T15:45:27+00:00

Beware, the markup has to remember that the changelog is appended
to the long description, and all together is displayed as the package
info in the pypi page.

So, we cannot reuse section markups so happily: they have to be
consistent.