https://bugs.freedesktop.org/show_bug.cgi?id=87030
Markus Wernig <pub...@wernig.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markus.mohrhard@googlemail.
| |com
--- Comment #1 from Markus Wernig <pub...@wernig.net> ---
> As I see it, there are two possible ways forward to get this stuff to work on
> Windows:
>
> 1) Set up a NSS database also on Windows. One would think there is a way to
> get the stuff to be added to that out of the Windows certificate store, using
> Windows APIs, and then store it in the database, using NSS APIs. Make sure to
> call NSS_Init() with the path to this database. Then the PDF signing code
> needs no change.
>
> 2) Add a Windows-specific implementation of the PDF signing. It is a single
> function, as far as I can see, PDFWriterImpl::finalizeSignature(), that needs
> ifdefs. This probably makes more sense. Presumably one just needs to figure
> out the right WinCrypt APIs to use instead of the NSS APIs. The concepts
> should be fairly similar, one hopes. It shouldn't be more than a handful
> function calls, knock on wood.
I think that the signatures should work with both methods. If the user
configures a NSS store under Windows in Tools->Options->Security->Certificate
Path it should work as well as when the default Keystore is used.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
