C++14 for 3rd party integration

We need to build C++14 library for third party Integration

Acceptance criteria

• storing the certification files with the private keys
• makes request to the back-end using the C++14 library (we need automatically generate calls/requests to the back-end functions)
• generates certificates via C++ library
• signing of emails
• signing of documents

Note: We need to check the storing the certification files

Related tickets :

• #17 #18 #19 #20

changed title from C++ lib for 3th party integration/ to C++ lib for 3th party integration

JFR and not lose this info:

he closest existing case I can think of is importer libraries for obscure old document formats. Based on that, the spec is roughly the following:

• either we only build the source files with our own build system, or the build system is autotools, producing a shared library

• baseline for the C++ language features used is documented at https://cgit.freedesktop.org/libreoffice/core/tree/README.md#n30

• try to minimize external dependencies, though using external libraries which are already bundled in LibreOffice is not a problem. I imagine the followings are of interest:

  • curl (with SSL/nss enabled) is OK
  • boost is OK
  • full list of externals is at https://cgit.freedesktop.org/libreoffice/core/tree/external

• license: Mozilla Public License v2 is preferred, BSD/MIT is also OK. LGPL and especially GPL is considered problematic.

And then the setup would be that you provide a C++ library, and we use that from LibreOffice (so you maintain a stable API, not the other way around).

Publishing the code e.g. on github and attaching a stable release tarball to a release tag is fine, we can fetch the source code from there.

We plan having both. Software certificates for everyone and hardware tokens for users who want better security

In this case -- LibreOffice already links to nss on Linux/macOS, and to crypt32.dll / ncrypt.dll on Windows; so if you use NSS and/or Cryptography API: Next Generation (CNG) on Windows, then that would fit our existing crypto usage.

changed the description

changed title from C++ lib for 3th party integration to Golang lib with C++ bindings for 3th party integration

Upper comment is only for the integration with LibreOffice Desktop.

changed title from Golang lib with C++ bindings for 3th party integration to Golang lib with C++ bindings for 3rd party integration

changed the description

added P5 label

added epics feature labels

added S3 label

changed title from Golang lib with C++ bindings for 3rd party integration to C++14 for 3rd party integration

changed the description

added P2 label and removed P5 label

added InPreparation label

unassigned @alexander.holodov

changed milestone to %v0.6

changed the description

As this is quick big task and in order to make it clear what we want to complete we need to split it

changed the description

changed the description

removed milestone

added ReadyForDev label

removed InPreparation label

assigned to @gospodin.bodurov

changed the description

assigned to @daniel.lyubomirov and unassigned @gospodin.bodurov