-
-
Save s1037989/513e8c29b89fb4f53b79927c0f7ec0d7 to your computer and use it in GitHub Desktop.
Sign and verify a file using OpenSSL command line tool. It exports the digital signature in Base64 format.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
function gen_keys { | |
[ -z "$1" ] && { echo "Usage: $FUNCNAME passphrase"; return 1; } | |
local passphrase="$1" privatekey=$(mktemp) publickey=$(mktemp) | |
openssl genrsa -aes128 -passout pass:"$passphrase" -out $privatekey 2048 >/dev/null | |
openssl rsa -in $privatekey -passin pass:"$passphrase" -pubout -out $publickey >/dev/null | |
printf "Private Key: %s\nPublic Key: %s\n" $privatekey $publickey | |
} | |
function sign_file { | |
[ -z "$2" ] && { echo "Usage: $FUNCNAME file privatekey publickey"; return 1; } | |
local file="$1" privatekey="$2" publickey="$3" dgst=$(mktemp) sig=$(mktemp) signedfile=$(mktemp) | |
trap "rm -f $dgst $sig" RETURN | |
openssl dgst -sha256 -sign $privatekey -out $dgst $file >/dev/null || return 1 | |
openssl base64 -in $dgst -out $sig >/dev/null || return 1 | |
cat $sig $publickey $file > $signedfile && echo $signedfile | |
} | |
function extract_file { | |
[ -z "$1" ] && { echo "Usage: $FUNCNAME signedfile"; return 1; } | |
local signedfile="$1" sig=$(mktemp) publickey=$(mktemp) dgst=$(mktemp) file=$(mktemp) | |
trap "rm -f $dgst $sig $publickey" RETURN | |
dd skip=0 count=350 if=$signedfile bs=1 of=$sig &>/dev/null || return 1 | |
dd skip=350 count=451 if=$signedfile bs=1 of=$publickey &>/dev/null || return 1 | |
dd skip=801 if=$signedfile bs=1 of=$file &>/dev/null || return 1 | |
openssl base64 -d -in $sig -out $dgst >/dev/null || return 1 | |
openssl dgst -sha256 -verify $publickey -signature $dgst $file >/dev/null && echo $file | |
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Sign a file with a private key using OpenSSL | |
# Encode the signature in Base64 format | |
# | |
# Usage: sign <file> <private_key> | |
# | |
# NOTE: to generate a public/private key use the following commands: | |
# | |
# openssl genrsa -aes128 -passout pass:<passphrase> -out private.pem 2048 | |
# openssl rsa -in private.pem -passin pass:<passphrase> -pubout -out public.pem | |
# | |
# where <passphrase> is the passphrase to be used. | |
filename=$1 | |
privatekey=$2 | |
if [[ $# -lt 2 ]] ; then | |
echo "Usage: sign <file> <private_key>" | |
exit 1 | |
fi | |
openssl dgst -sha256 -sign $privatekey -out /tmp/$filename.sha256 $filename | |
openssl base64 -in /tmp/$filename.sha256 -out signature.sha256 | |
rm /tmp/$filename.sha256 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
# Verify a file with a public key using OpenSSL | |
# Decode the signature from Base64 format | |
# | |
# Usage: verify <file> <signature> <public_key> | |
# | |
# NOTE: to generate a public/private key use the following commands: | |
# | |
# openssl genrsa -aes128 -passout pass:<passphrase> -out private.pem 2048 | |
# openssl rsa -in private.pem -passin pass:<passphrase> -pubout -out public.pem | |
# | |
# where <passphrase> is the passphrase to be used. | |
filename=$1 | |
signature=$2 | |
publickey=$3 | |
if [[ $# -lt 3 ]] ; then | |
echo "Usage: verify <file> <signature> <public_key>" | |
exit 1 | |
fi | |
openssl base64 -d -in $signature -out /tmp/$filename.sha256 | |
openssl dgst -sha256 -verify $publickey -signature /tmp/$filename.sha256 $filename | |
rm /tmp/$filename.sha256 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment