Age | Commit message (Collapse) | Author | |
---|---|---|---|
2017-08-23 | [docs] add bugfixes to changelog | Kali Kaneko | |
2017-08-21 | [docs] update changelog to 0.10.2 | Kali Kaneko | |
and bump changelog to 0.10.3 | |||
2017-08-11 | [pkg] update changelog to ongoing 0.10.2 | Kali Kaneko | |
2017-08-07 | [docs] adds a changelog for incoming box changes0.10.1 | Victor Shyba | |
2017-07-25 | [docs] add secion in changelog for ongoing release | Kali Kaneko | |
2017-07-18 | [doc] update changelog0.10.0 | drebs | |
2017-07-11 | [doc] fix changelog levels | drebs | |
2017-07-08 | [feat] use OpenSSL backend for scrypt if available | Kali Kaneko | |
This needs OpenSSL >= 1.1, otherwise it will keep using the scrypt dependency. We should think about deprecating scrypt as a dependency when we can be sure that the adoption of libssl 1.1 is wide enough. I think that at some point (soledad 0.11 or so) we can drop the scrypt dependency, which was being somehow problematic at times (the _scrypt.so was not appearing when installing with pip, needed workarounds). From that moment on, we can raise an error if an old libssl is found and no scrypt can be imported - leaving that to the user/packager. In debian stretch and afterwards, you can get that version by installing libssl-dev - Related: #8472 | |||
2017-06-01 | [docs] add entry about bumping pypi version0.9.6post1 | Kali Kaneko | |
2017-06-01 | [docs] bump changelog0.9.6 | Kali Kaneko | |
2017-03-17 | [docs] add efkin to authors, changelog entry for py3 tests | Kali Kaneko | |
2017-03-17 | [docs] changelog for 0.9.4 | Kali Kaneko | |
2017-03-13 | [pkg] write changelog for 0.9.3 | Kali Kaneko | |
2016-12-22 | [pkg] update changelog for 0.9.20.9.2release/0.9.x | drebs | |
2016-11-27 | [pkg] update changelog0.9.1 | drebs | |
2016-11-09 | [pkg] update changelog to 0.9.0 | drebs | |
2016-07-14 | [pkg] bump changelog to 0.8.10.8.1 | Kali Kaneko | |
2016-04-18 | [pkg] Update changelog0.8.0 | Kali Kaneko | |