*** Issue 39382 has been marked as a duplicate of this issue. ***

Hi, Malte,

Chandler and I have committed the fix to the xmlsec08. 

Because we can't test it in the real smartcard device, so I'm afraid that I can
only reassign it to you, instead of marking it as fixed. Sorry. ;-)

Michael

If there is an interim test build, I could help in the testing for access to a
USB token. Otherwise, it's sit and wait for the next m680 snapshot.

rfsalomon,

thanks for that :)

There are some incompatible changes in xmlsec08, so I don't have a build for that.
Would be good if you could confirm when xmlsec08 is integrated (will take some
weeks because of open issues).

MT->FST: We don't have the SmartCard anymore, so I suggest we hope it work, 
and let rfsalomon test in master.

If it doesn't - we don't loose anything...

re-open issue and try to reassign to fst

try to reassign to fst

try to reset resolution to FIXED

I'm available and eager to test. Just let me know when the build is ready.
Tested it on Pavel's m80 build1 but it seems the fix is still not there. I'll
wait for the next build (m81?) to repeat the test.

Wow, quick response :)

Will be in the master when CWS xmlsec08 is integrated, which might be m83.

:) I'm monitoring this issue closely since Digital Signatures are quickly
becoming a big issue here in Brazil with the Federal Government's new guidelines
for electronic documents.

Downloaded Pavel's m83 build and it seems that the fix didn't make it there...
Still waiting.

No bugs found so far, no bad effects discovered.

forgot to mention there it was tested. CWS xmlsec08

Downloaded and tested with m86 build. Couldn't test the functionality because
m86 is unable to find a mozilla user profile. Previous builds were able to find
the user profile without any extra configuration. Is any environment setting
required for m86 to find a valid mozilla profile?

My environment:

SuSE Linux 9.2
Mozilla 1.7.5
MOZILLA_FIVE_HOME=/opt/mozilla/lib

Attempted to open a new issue per Michael Mi's reccomendation. Since the issue
was closed as a duplicate, I'm copying the text over here. I thing this issue
should be reopened.

Once a certificate is stored in Mozilla's Software Security Device, I am able to
sign documents using it. However, certificates stored in hardware devices, such
as a USB Token, are not accessed even though they are correctly configured in
Mozilla and can be used by it to sign e-mails. Since these certificates stored
in hardware are usable in Evolution through libnss, I assume that OOo has still
to implement the interface to access these devices. Is this currently a
restriction or are there plans to implement access to hardware devices though
libnss?

Environment: SuSE Linux 9.2, Java 1.5.0, OOo 2.0 (1.9 m65)

eAladdin eToken Pro

No side effects discovered for the fix so found integrated on Master SRC680 m89