How to use Detached Public-Key Signature Verifier
- Supply the what to verify and text using the supported input described beside the controls.
- Review the selected options and the declared scope, then run the detached signature verifier.
- Read the result and unresolved findings before downloading or sharing a report. The original input is not changed.
Example: Detached Public-Key Signature Verifier
Verify an exact local file/message and detached signature with a supplied public key. This example uses synthetic public data.
Options
- Message source
- Choose the supported local-file or text workflow. Do not copy a file into text mode when its exact original bytes matter.
- Signature encoding
- Use the explicitly selected encoding. Encoding is representation; changing it must not change the decoded signature bytes.
Supported inputs and limits
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
Verify the same bytes that were signed
A file is verified as its exact bytes. Text mode encodes the entered text as UTF-8, so line endings, spaces and punctuation can change the result. A correct digest is useful for comparing the artifact, but the digest alone does not authenticate it. Establish the public key’s source separately.
Questions about Detached Public-Key Signature Verifier
Why can copied text fail?
Copying can change line endings or spaces. Verify the original file when the signature was made over file bytes.
Is the byte hash a signature?
No. A digest does not identify its publisher. The signature check uses your separately supplied public key.
Are files uploaded?
No. The tool reads the selected file locally in the browser.