We are doing some testing of Digital Signatures, and once OOo finds them, it
works great.  However it's not very easy to deploy in a large shop with lots of
users.  The issues:

1) It's hardwired to work with Mozilla, not Firefox.  It won't find Firefox
signatures unless you point a variable to them.

2) Users don't have the ability to configure this on their own, and it can't be
automated in a script at startup because some users keep multiple
Firefox/Mozilla profiles which all create their own sub-directories.

3) In our case, Firefox doesn't even run on the same server as Openoffice.  OOo
has no way to access the files except doing something like NFS which is not ideal.

4) Everything should be much easier to implement for system admins.  Deploying
this with hundreds of users would take a LOT of staff time.

It's fine that OOo looks for Mozilla certificates, anything automated is
excellent.  But there should also be a way INSIDE of Openoffice to allow users
to also merge in their own .p12 files and add them to the list of available
signatures.  This would work in the same way that Cups and OOo printers are
merged together at startup.....Mozilla AND OOo built certificates would merge
into one list.  Then we would simply generate files for the users, and give them
instructions for how to import them into OOo.

Thanks for consideration.