Package Details: eid-mw 4.1.18-1

Git Clone URL: (read-only)
Package Base: eid-mw
Description: The eID middleware for the Belgian eID
Upstream URL:
Licenses: LGPL3
Submitter: xdevla
Maintainer: Emil
Last Packager: Emil
Votes: 32
Popularity: 0.514404
First Submitted: 2012-02-14 10:56
Last Updated: 2016-06-19 06:43

Latest Comments

plenaerts commented on 2016-06-18 07:01

Updating version to 4.1.18 and md5sum to d27be9ac6f63e864c539c50b3db76763 works.

git diff:

wouter commented on 2016-05-20 08:46

@olive A XPI is shipped (in plugins_tools/xpi/src/ inside the tarball) but not installed by the Makefile.

Chromium doesn't work due to

olive commented on 2016-05-04 07:31

The add-on to be able to use authentification with firefox works but we had to force-enable it by setting xpinstall.signatures.required as false; then by enabling the add-on). This is a little worrying. What's the real cause of that? Does a signed version of the add-on exists.

By the way, I have been unable to authenticate with chromium. Does anyone have an idea?

BartVG commented on 2016-02-10 14:35

You could also add this key by using gpg in the terminal, for example:

gpg --keyserver hkp:// --recv-keys 824A5E0010A04D46

If you need to use a proxy you could use:

gpg --keyserver-options http-proxy=<proxy>:<proxyport> --keyserver hkp:// --recv-keys 824A5E0010A04D46

herremaw commented on 2016-01-08 16:25

'makepkg' complains about the PGP signature.

I have managed to fix that problem by installing 'seahorse'. Then from within 'seahorse' I have used the menu 'Remote → Find Remote Keys ...' and then looked for 'belgian'. That search returns among others the PGP keys: 'Belgian eID Automatic Signing Key - Continuous builds' and 'Belgian eID Automatic Signing Key - Offical releases'.

I have imported both these keys, but I suppose the 'Continous builds' would be sufficient for this package. Then, after setting 'trust' for these keys, 'makepkg' runs successfully.

Alad commented on 2015-10-28 18:46

Glad to see both GPG signing and SSL cert were fixed. Keep up the good work.

Emil commented on 2015-10-23 12:19

The developer contacted me, the fingerprint can be found here:

Emil commented on 2015-10-23 00:43

See the comment below you, they are using a different key than the official release key. I'll ask them where we can verify this key.

noplomplom commented on 2015-10-22 19:02

PGP signature cannot be verified. When trying to import the public key 824A5E0010A04D46, the fingerprint does not match the one mentioned on the developer's website.

silvermonk commented on 2015-09-23 14:55

Alad, I just replaced the SSL Cert.. (blushes).

Wouter (see IRC) also reminds us that the sources are now GPG signed (with the continuous build key, not the official release key)

All comments