soledad.git, branch 0.9.2 [soledad] [pkg] update changelog for 0.9.2 2016-12-22T19:27:57+00:00 drebs drebs@leap.se 2016-12-22T19:27:57+00:00 e360a3a75999503cf45bfbbad69970a452cf3d32 






[test] remove benchmark from ci pipeline
2016-12-19T14:51:30+00:00

drebs
drebs@leap.se

2016-12-19T14:50:24+00:00

ea501c30c1c4a7978a4f9253072081c48fd80cb2












[test] add couchdb tag for tests
2016-12-17T17:05:13+00:00

drebs
drebs@leap.se

2016-12-17T17:05:13+00:00

e28cd85b37f362a8748861da8eb846a65df39369












[pkg] use a twisted resource as server entrypoint
2016-12-17T16:54:03+00:00

drebs
drebs@leap.se

2016-12-17T12:56:22+00:00

feb14a1eadb894f16fcfd09ee6d229d6dfb35569












[test] configure baremetal gitlab ci runner
2016-12-12T11:17:52+00:00

drebs
drebs@leap.se

2016-12-01T11:25:17+00:00

086fc21058314e0a3b13b06af3905ca5c3ee311e












[feature] Change CTR to GCM on secrets.py
2016-12-12T11:17:52+00:00

Victor Shyba
victor1984@riseup.net

2016-12-07T05:03:58+00:00

7877527fe64eaee1f7f107913a4a3dc78767a338

Current implementation can allow tampering and the CTR->GCM exchange can
help to avoid it.
This commits also alters a behaviour where we moved ahead after failing
to decrypt a recovery document. IMHO we can't move ahead as this is a
fatal error.

Signed-off-by: Victor Shyba <victor1984@riseup.net>





Current implementation can allow tampering and the CTR->GCM exchange can
help to avoid it.
This commits also alters a behaviour where we moved ahead after failing
to decrypt a recovery document. IMHO we can't move ahead as this is a
fatal error.

Signed-off-by: Victor Shyba <victor1984@riseup.net>







[feature] Add retro compat on secrets.py ciphers
2016-12-12T11:17:52+00:00

Victor Shyba
victor1984@riseup.net

2016-12-07T04:24:53+00:00

b3fcc5c5bddc73475596c4fe74e3402f0d5c021a

Integrated the secrets's JSON key that specifies ciphers into _crypto
and added optional GCM. Also added a test to check if both cipher types
can be imported.

Resolves: #8680
Signed-off-by: Victor Shyba <victor1984@riseup.net>





Integrated the secrets's JSON key that specifies ciphers into _crypto
and added optional GCM. Also added a test to check if both cipher types
can be imported.

Resolves: #8680
Signed-off-by: Victor Shyba <victor1984@riseup.net>







[feature] use GCM instead of CTR+HMAC
2016-12-12T11:17:52+00:00

Victor Shyba
victor1984@riseup.net

2016-12-07T02:16:28+00:00

349a49d2be011a428023a4ece14001fda57e65c4

Resolves: #8668 - client: substitute usage of CTR mode + HMAC by GCM
cipher mode

Signed-off-by: Victor Shyba <victor1984@riseup.net>





Resolves: #8668 - client: substitute usage of CTR mode + HMAC by GCM
cipher mode

Signed-off-by: Victor Shyba <victor1984@riseup.net>







[refactor] improve blob signature magic usage
2016-12-12T11:17:51+00:00

Victor Shyba
victor1984@riseup.net

2016-11-30T03:07:24+00:00

694e5670da53e923cf809948e400cd546154162b

Our magic value wasn't being used and were represented as a string.
Refactored it to a constant, increased it's size to 2 bytes and optimzed
is_symmetrically_encrypted to look for the magic and symmetrically
encrypted flag under base64 encoding. Most file types will use this
feature to help identifying themselves, so it got refactored to serve
the purpose it was created.





Our magic value wasn't being used and were represented as a string.
Refactored it to a constant, increased it's size to 2 bytes and optimzed
is_symmetrically_encrypted to look for the magic and symmetrically
encrypted flag under base64 encoding. Most file types will use this
feature to help identifying themselves, so it got refactored to serve
the purpose it was created.







[bug] enable batching again
2016-12-12T11:17:51+00:00

Victor Shyba
victor1984@riseup.net

2016-11-29T05:21:02+00:00

5a1827f87dafbf64cfd39dd26e1923a456f05d44

Something happened during rebase. This configuration is supposed to be
True by default now.





Something happened during rebase. This configuration is supposed to be
True by default now.