Hmm.... The mysql workbench is going to expect to run the mysql authentication handshake... so you would have to jump in the middle of the tcp stream and substitute the actual password, no? See here for how a new forward tunnel can be run from a client
https://github.com/glycerine/sshego/blob/05503dd206cf9022d58b7c6ea04e112e65f40659/sshutil.go#L392 and then also instead of the simple io.Copy at https://github.com/glycerine/sshego/blob/05503dd206cf9022d58b7c6ea04e112e65f40659/shovel.go#L66 you could filter for the credentials and substitute the actual correct one for the user. This would be client side though, so users could use strings on the binary to find the actual passwords. But you could also intercept the tcp pump on the server side I think; here: https://github.com/glycerine/sshego/blob/05503dd206cf9022d58b7c6ea04e112e65f40659/direct.go#L73 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAPNEFAb4fwZciCRytgUzm4gFcBQ33u_0dmVf2bHYAPHyBSW5wA%40mail.gmail.com.
