I'm not seeing any options in Piwik for enabling the
MySQL connectors to use SSL. It's very important that we are given the capability of encrypting our connections to database servers, since they may not always be on the same server as Piwik.
For reference, projects such as
osTicket provide additional config variables as the following:
define('DBSSLCA','/path/to/ca.crt'); define('DBSSLCERT','/path/to/client.crt'); define('DBSSLKEY','/path/to/client.key');
So for example, an Amazon RDS connection will only need to define
DBSSLCA in the config for an SSL connection to operate.
Not directly related to resolve this issue but maybe an interesting read: https://www.facebook.com/MySQLatFacebook/posts/10153074619236696
The pull request @ https://github.com/piwik/piwik/pull/8049 is a great start - we have closed it for now as nobody is working on it, but if you are reading this, please consider finish the pull request so we can merge it in Piwik!
Since this issue has been in the works for over 2 years, does it mean something is blocking it so much that it is unlikely to be implemented soon?
If so, is there a recommended workaround to prevent Piwik from sending database passwords in clear text, without encryption? Many thanks for your time working on this issue and for answering my question.
This is a big one for us, and aligns well with the assertion that
Security is a top priority at Matomo (https://matomo.org/security/).
I'm currently working around this by copying code over from PR #10866. Unfortunately I was unable to find any documentation on how to create a release locally.
Because of this, I added #12509 (Include instructions for building Matomo from source), which will be nice for anyone else in a similar situation.
Thank you, @cah-andrewfitzgerald. Please ping me here when you have a version to test and I will try slotting it into our test and deployment release cycle. Good luck!
@cah-andrewfitzgerald As this is PHP and there is no compile step, you can just apply the patch from the PR on your existing release.
A nice trick is downloading https://github.com/matomo-org/matomo/pull/10866.patch
and then appling it using the
patch -p1 < 10866.patch
@RafalLukawiecki I don't believe we're going to have a testable version to contribute back. We're using PR #10866 as is, which works for us, but has not been accepted due to a lack of automated tests.
@Findus23 I understand that there is no compile step, but there is definitely some sort of transformation happening to get from the source code to the distributions which are available from matomo.org/download, but that's a conversation for issue #12509.
Looking at #10866 it seems actually good to merge (without testing) if you can confirm it works.
@tsteur: that would be great!
We're currently running 2.16.1 in a Docker container.
To confirm the PR works, I:
@gwaggott (the original PR author might be able to provide some more details/context)