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.

SHA1

On this page

The SHA1() function hashes the given string or binary data using the so-called secure hash algorithm, version 1. SHA1 has been deprecated as a means of securely signing data.

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, see [SHA2].

Syntax

SHA1(plaintext)
SHA(plaintext)

Arguments

  • plaintext: the data to hash.

Return Type

40 lower case hexadecimal digits corresponding to the 160-bit binary hash value.

Examples

SELECT SHA1('ohai'), SHA('ohai');
+------------------------------------------+------------------------------------------+
| SHA1('ohai')                             | SHA('ohai')                              |
+------------------------------------------+------------------------------------------+
| dca51952447d80bd35bf631bc21f06648798b7e0 | dca51952447d80bd35bf631bc21f06648798b7e0 |
+------------------------------------------+------------------------------------------+

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