| Alexandre Lision | ddd731e | 2014-01-31 11:50:08 -0500 | [diff] [blame] | 1 | The GNU uCommon C++ secure library component (and the core GNU uCommon C++ |
| 2 | library) is licensed under the GNU Lesser General Public License 3.0 or later. |
| 3 | It is generally believed that openssl can be linked with GNU L-GPL licensed |
| 4 | software, and with GNU GPL licensed software as well, when appearing as a |
| 5 | "default system library" on a target platform. However, we generally recommend |
| 6 | using the GNU tls (gnutls) library build of the GNU uCommon C++ secure library |
| 7 | component rather than openssl unless gnutls is not available for your target |
| 8 | platform of choice. |
| 9 | |
| 10 | We strive to maintain feature parity between the gnutls and openssl crypto |
| 11 | implementations. We may also add nss as a secure backend in the future. |
| 12 | Programming to the GNU uCommon C++ secure api is intended to avoid the need |
| 13 | entirely of using openssl, gnutls, or other library specific functions. This |
| 14 | means the total size of the secure library will grow as we add additional |
| 15 | common features, such as pki support. In the past as there has been no |
| 16 | generally agreed upon crypto library, so developers building new apps would use |
| 17 | a library they already know, or that is best optimized for the platform they |
| 18 | are using. Our goal is to remove this complexity of supporting different |
| 19 | crypto libraries by offering a single API for secure application development. |
| 20 | |