Package Details: autofirma 1.6.5-1

Git Clone URL: (read-only)
Package Base: autofirma
Description: Spanish Government digital signature client
Upstream URL:
Licenses: GPL, EUPL
Submitter: migrev
Maintainer: migrev
Last Packager: migrev
Votes: 14
Popularity: 0.824501
First Submitted: 2017-04-17 07:28
Last Updated: 2019-05-10 11:10

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

mluque commented on 2018-02-21 09:06

Thank you very much for your help, @Musikolo. The PKBUID you have given us works perfectly!

Musikolo commented on 2018-02-21 02:56

Just in case anyone wants to update to the last version (1.6.1 as of today), you can find an updated PKGBUILD at

I hope it helps! ;-)

mluque commented on 2018-02-20 15:46

Efectivamente @Marzal, en este momento "makepkg" falla con el siguiente mensaje de error:

==> Validating source files with md5sums... ... FAILED

==> ERROR: One or more files did not pass the validity check

Marzal commented on 2018-02-03 22:36

La versión 1.6 esta ya publicada a331cc3e2cd3e183f02227eaf701cfc2

Y puesto que el PKGBUILD apunta al currentversion no se si le estará fallando este paquete a la gente que lo este instalando de 0 porque no coincida el md5sum y el pkgver ya que el fichero deb ahora se llama AutoFirma_1_6.deb

ioan commented on 2017-12-15 00:21

@migrev mira este pull ya esta la version para chromium

Bakaur commented on 2017-12-10 08:55

Gracias por su trabajo. ¿Seria posible usarlo en firefox con total seguridad actualmente, aunque haya caducado?

reztho commented on 2017-10-30 09:04

Shouldn't this line be put in an .install file?
java -jar "${pkgdir}"/usr/lib/AutoFirma/AutoFirmaConfigurador.jar

The way you did it, it means at the moment the package's being compiled, it will potentially affect the host system since I don't think you're telling the jar code to go to ${pkgdir} to make its changes.

Not everybody is compiling AUR packages in a chroot, although they should.

Ideally, it should be researched what changes make that jar to revert the operation when uninstalling the autofirma package.

migrev commented on 2017-10-24 09:31

Investigando sobre el asunto las conclusiones son las siguientes:

- El paquete actual funciona sin problema con firefox. He podido firmar varios documentos sin problema y el protocolo afirma:// funciona correctamente.

- Respecto a chrome/chromium, es necesario tener firefox instalado, ya que AutoFirma utiliza el almacén de certificados de éste. El problema es que AutoFirma usa un certificado autofirmado que chrome rechaza, por lo que, aunque xdg-open invoca el servicio correctamente, luego el javascript de la página no consigue establecer conexión por considerarla insegura. Parece que la mejor opción es generar un nuevo certificado correctamente firmado por una CA, pero estoy valorando las opciones.

Procuraré tenerlo funcionando lo antes posible.

Saludos a todos

timofonic commented on 2017-09-15 00:01

They replied me to the two messages. There's a fast translation of their replies. I seriously doubt "060" is going to help me at all.

Will this be standard someday and not require custom software written in Java at all? I'm not a fan of Java.
Good Morning,

We are sorry to inform you that this Center of Attention to Integrators and Developers (CAID) of the MINHAFP, to which only Public Organisms, such as Ministries, Town halls, Universities, etc., but in no case to private individuals or companies.

If you need help, you can get it through the following means intended for citizens:

- By telephone, by calling 060.
- You can also do it via email:
Good Morning:

We inform you that this is the Center for Attention to Integrators and Developers (CAID) of the MINHAFP, which supports various public bodies such as Ministries, City Councils, Universities, but in no case to individuals or companies.

To solve your doubts and incidents you must go to the Customer Service Center (CAU) on phone 060 or through any of the channels indicated at

You can reopen this issue by using the link, entering 348990 in the query or incident identifier field and 323736 in the tracking number.

Yours sincerely.

timofonic commented on 2017-09-14 23:53

@Marzal I tried both Firefox and Chrome, no luck.

I contacted them over several forms on their site, since they closed the issue tracker in the GitHub project (too bad decision).

I needed it urgently for the following site. Fortunately, I managed to set up a VM with Windows (my typical last option, but I'll have it for the future too) and was able to do the signings.

Firefox ESR errors (Nightly outputs nothing):

Chrome errors: