Skip to content

@vixentael vixentael released this Mar 15, 2019 · 7 commits to master since this release

0.85.0, March 15th 2018

Core:

  • Breaking changes:

    Introducing a new more flexible configuration format for AcraCensor rules. AcraCensor doesn't support the old format, all users should migrate (don't worry, it's a simple procedure).

  • Search through encrypted data

    You now can run SQL queries over encrypted AcraStructs allowing users to search through sensitive data without exposing it. This feature is only available in Acra Enterprise version.

  • Transparent proxy mode

    TLDR: Transparent proxy mode allows you to configure AcraServer to encrypt records in specific database columns without altering the application code.

    The application flow doesn't need to change: application sends SQL requests through AcraConnector and AcraServer to the database. AcraServer parses each request, encrypts the desired values into AcraStructs, and passes the modified requests to the database. To retrieve the decrypted data, your application talks to AcraServer again: upon receiving the database response, AcraServer tries to detect AcraStructs, decrypts them, and returns the decrypted data to the application.

    Transparent proxy mode is useful for large distributed applications where updating the source code of each client app separately would be complicated.

    To enable this mode, you need to create a separate encryptor configuration file (acra-encryptor.yaml) that describes which columns to encrypt and provide a path to it in the AcraServer configuration file (or via CLI params --encryptor_config_file=acra-encryptor.yaml).

    Read more details in the Readme and in the Acra documentation section dedicated to Transparent encryption.

    (#285, #309, #314).

  • AcraCensor – SQL firewall to prevent SQL injections

    TLDR: Improved stability of AcraCensor, switched to more flexible rules' configuration.

    Breaking changes: Introducing a new format for configuration files, the previous format is no longer supported, you should migrate to the new one.

    • New configuration file format allows configuring the allowlist and the denylist separately or simultaneously.

      The allow handler allows something specific and restricts/forbids everything else. The allowall handler should be a final statement as that means that all the other queries will be allowed.

      The deny handler allows everything and forbids something specific. The denyall means "block all queries!" (that haven't been allowed or ignored before).

      For each handler, there are settings that regulate queries, tables, and patterns. The order of priority for the lists is defined by their position in the configuration file. The processing priority for each list is as follows: queries, followed by tables, followed by patterns.

      (#298, #297, #304, #306).

      Read more in AcraCensor docs.

    • Added version to the configuration file. This allows detecting an outdated configuration easily. From now on, AcraCensor supports explicit configuration version and logs errors if the configuration is not valid (#321).

    • Improved parsing of SQL queries with prepared statements (#303, #283).

    • Improved error handling for queries that AcraCensor can't parse (#291, #284).

    • Added ability to log unparsed queries to a separate log file for the debugging and configuration purposes. Sometimes AcraCensor can't parse all of the incoming queries and it is useful to have a separate log for them.

      How to use it: Provide the path to the unparsed queries log file in the configuration file parse_errors_log: unparsed_queries.log (#295).

    • Improved support of PostgreSQL queries ("RETURNING" clause) and quoted identifiers (now you can use "tablename" and WHERE "column"=1) (#296).

    • Fixed the bug in QueryCapture log that caused duplicated of records in the log to appear (#318).

  • AcraServer

    • Fixed handling of null-size packets in PostgreSQL protocol (#286).

    • Fixed handling of setting a custom connection API port (#294).

    • Fixed handling of the plain text data response: if the database returns a plain text response, it is redirected "as is" (#305).

    • Fixed handling of casted placeholders in expressions like SELECT $1::type1::type2 FROM table1 WHERE column1=$2::type3::type4 (#328).

    • Improved code quality (some refactoring here and there) (#302, #301).

  • AcraServer, AcraTranslator, AcraConnector

    • Refactored logs and error messages got even more descriptive and user-friendly (#312, #299, #317).

    • Added on-start version logging to make it easier to understand which version is running (#319).

    • Added versioning for configuration files of each service (#322).

    • Added exporting version to metrics (#330, #320).

    • Updated some configuration parameters descriptions for better user-friendliness (please see our docs of AcraConnector and AcraServer for detailed descriptions of each parameter and usage examples) (#329).

  • AcraWriter

    • Updated AcraWriter for ActiveRecord (Ruby), fixed dependencies, added support of mysql2 adapter (#287).

    • Updated AcraWriter for Django (Python), fixed potential encoding issues (#293, #292).

    • Updated AcraWriter for C++, improved cpp codec usage (#290, #289).

    • Added bitcode for AcraWriter iOS and added Swift example project (#327, #326, #325, #324, #323, #323, #307).

    • Improved distribution of AcraWriter for Android, now it's available via Maven (#310).

  • Other

    • Added more tests and then — added even more tests. We just love automating things! (#331, #311, #308, #292).

    • Updated the version of pyyaml used in the tests due to CVE-2017-18342. This change doesn't affect the users of Acra, it only affects our test suite (#300).

Infrastructure:

  • Updated Docker files, added more comments, and updated Go version (#313, #288).

Example projects and demos:

Related blog posts:

Features coming soon:

  • Pseudonymisation: an early version of pseudonymisation library/plugin for Acra for transparent data pseudonymisation.

  • Cryptographically protected audit log: protection for logs against tampering.

Documentation:

Assets 2
You can’t perform that action at this time.