soledad.git - [soledad]

Age	Commit message (Collapse)	Author
2017-04-04	[bug] fix loose ends on _crypto and tests	Victor Shyba

2017-04-04	[style] pep8 fixes	Victor Shyba

2017-04-04	[bug] fix blobs put	drebs

2017-04-04	[bug] handle case when blob is not found in server	drebs

2017-04-04	[refactor] improve logging and manual testing of blobs	drebs

2017-04-04	[doc] add license header to _blobs.py	drebs

2017-04-04	[style] pep8 fixes	drebs

2017-04-04	[bug] use rowid to insert blob in sqlcipher	drebs

2017-04-04	[feature] close mvp loop with client	Kali Kaneko

2017-04-04	[feature] enable simple obfuscation of blob size in preamble	Kali Kaneko
	use a powers of two ceiling for the reported size in the preamble. for this to be effective against a passive adversary, cover traffic should be used in the uploads too. This is just a first-stop measure; proper research should be done to determine a good tradeoff between avoiding information leakage and saving some storage and bandwidth.. - Documentation: #8759 - Related: #8759
2017-04-04	[feature] save blob to db, incrementally	Kali Kaneko

2017-04-04	[feature] add attribute to keep blob crypto	Kali Kaneko

2017-04-04	[refactor] refactor crypto api to better allow streaming	Kali Kaneko
	Motivation is that I need to pass partial data to the decryptor, mainly.
2017-04-04	first implementation of client blobs	Kali Kaneko

2017-03-31	[feature] raise earlier when deleting None	Victor Shyba
	If an application tries to delete None, by accident, raising earlier would help to show the caller stack trace instead of inner sqlite backend stack and make the error more friendly. - Resolves: #8791
2017-03-23	[docs] add Anike to client/AUTHORS	Victor Shyba

2017-03-23	[feature] generate recovery code	Anike Arni
	with @tayane
2017-03-17	[docs] add tulio to authors0.9.5	Kali Kaneko

2017-03-17	[docs] add efkin to authors, changelog entry for py3 tests	Kali Kaneko

2017-03-17	[refactor] Improve python3 compatibility	efkin
	With this commit all tests on py34 tox environment are collected.
2017-03-17	[test] Prepare new tox environment	efkin
	At this point tests are not yet collectable in the new environment. But no regressions observed.
2017-03-13	[docs] explain sync bypass due lack of token	Victor Shyba

2017-03-13	[feat] make database creation appear in logs	drebs

2017-03-13	[bug] remove offline flag	drebs
	The offline flag is not needed and rendered the soledad client prone to bugs because it would need to be toggled and that is succeptible to timing problems.
2017-03-13	[bug] fix raising of invalid auth token error	drebs

2017-03-09	[bug] secrets version defaults to v1	Tulio Casagrande

2017-03-09	[bug] add default version when decrypting secrets	Tulio Casagrande
	Resolves: https://0xacab.org/leap/soledad/issues/8788
2017-03-02	[bug] handle error once	Victor Shyba
	Handle it only if self.deferred wasnt called yet, otherwise that's just an out-of-sync call from a scheduled deferred. Since it was already logged, it's ok to ignore.
2017-03-02	[bug] fix shared database initialization	drebs

2017-02-25	[bug] save client secret downloaded from remote storage	drebs
	After refactor, the client secret bootstrap logic was flawed, and remote secret was not being saved properly. This commit fixed that and tries to improve the bootstrap code to make it more clear.
2017-02-25	[bug] remove unused named tuple from client secrets	drebs

2017-02-25	[refactor] improve secret bootstrap code and doc	drebs

2017-02-25	[doc] improve doc and rename EmitMixin to UserDataMixin	drebs

2017-02-25	[refactor] pass soledad object to client secrets api	drebs
	In order to be able to change passphrase, token and offline status of soledad from the bitmask client api, the secrets api also has to be able to use up-to-date values when encrypting/decrypting secrets and uploading/downloading them to the server. This commit makes public some soledad attributes that were previously "private" (i.e. used to start with "_" and were not meant to be accessed from outside), and passes the whole soledad object to the client secrets api. This makes the code cleaner and also allows for always getting newest values of soledad attributes.
2017-02-23	[refactor] remove syncable property from shared db	drebs

2017-02-23	[feature] add offline status to soledad client api	drebs

2017-02-23	[feat] avoid client sync if no token is set	drebs

2017-02-23	[refactor] use get_token in client secrets api	drebs

2017-02-23	[refactor] add EmitMixin for a cleaner emitting experience	drebs

2017-02-23	[refactor] remove creds from client api	drebs

2017-02-16	[style] add deprecation warning on legacy decoder	Victor Shyba

2017-02-16	[feature] add doc size to preamble	Victor Shyba
	That's necessary for blobs-io. Current code includes backwards compatibility branching and tests, which shall be removed on next releases.
2017-02-15	[tests] add tests for preamble encoding	Victor Shyba

2017-02-09	[refactor] remove twisted session persistence	drebs
	The need for token caching in server is a matter of debate, as is the ideal way to do it. Twisted sessions store the session id in a cookie and use that session id to persist. It is not clear if that implementation is needed, works with future features (as multiple soledad servers) or represents a security problem in some way. Because of these, this commit removes it for now. The feature is left in git history so we can bring it back later if needed.
2017-02-09	[feat] use cookies in the client syncer	drebs

2017-02-09	[doc] improve comment for client secrets file migration function	drebs

2017-02-09	[bug] several fixes for secrets refactor	drebs
	- store ENC_METHOD value instead of string in secrets file - allow for migration of not-activated secrets - allow migration of 'aes256' and ENC_METHOD secrets cipher
2017-02-09	[bug] use derived key for local storage	drebs

2017-02-09	[refactor] improve secrets generation and storage code	drebs

2016-12-12	[feature] Change CTR to GCM on secrets.py	Victor Shyba
	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>