24 Jun
2012
24 Jun
'12
8:42 p.m.
Hello all,
I think I had forgotten to post an update of the most recent
developments about BCEE S-NET to this list.
1. There is another workaround available, which is more light-weight and
also safer than the proxy solution that I suggested earlier:
https://www.lilux.lu/lilux/mediawiki/index.php/Luxtrust#BCEE
This is a bookmarklet, which you can drag on your bookmark folder, and
then click as soon as you arrive on the broken S-NET page. This will
then fix the applet tag via javascript.
2. Last week I had a conversation with Thierry Tournay from BCEE, and he
assured me that "during next week, the Luxtrust 1.4.1 wrapper will be
deployed, which will fix your problem", i.e. if all goes to plan, it
should work at latest by the end of the month.
Regards,
Alain
22 Aug
22 Aug
7:06 a.m.
New subject: After BCEE, now CCP too uses the faulty 1.4 version of the Luxtrust wrapper
Hello all,
Just for your information, it has come to my attention that CCP now also
uses the buggy 1.4 version of the LuxTrust wrapper.
However, the good news is that my bookmarklet from
http://www.alain.knaff.lu/Luxtrust/bookmarklet.html is able to work
around the problem, just as for BCEE.
I've updated the wiki page at
https://www.lilux.lu/lilux/mediawiki/index.php/Luxtrust#CCP
to take into account this new devolution of the situation.
However, despite the existence of the workaround, it is still useful to
call or mail P&T about the issue, in order to prevent it from degrading
further.
If somebody has good internal contacts with Raiffeisen, it might be
useful to warn them in advance of this buggy version 1.4, apparently
LuxTrust themselves are not warning the banks enough to stay clear of
that version, despite the existence of a 1.4.1 version which no longer
has the bug.
Regards,
Alain
5024
days inactive
5083
days old
1 comments
1 participants
participants (1)
-
Alain Knaff