Sign inTry Free

Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

MD5

On this page

The MD5() function hashes the given string or binary data using the message digest algorithm, version 5.

MD5 has been strongly deprecated as a means of securely signing data, given the multiple weaknesses discovered in the algorithm.

It is present in SingleStore Helios mainly for backwards compatibility and for systems which require a "good enough" hashing function and can tolerate collisions. For a more secure hash function, refer to SHA2.

Note

MD5 is disabled when FIPS mode is enabled (via the ssl_fips_mode engine variable).

A warning is generated when MD5 is used:

SELECT MD5('a');


ERROR 2535 (HY000): SSL fips mode error: FIPS mode ON: MD5 digest is not supported.


SHOW WARNINGS;
+---------+------+------------------------------------------------------------------------+
| Level   | Code | Message                                                                |
+---------+------+------------------------------------------------------------------------+
| Warning | 2535 | SSL FIPS mode error: FIPS mode ON/STRICT: MD5 digest is not supported. |
+---------+------+------------------------------------------------------------------------+

Syntax

MD5(plaintext)

Arguments

  • plaintext: Data to hash.

Return Type

32 lower case hexadecimal digits corresponding to the 128-bit binary hash value.

Examples

SELECT MD5('ohai');
+----------------------------------+
| MD5('ohai')                      |
+----------------------------------+
| 5a73678b7b674005056434a48054707d |
+----------------------------------+

Related Topics

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In