Add MySQL 9.1.0 configuration, initialization script, and update bundle release to 2024.12.1

[N6REJ]

PR Type

enhancement, configuration changes

---

Description

• Added initialization script for MySQL 9.1.0 to facilitate insecure setup.
• Introduced configuration files for MySQL 9.1.0, including bearsampp.conf, my.ini, and my.ini.ber.
• Updated build.properties to reflect the new bundle release version 2024.12.1.
• Enhanced releases.properties with the release details for MySQL 9.1.0.

---

Changes walkthrough 📝

	Relevant files
Enhancement	init.bat Add MySQL 9.1.0 initialization batch script                            bin/mysql9.1.0/init.bat Added a batch script to initialize MySQL 9.1.0 insecurely. +3/-0
Configuration changes	bearsampp.conf Add MySQL 9.1.0 configuration file                                              bin/mysql9.1.0/bearsampp.conf Added configuration file for MySQL 9.1.0. Defined MySQL executable paths and settings. +10/-0    my.ini Add MySQL 9.1.0 my.ini configuration                                          bin/mysql9.1.0/my.ini Added MySQL 9.1.0 configuration settings. Configured client, mysqld, and other MySQL utilities. +55/-0    my.ini.ber Add backup configuration for MySQL 9.1.0                                  bin/mysql9.1.0/my.ini.ber Added backup configuration for MySQL 9.1.0. Mirrored settings from my.ini. +55/-0    build.properties Update bundle release version                                                        build.properties Updated bundle release version to 2024.12.1. +1/-1      releases.properties Add MySQL 9.1.0 release information                                            releases.properties Added release information for MySQL 9.1.0. +1/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 Security concerns Multiple Security Issues: Insecure initialization: The MySQL server is initialized with --initialize-insecure flag which creates root account without password Empty root password: Configuration explicitly sets empty root password in bearsampp.conf Authentication plugin: The default_authentication_plugin setting is commented out in my.ini, which may result in less secure legacy authentication being used Exposed configuration: Sensitive server configuration including paths and security settings are stored in plain text

⚡ Recommended focus areas for review Security Risk The initialization script uses --initialize-insecure flag which creates the root account without password protection Security Risk Root password is explicitly set to empty string, leaving database vulnerable to unauthorized access Configuration Concern Important security settings like default_authentication_plugin are commented out, which may affect authentication security

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Initialize MySQL with secure password generation instead of an insecure blank password The --initialize-insecure flag creates a root user without a password, which is a security risk. Use --initialize instead to generate a secure random root password. bin/mysql9.1.0/init.bat [3] -%~dp0bin\mysqld.exe --initialize-insecure +%~dp0bin\mysqld.exe --initialize Apply this suggestion Suggestion importance[1-10]: 9 Why: Using --initialize-insecure creates a significant security vulnerability by setting up MySQL with no root password. Switching to --initialize is crucial for security as it generates a random root password.	9
	Avoid using empty passwords for root database users Setting an empty root password creates a significant security vulnerability. Set a strong default password or require one during initialization. bin/mysql9.1.0/bearsampp.conf [8] -mysqlRootPwd = "" +mysqlRootPwd = "@MYSQL_ROOT_PASSWORD@" Apply this suggestion Suggestion importance[1-10]: 9 Why: Empty root passwords pose a severe security risk, making the database vulnerable to unauthorized access. Using a placeholder for a required password is a critical security improvement.	9
	Enable explicit secure authentication plugin instead of relying on defaults Enable the default authentication plugin setting to use mysql_native_password for better security and compatibility. bin/mysql9.1.0/my.ini [31] -#default_authentication_plugin=mysql_native_password +default_authentication_plugin=mysql_native_password Apply this suggestion Suggestion importance[1-10]: 7 Why: Explicitly setting mysql_native_password as the authentication plugin enhances security and ensures consistent authentication behavior across different MySQL versions.	7

💡 Need additional feedback ? start a PR chat