Hi Joel,
The El Capitan OS X release changed some things requiring changes in
security-related software for which we've created an updated version of
the middleware. In addition, the update of OS X to El Capitan may move
some settings around which in the case of our middleware means it will
break.
Our most recent release, which is available on
eid.belgium.be today (and
in fact has been since a number of weeks now), should fix all those issues.
As for Adobe Reader, a few of the changes required for El Capitan have
unfortunately caused an incompatibility issue with Adobe Reader on OS X.
A fix for that has now been implemented and should be available this
week (hopefully later today); look for version 4.1.9.
As a general rule, whenever you update OS X (to a new major version, not
minor security-related updates), it makes sense to check if there is an
update of the middleware as well, and if so, to update that too. We do
check if changes are required whenever/before Apple releases a new
version of OS X, and when that is the case we update our middleware, but
we can obviously not be expected to support operating system versions
that didn't exist yet when you downloaded the middleware...
Regards,
On 19-10-15 23:35,
jo...@redilio.us wrote:
> Every 3 months, I spend over an hour battling the middleware, plugins
> and Adobe Reader to fill my VAT returns. This is getting old... With the
> release of El Capitan, I can't even sign documents at all on OS X anymore.
>
> After years of eID being in place, the situation for me is just appalling:
>
> * OS X (El Capitan):
> o Chrome (46): no login at all
> o Safari: no login at all
> o Firefox: no signing
> o Adobe Reader 11: PKCS error 0x5
> o Adobe Acrobat Reader DC: PKCS error 0x6
> * Windows 10:
> o Chrome (46): no signing
> o Edge: no signing
> o Reader DC: signing, with warning about document signature
>
> Seems to me the only working setup is being on Windows and using
> external signing in Adobe Reader. Fucking seriously?
--
Wouter Verhelst