Bug #91828 Bad handshake since 8.0.12
Submitted: 30 Jul 2018 8:38 Modified: 14 Aug 2018 21:07
Reporter: Flo Bayer Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Documentation Severity:S3 (Non-critical)
Version:8.0.12 (64 bits) OS:Microsoft Windows (8.1 Pro)
Assigned to: CPU Architecture:x86 (i7-4770)
Tags: handshake, tunnel, workbench

[30 Jul 2018 8:38] Flo Bayer
Description:
Since I have updated MySQL Workbench to 8.0.12 (today) I got a 'bad handshake' error when connecting to a server; the connection the all other servers works fine.
This (old) server runs with Ubuntu 10.04.4 LTS and MySQL 5.1.73.

The older version of MySQL Workbench (6.3?) worked properly and without any errors or problems.

Sine 8.0.12 I got the following error:
Cannot Connect to Database Server
Your connection attempt failed for user 'root' from your host to server at 127.0.0.1:3306:
Bad handshake

When I try to connect via right click on the connection and then "Start command line client", I'll get a 'ERROR 1043 (08S01): Bad handshake' after entering the MySQL password.

Connecting to a Ubuntu 12.04.1 with MySQL 5.5.54 works still fine.

Thanks!

How to repeat:
Take the current MySQL Workbench client for Windows (8.0.12) and try to connect to a Ubuntu 10.04.4 LTS with MySQL 5.1.73.
[31 Jul 2018 6:26] Flo Bayer
screenshot from "Start Command Line Client"

Attachment: screenshot-000785.png (image/png, text), 3.84 KiB.

[31 Jul 2018 6:26] Flo Bayer
screenshot from "Open Connection"

Attachment: screenshot-000783.png (image/png, text), 8.60 KiB.

[31 Jul 2018 7:05] Mike Lischke
Server 5.1 is not a supported MySQL version for Workbench. Supported versions are 5.5, 5.6, 5.7 and 8.0.

Additionally, there seems to be an SSH problem. The log contains "09:57:02 [INF][      SSHCommon]: libssh: ssh_packet_userauth_failure ssh_packet_userauth_failure: Access denied. Authentication that can continue: publickey,password", which points to an authentication problem.
[31 Jul 2018 7:16] Chiranjeevi Battula
Hello Flo Bayer,

Thank you for the bug report.
Per Oracle's Lifetime Support policy, as of December 31, 2013, MySQL 5.1 is covered under Oracle Sustaining Support. Users are encouraged to upgrade to MySQL 5.6.
EOL Announcements : https://www.mysql.com/support/eol-notice.html

Thanks,
Chiranjeevi.
[31 Jul 2018 7:19] Flo Bayer
Yep, I think so, too.
But even if I choose "Use SSL" -> "No" it won't work.

MySQL Workbench 6.3 makes this connection easily. Same connection, same settings.
[31 Jul 2018 7:21] Flo Bayer
Okay, thanks for help anyway!
[9 Aug 2018 16:38] Bob Krieter
Based on support comments, please change the wording on page https://dev.mysql.com/doc/refman/8.0/en/workbench.html

It currently says "MySQL Workbench provides a graphical tool for working with MySQL servers and databases. MySQL Workbench fully supports MySQL versions 5.1 and above"

If 5.1 is not supported (indeed, it did not work for me either with 8.0), then the 8.0 page should not say that 5.1 is supported.
[9 Aug 2018 20:49] MySQL Verification Team
Thank y6ou for the feedback and you are right need to correct the documentation from:

"MySQL Workbench provides a graphical tool for working with MySQL servers and databases. MySQL Workbench fully supports MySQL versions 5.1 and above"

to

"MySQL Workbench provides a graphical tool for working with MySQL servers and databases. MySQL Workbench fully supports MySQL versions 5.5 and above"
[14 Aug 2018 21:07] Christine Cole
Posted by developer:
 
MySQL Server version adjusted to 5.5 and higher in documentation. 
Thank you for the bug report.
[18 Oct 2018 17:04] Malcolm Cook
I am happy to see reported resolution but must report that connecting with

    My SQL workbench 8.0.12 (Windows)

to

   mysql  Ver 15.1 Distrib 5.5.50-MariaDB, for Linux (x86_64) 

I still get the bad handshake error using connection that succeeds under version 6.0.3 of the workbench.

My log (%AppData%\MySQL\Workbench\wb.log) reads:

11:09:07 [ERR][SQL Editor Form]: SqlEditorForm: exception in do_connect method: Exception: Bad handshake
11:09:07 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: Bad handshake
11:09:07 [ERR][  GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.Bad handshake
11:09:07 [ERR][SQL Editor Form]: SQL editor could not be connected: Bad handshake
11:09:07 [ERR][SQL Editor Form]: Your connection attempt failed for user 'cvt' from your host to server at django:3306:
  Bad handshake

Please:
1 Check that mysql is running on server sssss
2 Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the uuuu has rights to connect to sssss from your address (mysql rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for sssss connecting from the host address you're connecting from
[17 Jan 2019 11:25] MySQL Verification Team
Bug #93960 marked as duplicate of this one
[25 Oct 2019 10:36] MySQL Verification Team
Bug #97373 marked as duplicate of this one