> 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/windows/clienteff/modos-de-uso-para-firmar-ficheros/firma-sin-aplicacion.md).

# Signing without an application

To perform file-by-file signatures, without using an application defined in EditranFF:

```
clienteff -firma -fichero [path of file to be signed] -alias [aliases of the signers,
separated by ','] [-destino [destination directory path]]
```

Where:

* **-fichero \[path of file to be signed]:** path to the file to be signed. The metacharacters ‘\*’ and ‘?’ are supported to refer to a set of files.
* **-alias \[aliases of the signers, separated by ‘,’]:** aliases of the local users who will sign. They must exist in the configuration.
* **\[-destino \[destination directory path]]:** optional pair of parameters. If not specified, the signature file will be placed in the same directory as the input file with the name \[data file].xsig. If specified, the directory must exist.

The remaining required configuration (Signing mode, certificate path, etc.) is taken from the default parameter data defined in the configuration.

For example, to sign the file *ficheropruebas.xml* located in *C:/files* with the user *usuario1* and the resulting signature is to be saved in the directory *C:/files/firmas*, the following call will be made:

```
clienteff -firma -fichero C:/files/ficheropruebas.xml -alias usuario1 -destino
C:/files/firmas
```


---

# 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/windows/clienteff/modos-de-uso-para-firmar-ficheros/firma-sin-aplicacion.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.