Re: Update to Percona CVE-2016-6662 Vulnerability Communication

2016-09-15 Thread Reindl Harald
Am 16.09.2016 um 00:21 schrieb Johan De Meersman: - Original Message - From: "Reindl Harald" Sent: Friday, 16 September, 2016 00:12:26 frankly - mysqld_safe needs to go away and life is beautiful without for years here and yes taht worked for mysql too before switch to MariaDB to sa

Re: Update to Percona CVE-2016-6662 Vulnerability Communication

2016-09-15 Thread Johan De Meersman
- Original Message - > From: "Reindl Harald" > Sent: Friday, 16 September, 2016 00:12:26 > > frankly - mysqld_safe needs to go away and life is beautiful without for > years here and yes taht worked for mysql too before switch to MariaDB > > to say it clear: running *any* code as root fo

Re: Update to Percona CVE-2016-6662 Vulnerability Communication

2016-09-15 Thread Reindl Harald
Am 16.09.2016 um 00:05 schrieb Johan De Meersman: This is probably of interest to many of you, and I've not seen it on the list yet. Kenny Gryp's blog about the vulnerability is at https://www.percona.com/blog/2016/09/12/database-affected-cve-2016-6662/ . For those who use it, there's an an

Fwd: Update to Percona CVE-2016-6662 Vulnerability Communication

2016-09-15 Thread Johan De Meersman
This is probably of interest to many of you, and I've not seen it on the list yet. Kenny Gryp's blog about the vulnerability is at https://www.percona.com/blog/2016/09/12/database-affected-cve-2016-6662/ . For those who use it, there's an ansible playbook to patch the workaround into mysqld_s