The Bourne shell is everywhere. It is part of the most basic Linux install. You will find it on the biggest SPARC machines down to a Raspberry Pi. It is nice to know it will always be there. Unlike other, more complex scripting environments such as Perl and Python, it doesn’t require any additional dependencies to be installed.

Anyone that has automated a MySQL task using a Bourne shell such as Bash will be familiar with the following message:

Warning: Using a password on the commandline interface can be insecure.

This semi-ominous warning describes a security flaw in passing credentials on a process command line. Any unprivileged user on the system can use a command like ps aux to find these credentials. While the MySQL shell has added some additional protections to hide these credentials, other information such as database user names, host names, ports and sockets can still be determined by process scanning.

The recommended approach to get around this warning is to use a configuration file to store these credentials. However, in the case of a self-contained script, we may not want to require the user to create a credential file. It would need to be maintained, and might interfere with other tools that use the MySQL shell. For creating automated tools in the Percona Development Services department, I came up with a couple of methods for integrating the MySQL shell into Bash (or any other Bourne Shell) securely.

This first script demonstrates the shell function mysql_exec(). This is for use with small queries that are normally passed to the MySQL shell via the -e parameter.

#!/bin/sh
# call mysql client from shell script without
# passing credentials on command line
# This demonstrates small single queries using
# the -e parameter.   Credentials and connection
# info are sent through standard input.
# david . bennett @ percona . com - 9/24/2016
mysql_user=root
mysql_password=password
mysql_host=127.0.0.1
mysql_port=3306
mysql_database=test

mysql_exec(){
    local query="$1"
    local opts="$2"
    mysql_exec_result=$(
    printf"%s\n"\
    "[client]"\
    "user=${mysql_user}"\
    "password=${mysql_password}"\
    "host=${mysql_host}"\
    "port=${mysql_port}"\
    "database=${mysql_database}"\
|    mysql--defaults-file=/dev/stdin"${opts}"-e"${query}"
    mysql_exec"select 'Hello World' as Message"
    echo"${mysql_exec_result}"

Sometimes, you need to process too many queries to pass on the command line. In this case, there is another technique for passing the credentials.

mysql_exec_from_file()c {
    local query_file="$1"
    local opts="$2"
    local tmpcnf="$(mktemp)"
    chmod600"${tmpcnf}"
    printf"%sn"
    "[client]"
    "user=${mysql_user}"
    "password=${mysql_password}"
    "host=${mysql_host}"
    "port=${mysql_port}"
    "database=${mysql_database}"
    >"${tmpcnf}"
    mysql_exec_from_file_result=$(
    mysql--defaults-file="${tmpcnf}""$opts"<"${query_file}"
    rm"${tmpcnf}"

While other languages may offer cleaner ways to access your MySQL database, you’ll always know that you’ll be able to execute your shell-based MySQL job scripts across all of the Unix machines in your enterprise.

You can download these scripts directly from my GitHub account.