1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
nng_tls_config_cert_key_file(3)
===============================
:doctype: manpage
:manmanual: nng
:mansource: nng
:manvolnum: 3
:icons: font
:source-highlighter: pygments
:copyright: Copyright 2018 Staysail Systems, Inc. <info@staysail.tech> \
Copyright 2018 Capitar IT Group BV <info@capitar.com> \
This software is supplied under the terms of the MIT License, a \
copy of which should be located in the distribution where this \
file was obtained (LICENSE.txt). A copy of the license may also \
be found online at https://opensource.org/licenses/MIT.
NAME
----
nng_tls_config_cert_key_file - load own certificate and key from file
SYNOPSIS
--------
[source, c]
-----------
#include <nng/nng.h>
int nng_tls_config_cert_key_file(nni_tls_config *cfg, const char *path,
const char *pass);
-----------
DESCRIPTION
-----------
The `nng_tls_config_cert_key_file()` function loads a certificate (or
certificate chain) and a private key from the file named by 'path'.
The file must contain both the https://tools.ietf.org/html/rfc7468[PEM]
encoded certificate and associated private key, which will be used when
establishing TLS sessions using 'cfg'. It may contain additional certificates
leading to a validation chain, with the leaf certificate first.
There is no need to include the self-signed root, as the peer
will need to have that already in order to perform it's own validation.
The private key may be encrypted with a password, in which can be supplied in
'pass'. The value NULL should be supplied for 'pass' if the key is not
encrypted.
On servers, it is possible to call this function multiple times for the
same configuration. This can be useful for specifying different parameters
to be used for different cryptographic algorithms.
RETURN VALUES
-------------
This function returns 0 on success, and non-zero otherwise.
ERRORS
------
`NNG_ENOMEM`:: Insufficient memory is available.
`NNG_EBUSY`:: The configuration 'cfg' is already in use, and cannot be modified.
`NNG_EINVAL`:: The contents of 'path' are invalid.
`NNG_ENOENT`:: The file named by 'path' does not exist.
`NNG_EPERM`:: The file named by 'path' cannot be opened.
SEE ALSO
--------
<<nng_strerror#,nng_strerror(3)>>,
<<nng_tls_config_alloc#,nng_tls_config_alloc(3)>>,
<<nng_tls_config_own_cert#,nng_tls_config_own_cert(3)>>,
<<nng#,nng(7)>>
COPYRIGHT
---------
Copyright 2018 mailto:info@staysail.tech[Staysail Systems, Inc.] +
Copyright 2018 mailto:info@capitar.com[Capitar IT Group BV]
This document is supplied under the terms of the
https://opensource.org/licenses/MIT[MIT License].
|
