> For the complete documentation index, see [llms.txt](https://docs.talsec.app/freerasp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talsec.app/freerasp/freerasp/wiki/getting-signing-certificate-hash.md).

# Getting Signing Certificate Hash

This guide provides step-by-step instructions for getting the Base64-encoded signing certificate hash for your Talsec configuration.

## What is Signing Certificate Hash?

All Android apps must be signed with a digital certificate before installation. The **signing certificate SHA-256 hash in Base64 form** - which we'll refer to as the **hash** for short, also known as a fingerprint -is the certificate's unique identifier, crucial for security and integrity. The Talsec SDK uses this hash for [app tampering detection](/freerasp/freerasp/wiki/threat-detection/app-tampering-detection.md).

<details>

<summary>What the Signing Certificate Hash Guarantees?</summary>

The hash guarantees that:

* The app's **origin is verified**, preventing malicious actors from distributing fake or modified versions.
* Only the **original developer can provide updates**, ensuring a secure upgrade path.
* Third-party services and APIs can **authenticate the app before granting access**.

</details>

## Choose Your Signing Method

The first step is to determine which app signing method you're using.

If **you're using Google Play App Signing**, a very common practice for Android App Bundles (AAB) distribution, your upload key and distribution key are distinct. So, be sure to use the app signing certificate key from the Google Play Console. Proceed with the [**Google Play App Signing Method**](/freerasp/freerasp/wiki/getting-signing-certificate-hash/google-play-app-signing-method.md).

If **you're managing your own signing key (Manual App Signing)**, you'll need to generate the hash yourself from your keystore, proceed with the [**Manual App Signing Method**](/freerasp/freerasp/wiki/getting-signing-certificate-hash/manual-app-signing-method.md).

Continue with the method that matches your signing process ➡️


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talsec.app/freerasp/freerasp/wiki/getting-signing-certificate-hash.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.