> 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-lite-v7-open-en/linux/clienteff/modos-de-uso-para-verificar-firmas/consideraciones-con-respecto-a-todos-los-modos-de-firma.md).

# Considerations regarding all signing modes

When the signature file includes the signed data file (modes XADES\_DETACHED\_INTERNO\_IMPLICITO, XADES\_ENVELOPED, XADES\_ENVELOPING\_IMPLICITO, XADES\_DETACHED\_INTERNA\_EXPLICITA\_UNFICH and PKCS7\_ATTACHED), the verification process will extract the data file included in the signature into the data directory specified in the application profile. In the other modes, the data file must have been received together with the signature file and be located in the data directory when validation is performed.

During the verification process, it is created in *\[application data directory]/TMP.XD* a file with the same name as the data file followed by the .ctrl extension. It contains a first line reporting the result of the verification and then as many lines as certificates have signed the file. Each of these lines contains the certificate DN preceded by ‘S’ if that certificate is found in the application profiles, or by ‘N’ otherwise. This information is of interest when the process ends with code 6 (Incorrect signature error due to profiles), see section **4.4.**


---

# 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-lite-v7-open-en/linux/clienteff/modos-de-uso-para-verificar-firmas/consideraciones-con-respecto-a-todos-los-modos-de-firma.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.