All Versions
Latest Version
Avg Release Cycle
79 days
Latest Release
1566 days ago

Changelog History
Page 1

  • v0.85.0 Changes

    March 15, 2018

    πŸš€ 0.85.0, March 15th 2018


    πŸ’₯ 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).


    πŸ›  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).


    ⚑️ 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).


    βž• 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).


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

    Example projects and demos:

    iOS Swift example project that shows how to generate AcraStructs with and without Zones.

    Android example project that shows how to integrate AcraWriter library into Android app using maven, and then to generate AcraStructs with and without Zones, and to decrypt them using AcraTranslator.

    πŸ”§ AcraCensor demo that shows how to configure AcraCensor for SQL injections prevention in OWASP Mutillidae 2 example app.

    πŸ’Ž Protecting data in a Rails application demo based on AcraServer, PostgreSQL, and Ruby on Rails client application.

    Protecting metrics in TimescaleDB demo based on AcraServer, TimescaleDB, and Grafana.

    πŸ”§ Transparent proxy mode demo that shows how to configure AcraServer in Transparent proxy mode to protect Django-based application.

    Related blog posts:

    🌐 The difference between SQL firewalls and Web Application Firewalls.

    πŸ— Engineering details on how we built AcraCensor.

    πŸ”‹ 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:

    πŸ“š Updated AcraServer documentation to describe Transparent mode in more details.

    πŸ“š Updated AcraCensor documentation to describe the new configuration format and procedures for migration from the previous one.

    πŸ“š Updated AcraWriter documentation for iOS and Android to reflect the improved installation ways.

  • v0.84.2 Changes

    February 19, 2019

    πŸš€ 0.84.2, February 19th 2019

    πŸš‘ Hotfix:

    πŸ›  Fixed an issue in communication of AcraServer and PostgreSQL that causes AcraServer to stop processing connection due to an unexpected error in parsing packets. The issue occurred when last data in data row column from PostgreSQL comes with empty data (0 bytes).

    Details: #315

  • v0.84.1 Changes

    January 25, 2019

    πŸš€ 0.84.1, January 25th 2019

    πŸš‘ Hotfix:

    πŸ›  Fixed an issue in communication of AcraServer with some specific ORMs (xorm precisely) with MySQL database. In some cases, when database has plaintext data, AcraServer can't decrypt it (which is ok), but propagates decryption error and closes connection (which is wrong, it's fixed).

    Details: #305

  • v0.84.0 Changes

    November 09, 2018

    πŸš€ 0.84.0, November 9th 2018


    Key management

    • Improved LRU cache: fixed concurrent access to LRU cache by adding mutex. LRU cache is used for quick access to in-memory keys (private keys are stored encrypted) in AcraServer and AcraTranslator (#272).

    πŸ“š AcraServer documentation, AcraTranslator documentation.

    • Improved AcraRotate utility: added "dry-run" mode for testing AcraRotate before it is used for real. In the "dry-run" mode AcraRotate doesn't rotate keys: it fetches AcraStructs (from files or database), decrypts, rotates in-memory keys, encrypts the data with new public keys and prints the resulting JSON with new public keys without actually saving the rotated keys and AcraStructs. As key rotation might be tricky, we want users to make sure that AcraRotate has all the required permissions and access right before actually re-encrypting the data (#269).

    πŸ“š AcraRotate documentation.


    • Added C++ AcraWriter library, added examples and tests. The library itself is a single header-only file acrawriter.hpp with dependency on Themis, placed in wrappers/cpp.
      Read the usage guide and examples in examples/cpp folder (#270).

    πŸ“š AcraWriter C++ documentation.

    🌲 Logging

    πŸ‘Œ Improved logs of AcraConnector and AcraServer: use Debug log level for all network errors (closed connection, unavailable network, etc) and use Error log level only for cases of certainly unexpected behavior (#275).

    πŸ‘Œ Improved startup logs: log process PID on start of AcraServer, AcraConnector, AcraTranslator, and AcraWebConfig (#275).

    πŸ›  Fixed timestamps: do not overwrite logs' timestamps (#273).

    Tracing with OpenCensus

    • Added tracing with OpenCensus: AcraServer, AcraConnector, and AcraTranslator track every request from client application to the database and back. Each client request has a unique traceID that helps measure how much time it needs to perform a certain data processing functions (i.e. checking requests via AcraCensor, encrypting data, decrypting AcraStructs, etc.). Traces can be exported to Jaeger (#279, #276, #274).

    πŸ“š You can read more about tracing in our documentation in Tracing in Acra.

    A blogpost about technical details, profits, and pitfalls during the implementation of traces is coming soon.


    πŸ‘Œ Improved AcraServer's connection handling: stop accepting connections after error and stop AcraServer instead of trying to accept connections after the listening socket was closed (#275).

    πŸ‘Œ Improved AcraCensor's handling of prepared statements for PostgreSQL binary protocol (#280).

    πŸ‘Œ Improved handling of terminating packets (COM_QUIT for PostgreSQL and TerminatePacket for MySQL) to correctly handle the closing connections from clients (#275).

    πŸ”¨ Refactored inner logic of AcraCensor: improved code quality and stability, added more tests that use more patterns (#268).


    πŸ— Ceased testing and supporting Go versions below 1.9. This will only affect the users who build Acra manually from sources.
    🐳 You can install the pre-built Acra components shipped for various Ubuntu, Debian, and CentOS distributives using Installation guide. Alternatively, you can check out our Docker images and Docker-compose files in docker folder (#277).

    ⚑️ Tested Acra suite with PostgreSQL v11 and MariaDB v10.3 and updated docker compose examples and Acra Engineering Demo to use it (#278).

    πŸ— Published Acra load balancing demo: it illustrates some of the many possible variants of building high availability and balanced infrastructure based on Acra data protection suite components, PostgreSQL, and Python web application. In these examples we used HAProxy – one of the most popular high availability balancers today.

    ⚑️ Updated AcraStruct Validator – an online tool that can decrypt your AcraStructs. AcraStruct Validator is useful for developers who build their own AcraWriters (to validate AcraStruct binary structure).

    πŸ”‹ Features coming soon:

    βš™ Running SQL queries over encrypted data: perform AcraServer-side lookups (search) over protected data.

    πŸ”Œ Pseudonymisation: early version of pseudonymisation library/plugin for Acra for transparent data pseudonymisation.

    πŸ”Š Cryptographically protected audit log: protection for logs against tampering.

    πŸ“š Documentation:

    πŸ“š AcraWriter C++ has a short guide for installing and using AcraWriter for C++.

    πŸ“„ AcraRotate: added description and notes about "dry-run" mode.

    πŸ“š Updated documentation for logging, collecting metrics, and tracing in Acra.

    πŸ›  Many small fixes here and there to make your overall experience of using Acra's docs on a new platform distinctive and smooth ;)

  • v0.83.0 Changes

    September 28, 2018

    πŸš€ 0.83.0, September 28th 2018


    πŸ”’ Security

    ⚑️ Updated the default and allowed TLS configurations (#254).

    Use TLS v1.2 (the latest supported version in Golang now) and limited cipher suite recommended by Internet Assigned Numbers Authority and OWASP for most transport connections.

    πŸ‘‰ Use TLS v1.0 and extended cipher suit for MySQL TLS connections due to the limited support of MySQL database and drivers.

    πŸ‘Œ Improved security of transport connection between Acra's services by validating the clientId length. This decreases the chance of misusing the clientId (#253).

    Key management – key rotation

    Added AcraRotate utility for rotation of Zone keys and re-encryption of AcraStructs. AcraRotate generates a new Zone keypair ( and zoneid_zone) for a particular ZoneId and re-encrypts the corresponding AcraStructs with new keys. ZoneId stays the same (#256, #239).

    AcraRotate doesn't affect the ACRA_MASTER_KEY or storage keypair used without Zones ( / clientid_storage keys).

    AcraRotate rotates only the Zone storage keys and affects only the AcraStructs encrypted with Zones.

    AcraRotate works with AcraStructs stored both in database cells (MySQL or PostgreSQL) or files.

    πŸ“š Read the full documentation on AcraRotate on the Documentation Server.

    AcraCensor – SQL filter and firewall

    πŸ‘Œ Improved SQL filtering through more complex pattern matching (#264, #263, #262, #238).

    - `%%VALUE%%` pattern represents literal value (string, binary, number, boolean) and is supported in the following expressions: WHERE, IN, ORDER BY, GROUP BY, BETWEEN.
    - `%%LIST_OF_VALUES%%` pattern represents several values one by one, used with IN expressions.
    - `%%SUBQUERY%%` pattern represents a subquery expression inside the main query.
    - `%%WHERE%%` pattern represents one or more expressions after a WHERE statement. This pattern works for SELECT/UPDATE/DELETE queries.
    - `%%COLUMN%%` pattern represents a column expression used after SELECT and ORDER BY expressions.
    - `%%SELECT%%` pattern represents a whole SELECT expression.

    πŸ“š Read the detailed description and usage examples on the AcraCensor page on DocServer.


    βž• Added Java/Android AcraWriter library, added examples and tests (#252).

    Read the usage guide and examples in examples/android_java folder.

    βž• Added SQLAlchemy type wrappers for the Python AcraWriter (#257).

    πŸ‘Œ Improved and refactored the Python AcraWriter example of encrypting data and reading it from the database (#258).

    Prometheus Metrics

    - Added functionality for exporting the basic metrics of AcraServer, AcraConnector, and AcraTranslator to Prometheus: if incoming_connection_prometheus_metrics_string is set, the service will generate specific metrics (time of connection life, time of processing requests, AcraStruct decryption counters) and push them to Prometheus (#260, #251, #234).


    πŸ‘Œ Improved AcraConnector's compatibility with PostgreSQL: AcraConnector now correctly handles the database's denial to use TLS connection (#259).

    βž• Added export of CLI parameters for AcraServer, AcraConnector, and AcraTranslator to markdown (#261).

    πŸ‘Œ Improved readability of CEF-formatted logs by sorting extension fields in alphabetical order (#255).

    πŸ‘Œ Improved quality of our codebase β€” cleaned up the old unnecessary code (#250).


    • βž• Added AcraRotate as a ready-to-use tool inside AcraTranslator and AcraServer Docker containers (#236).

    πŸ“š Documentation:

    πŸ“š Made the Documentation Server the primary and the only regularly updated source of documentation for Acra. The most recent version of the documentation, tutorials, and demos for Acra can be found there. The GitHub Wiki documentation for Acra is still available, but is no longer updated starting with the version 0.82.0 (with the exception of Changelog and README files with every new version release).

    πŸ“š AcraCensor: updated the details on how the "patterns" filter works.

    πŸ“„ AcraRotate: added a tutorial for using AcraRotate to rotate Zone keys and re-encrypt the data.

    πŸ›  Tons of small fixes here and there to make your overall experience of using Acra's docs on a new platform distinctive and smooth ;).

  • v0.82.0 Changes

    August 14, 2018



    AcraTranslator is a lightweight server that receives AcraStructs and returns the decrypted data. AcraTranslator doesn’t care about the source of the data, it accepts AcraStructs via HTTP or gRPC API. An application can store AcraStructs anywhere it is convenient: as cells in the database, as files in the file storage (local or cloud storage, like AWS S3). An application sends AcraStructs as binary data and receives plaintext (or decryption error) from AcraTranslator.

    However, sending plaintext data over a non-secure channel is a bad idea, so AcraTranslator requires the use of Themis Secure Session encryption channel (which is basically an encrypted TCP/unix sockets). To establish a Secure Session connection, an application doesn’t need to contain the crypto-code itself, only to direct the traffic through AcraConnector instead.

    🐳 AcraTranslator supports AcraStructs via HTTP and gRPC API, uses in-memory LRU cache to store encryption keys, and detects poison records. AcraTranslator is shipped as a pre-built binary and as a Docker container.

    πŸ”§ Read the detailed guide on how to install, configure, and run AcraTranslator.

    (#213, #212, #207, #205, #204, #203, #200, #199, #198, #197)

    ⚑️ Updated AcraConnector to support connections with AcraTranslator (#206).

    🌲 Logging

    πŸ‘Œ Improved startup logs for AcraServer, AcraTranslator, and AcraConnector: now it's easier to understand that the service is up and running (#242).

    βž• Added clientId to AcraServer logs: now it's easier to understand which client was sending the request that led to a failed or successful AcraStruct decryption (#214).

    πŸ‘Œ Improved logging by masking query parameters: neither AcraServer nor AcraCensor won't leak sensitive query while logging the content (#216, #211).

    Poison records

    0️⃣ Poison record detection for AcraServer and AcraTranslator can now be turned on and off. Poison records detection is ON by default: AcraServer/AcraTranslator will try to detect poison record and log to stderr if a poison record is detected (#240, #230, #215).

    🐎 Increased performance of AcraServer/AcraTranslator if poison records are enabled (#232).

    Key management

    πŸ‘Œ Improved processing of decryption keys for AcraServer, AcraTranslator, and AcraConnector: now it is possible to store private keys encrypted in files and in memory, decrypt them before using, and purge after usage (#202).

    βž• Added configurable LRU cache for the in-memory keys: this will increase the performance if you operate with hundreds of storage keys on AcraServer and AcraTranslator (#219).

    AcraCensor / SQL filter and firewall

    • Improved SQL filtering by adding pattern matching: now you can blacklist or whitelist queries that match particular patterns, like SELECT %%COLUMN%% FROM company %%WHERE%%.

    πŸ‘ Currently supported patterns: %%VALUE%%, %%COLUMN%%, %%WHERE%% and %%SELECT%%.

    Read the detailed description and usage examples on the AcraCensor page.

    (#248, #247, #246, #245, #243, #238, #231, #226, #217)

    - Improved AcraCensor performance for queries matching (#208).


    • Added iOS/Objective-C AcraWriter library as CocoaPod, added examples and tests.

    Read the usage guide and examples in examples/objc folder.

    (#241, #235, #233).

    - Improved security of AcraWriter libs for Go, Ruby, Nodejs, and iOS through zeroing secret keys where it was missing (#244).

    βͺ AcraRollback

    - Improved handling of insert query parameter to simplify using AcraRollback from bash (#210).


    πŸ‘Œ Improved AcraStruct decryption by multiple validations of AcraStruct format before decrypting. This fix improves AcraServer/AcraTranslator error messages in case of a failed decryption (#201).

    πŸ‘Œ Improved stability of integration test suite, trying to avoid 'timed out' errors from CircleCI (#200).

    πŸ‘Œ Improved code quality, fixing gofmt and golint issues (#229, #228, #227, #224, #223, #221).

    🚧 WIP

    βž• Adding a way to export decryption metrics (decryption time, number of connections) from AcraServer to Prometeus (#234).

    Prototyping AcraRotate tool for rotating the Zone keys easily (#239).


    ⬇️ Drop testing and supporting go version below 1.8. This will only affect the users who build Acra manually from sources.
    🐳 You can install pre-built Acra components shipped for various Ubuntu, Debian, and CentOS distributives using Installation guide. Alternatively, you can check out our Docker images and Docker-compose files in docker folder

    βž• Added AcraTranslator as pre-built binary and docker container (#222).

    βž• Added AcraTranslator and AcraConnector docker-compose files: now it's easy to set up a demo stand just by running one command (#225).

    βž• Added AcraRollback and AcraPoisonRecordMaker as ready-to-use tools inside AcraTranslator and AcraServer Docker containers (#236).

    πŸ“š Documentation:

    0️⃣ Key management: clarified key names and default locations, illustrated public key exchange in details.

    AcraServer: improved examples of how to run AcraServer.

    AcraTranslator: added description of the service, installation and launching guide, added ready-to-use examples for HTTP and gRPC API.

    AcraConnector: added examples of how to run AcraConnector with AcraTranslator.

    πŸ”§ AcraCensor: added examples of the configuration file, described in details how the "patterns" filter works.

    βͺ AcraRollback: added examples of running AcraRollback in local mode, which allows storing the decrypted data locally, without pushing it back to the database.

    πŸ“š This is the last version of Acra for which the main documentation will be actively updated in the GitHub Wiki. From now on, the most recent version of the documentation, tutorials, and demos for Acra will be available in the official Cossack Labs Documentation Server.

  • v0.81.0 Changes

    July 06, 2018


    • Prepared Statements

      • Added support of prepared statements for PostgreSQL/MySQL. Both binary and text response formats are supported (#192).
    • SQL requests filtering in AcraCensor

    AcraCensor got smarter in preventing SQL Injections.

    • Improved flexibility for parsing queries. If AcraCensor can't parse an SQL query, it is considered as potentially too dangerous to send it to the database, so AcraCensor blocks such "unparseable" queries by default. However, setting the configuration flag ignore_parse_error to true will make AcraCensor ignore the "unparseable" quality of queries and send them to the database anyway. Check out the configuration example in configs/acra-censor.example.yaml (#194).

    • Added support of complex JOIN queries (#191).

    • Improved reading/writing QueryCapture log file. Now AcraCensor uses bufferisation before writing queries into a log file. Changed format of QueryCapture log to JSON Line (each query sits in a separate line in a log file instead of having an array of JSON objects) (#193).

    • Introduced a few fixes here and there, made integration tests for AcraCensor more stable (#184).

      • πŸ‘ Improving MySQL support

    We introduced MySQL support just a few Acra releases ago and we continue polishing it. Now we've updated the example projects so you can jump right into the code!

    Take a look at how to use Acra for both PostreSQL and MySQL databases in these examples:

    • Go: see the examples/golang folder (#190).

    • Ruby: see the examples/ruby folder (#189).

    • Python: see the examples/python folder (#188).

      • Other
    • Updated handling of message formats for PostgreSQL and MySQL protocols (#186).

    • Improved logging in CEF and JSON formats for high load systems (#195).

    • Added comprehensive Readme to every project in /examples folder (#196).

    • Added pre-generated configuration file for AcraAuthmanager. Now it's easier to configure AcraServer using AcraWebconfig (#187).

    πŸ“š Documentation:

  • v0.80.0 Changes

    May 31, 2018


    • Renaming

      • Global renaming of Acra components and their configuration parameters. We believe that the updated naming will decrease confusion about the components' functions and will make Acra's setup and usage process easier.

    Main services:

    | Old name | New name | Function | | --- | --- | --- | | AcraServer | AcraServer | decrypts data from the database | | AcraWriter | AcraWriter | encrypts data on the client side | | AcraProxy | AcraConnector | encrypts traffic between the client and the server using Themis Secure Session | | AcraCensor | AcraCensor | firewall, part of AcraServer, blocks suspicious SQL requests to the database | | AcraConfigUI | AcraWebConfig | lightweight HTTP web server for managing AcraServer's certain configuration options |


    | Old name | New name | Function | | --- | --- | --- | | acra_rollback | AcraRollback | decrypts the whole database | | acra_genkeys | AcraKeymaker | generates encryption keys for storage and transport of the Acra components | | acra_genauth | AcraAuthmanager | generates user accounts for AcraWebConfig | | acra_genpoisonrecord | AcraPoisonRecordMaker | generates poison records for databases | | acra_addzone | AcraAddzone | generates Zones' header for AcraWriter |

    Check the configurations of components inside /configs folder and read Migration Guide for more details (#175, #174, #173, #170, #169, #168).

    • SSL/TLS

      • Improved SSL/TLS connections between AcraServer<->AcraConnector and AcraServer<->database. Added TLS authentication mode (tls_auth) argument to the AcraServer/AcraConnector configuration files:
        • for AcraConnector it indicates how to authenticate AcraServer during a TLS connection;
        • for AcraServer it indicates how to authenticate database during a TLS connection.
      • Updated TLS configuration to provide other less strict authentication methods (do not authenticate client from server, ask for any certificate, ask and check) (#171).
    • SQL requests filtering

      • Added support of filtering SQL requests for PostgreSQL databases. Now you can setup AcraCensor rules for both MySQL and PostgreSQL databases (#177).
      • Improved QueryCapture: AcraCensor writes allowed/blocked queries into a separate log file without blocking the main process (#176, #172).

    See a detailed description of AcraCensor on the corresponding AcraCensor documentation page.

    • πŸ’Ž AcraWriter in Ruby

    • Key Handling

      • Added make keys target in the Makefile: one command now generates keys and places them into correct folders for all Acra components (#182, #181).
      • Improved handling of master key length longer than 32 bytes (#183).
    • Other

      • Updated notification when AcraConnector is launched in an environment without netstat (#167).
      • Updated error handling for AcraServer working with Zones and fix some corner-cases in using PostgreSQL protocol (#186, #179).


    • 🐳 Even better Docker support

      • Added more ready-to-use Docker Containers: acra-keymaker, acra-authmanager. As a result, each Acra component is wrapped into a Docker container, allowing you to try Acra into your infrastructures easily.
      • Added easy-to-use docker-compose files for setting up the whole Acra-based environment connected to MySQL database. Possible configurations include setup with/without SSL, with/without AcraConnector, with/without Zones (#180). Check out the instructions and examples in the /docker folder: we have examples for both MySQL and PostgreSQL databases.
      • Updated descriptions for official Cossack Labs packages on Docker Hub.
      • Updated Getting started with Docker guide to make starting out with Acra even easier.
    • OS

      • Added support of Ubuntu Xenial, Ubuntu Bionic (added precompiled binaries and tests to make sure that Acra is compiling/building/working well on 16.04/18.04).

    πŸ“š Documentation:

    • ⚑️ Updated tutorials about protecting a Ruby on Rails app and a Django app.
    • ⚑️ Every single document, code line, and image are updated using the new naming.
    • Significant parts of the README have been rewritten.
  • v0.77.0 Changes

    April 13, 2018


    MySQL databases

    • Added support for MySQL: now you can connect Acra to MySQL databases. Works with any SSL mode: require, allow, disable.
    • Tested and supported on: MySQL (#155, #140).

    πŸ‘ > Note: Prepared statements are not supported yet, but this feature is coming soon!

    πŸ“š Read about the new configurations on the AcraServer documentation page.

    Keeping keys in secret

    • Added encryption for the keys' folder: private keys are now symmetrically encrypted by master_key (#143) for storage.
    • Added ability to generate public/private keys in the separate folders (#148, #142).

    Read more about the current changes in key management here.

    Filtering requests for MySQL

    • Added firewall component named AcraCensor to handle MySQL queries.

    πŸ”§ You can provide a list of restricted or allowed tables, columns, and exact queries to handle. AcraCensor will pass the allowed queries and return error on forbidden ones. Rules are configured and stored in yaml file. Each request is logged in real time. Moreover, all the queries and their states are logged into a separate log file. (#151, #138, #136, #132, #125, #108).

    πŸ“š See a detailed description of AcraCensor on the corresponding AcraCensor documentation page.

    πŸ’» Web Config UI

    • Added lightweight HTTP web server for managing AcraServer's certain configuration options.

    ⚑️ You can update the proxy address and port, database address and port, handling of Zone mode and poison records. On saving new configuration, acraserver will gracefully restart and use these settings automatically. The access to thiw web page is restricted using basic auth. (#153, #141, #123, #111).

    πŸ‘€ See the interface screenshot and detailed instructions at Acra Config UI page.

    🌲 Logging

    • Added support of new logging formats: plaintext, CEF, and json.

    πŸ”§ Logging mode and verbosity level is configured for AcraServer, AcraProxy, and AcraConfigUI in the corresponding yaml files. Log messages were slightly improved, custom error codes were added (which we believe will help to understand and debug any issues) (#135, #126, #110).

    🌲 Read more about the log analysis at Logging page.

    βœ… Tests

    • Added many new integartion tests, fixed stability and handling of more complicated use-cases (#150, #147, #137, #117, #116, #115).


    🐳 Docker support

    βž• Added Docker Container for every main component: AcraServer, AcraProxy, AcraConfigUI, and key generators (AcraGenKeys and AcraGenAuth). You can find the containers in /docker folder or on the Docker Hub (#139).

    ⚑️ Updated Getting started with Docker guide to make starting out with Acra even easier.

    βž• Added easy-to-use docker-compose files to launch Acra in different environments, including key distribution. Possible configurations are:

    - `acraserver` + `acra_configui `;
    - connecting to PostreSQL or MySQL databases;
    - using Secure Session or SSL as transport encryption;
    - with or without `acraproxy`;
    - with or without zones.  

    🐳 This is huge! We encourage you to try it! Check out the instructions and examples in the /docker folder. (#154, #146, #134, #133, #102).

    Go versions

    - Updated the list of supported versions of Go. Every Acra component can now be built using Go >1.7, except acra_rollback that requires Go >1.8. No worries, you can still download Acra as a binary package anyway :)


    • Dropped support of Debian Wheezy (no autotests, no precompiled binaries now).

    πŸ“š Documentation:

    • πŸ“š Updated QuickStart documentation about launching and building Acra components.
    • Described how to setup AcraCensor and AcraConfigUI.
    • βž• Added more details and described new options (like using TLS and connecting to MySQL databases) for AcraServer and AcraProxy.
    • 🌲 Described new logging formats.
    • ⚑️ Updated description of Key management approach we encourage you to use.
    • 🐳 Described Docker components and ready-to-use Docker Compose configurations based on the Docker Readme.
    • ⚑️ Updated Getting started with Docker guide.
    • πŸ“„ Distributed the information about master key across the docs.
    • Many small improvements.
  • v0.76 Changes

    March 09, 2018


    • πŸ‘ SSL / TLS support

    πŸ‘ Now you can use PostgeSQL with SSL/TLS settings enabled. Acra supports two modes of connection between AcraServer and the database: using SSL/TLS or using Secure Session (#113, #119).

    • Unix sockets

    πŸ‘ Acra now supports usage of both TCP and Unix Sockets as a connection layer between AcraWriter <-> AcraProxy <-> AcraServer.

    βœ… Tests

    • Updated integration test suit to support multiple connection modes between the Acra components and the database (#115, #117, #118, #120).
    • Added Docker image to make testing easier (#104).


    • βž• Added support of Go 1.10, removed support of older Go versions (<1.6).
    • βž• Added support of Ubuntu 17.10, Ubuntu 16.04, Ubuntu 14.04, Debian Stretch.
    • ⚑️ Updated dependency libraries (libthemis and libcrypto) to use the latest ones.

    πŸ“š Documentation:

    • πŸ“š Updated the documentation and tutorials to reflect the latest changes.