Join the SkySQL and MariaDB Crews in Santa Clara and Save on Registration
Percona Live: MySQL Conference and Expo 2013 starts in just 3 weeks, and it’s the premiere event for MySQL users, open-source enthusiasts, and the technology movers ‘n shakers that make up the rich and diverse MySQL ecosystem.
Submitted by Jean-Jerome Schmidt on April 2, 2013 - 9:34pm GMT
MySQL 5.6 introduces a number of new features designed to improve the security of MySQL. There's the new master_info_repository variable that lets you store replication connection information in a table instead of a lowly text file, new warnings telling users that they should use SSL/TLS, there is a new option to give replication user & password with START SLAVE instead of CHANGE MASTER, and there's mysql_config_editor to encrypt passwords. The problem with these features is that they are a form of Security through Complacency: these things make you feel more secure, but the realistic benefits disappear behind the curtains of Security Theater as soon as an even marginally-determined intruder comes along. In this post, I'll look at some of the new security features in MySQL 5.6 and, however well-intentioned they may be, the danger of relying on these features.
MySQL 5.6 includes a couple new options that allow you to store replication master and relay information in tables instead of in the respective master.info and relay-log.info files that have been used historically. This appears to be partly under the guise of increased security, particularly in the case of the master info "repository", if the "Note" we get from CHANGE MASTER TO is to be believed. However, it's important to note that using --master-info-repository=TABLE really offers no security benefit of any kind.
SkySQL and Monty Program are on the road with our joint Meetup in Amsterdam where Monty Widenius - the origninal creator of MySQL - will unveil his vision of the future of the MySQL database via MariaDB.
Submitted by Therese Elg on February 18, 2013 - 1:06pm GMT
SkySQL et Monty Program organisent une demie journée de conférences consacrées aux bonnes pratiques et retours d'expériences autour des bases de données MySQL®et MariaDB, l'objectif étant de répondre aux préoccupations actuelles des administrateurs de bases de données.
Submitted by Jean-Jerome Schmidt on February 14, 2013 - 4:17pm GMT
SkySQL and the SkySQL logo are trademarks of SkySQL Corporation Ab. Oracle, MySQL, and InnoDB are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.