MySQL and Heatwave Summit Presentation

MySQL and Heatwave Summit Presentation

Last week I had the opportunity to speak at the MySQL and Heatwave Summit in San Francisco.

I discussed the impact of the new MySQL 8.0 default caching_sha2_password authentication, replacing the mysql_native_password authentication that was the default for approximately 20 of the 30 years that MySQL has existed. The new authentication plugin implements multiple strategies to improve on the insecure previous approach including using SHA256, multiple iterations and password salts.

As with any presentation, while you may have solid knowledge on any given topic, it was great for the audience to share .

Thanks Fred for informing me of print_identified_with_as_hex variable . I was unaware of this flag to address the SHOW CREATE USER issue I presented in my slides. I also did not cover in my presentation the impact of TLS versions being deprecated and removed in MySQL 8.0.x versions. Thanks Mark for reminding me. For more information read the documentation on encrypted-connection-protocols-ciphers .

SQL > show global variables like 'print%'; 
+------------------------------+-------+ 
| Variable_name                | Value | 
+------------------------------+-------+ 
| print_identified_with_as_hex | OFF |
+------------------------------+-------+

You can find a copy of my slides on my presentations page.

Tagged with: Authentication MySQL Upgrades

Related Posts

Improving container security in your CI/CD pipeline

At PyCon AU 2026 , the presentation Your Python container is 90% stuff you didn’t ask for by Scott Norris at Chainguard really exposed the impact of being lazy in container management for security purposes.

Read more

My take on PyCon Australia 2026

PyCon AU 2026 held in Brisbane this week was a five day event for the Python community. With specialized tracks and dedicated tutorial and engineering days there was a wide variety of content available.

Read more

Fixing Old Software Bugs Without Thinking

I previously came across an issue in my benchmarking work where I relied on the Latency Histogram section of sysbench output. On Linux it worked fine — I generally ran my workload there, so it never mattered.

Read more