Cita:
Empezado por Neftali [Germán.Estévez]
|
Hola a todos.
Al final hablando con SecureBlackBox me han dado la siguiente solución.
Cita:
Your version of SecureBlackbox used a “DRU” approach to incorporate the SecureBlackbox product DLL into your application and load it manually in run time. That was an efficient and handy approach, but it proved to have one drawback. Certain variants of the operation system and antimalware apps take that approach suspiciously, and stop the applications from loading the DLL in that way right in the middle of the process (effectively, by making the application crash). The behaviour you are observing looks very similar to that.
That’s why we eventually stopped offering that option and suggested to always ship the SecureBlackbox DLL in the “normal” way, by deploying it alongside the application. This eliminates any side effects caused by DEP and anti-malware software.
To fix the issue on your side, please do the following two things:
1) Define USESECUREBLACKBOXDLL globally in your project settings.
2) When deploying your application, please put the SecureBlackbox20.dll file (you will find it in the \lib directory in the SBB folder) alongside your application’s executable
|
Lo he probado y funciona correctamente.
Ahora el problema lo tengo a la hora de firmar el fichero con sbxXAdESSigner1.Sign(); que despues de cargarle todos los parametros me sale el siguiente error.
Cita:
1048581 The certificate does not have a associated private key
|
El certificado le he puesto uno nuestro y le pasa lo mismo. Por algún motivo no puede acceder a la clave privada de los certificados.
Un Saludo.