> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/verificacion-de-firmas.md). # Signature verification Signature verification with Editran/FF is carried out at two levels. First, it is checked that the signature is correct in terms of integrity and structure, that it has been made with certificates issued by recognized Certification Authorities, and that they are neither expired nor revoked. Once these validations have been passed, in the signing modes where the signed file is included, it is extracted. Finally, Editran/FF checks that the signers of the file are those expected according to the product configuration profiles, both in identity and in number. As will be seen below, for Editran/FF to be able to carry out this validation of the signatures with respect to the expected signers, it is essential that the signing party provide the validating party with certain information about both the certificates and the signature validation system required that it has used; only in this way can the validating party guarantee that the received signatures continue to meet the criterion originally established by the signing party. --- # 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.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/verificacion-de-firmas.md?ask=&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.