summaryrefslogtreecommitdiff
path: root/doc/rst/legacy/reference/fc_verifyrecover/index.rst
blob: 5e50526e0cc2345c68ef3e5f500f1d04fe37a937 (plain)
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
.. _mozilla_projects_nss_reference_fc_verifyrecover:

FC_VerifyRecover
================

`Name <#name>`__
~~~~~~~~~~~~~~~~

.. container::

   FC_VerifyRecover - Verify data in a single recoverable operation.

`Syntax <#syntax>`__
~~~~~~~~~~~~~~~~~~~~

.. container::

   .. code:: eval

      CK_RV FC_VerifyRecover(
        CK_SESSION_HANDLE hSession,
        CK_BYTE_PTR pSignature,
        CK_ULONG usSignatureLen,
        CK_BYTE_PTR pData,
        CK_ULONG_PTR pusDataLen
      );

`Parameters <#parameters>`__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

   ``hSession``
      [in] session handle.
   ``pSignature``
      [in] mechanism to be used for the signing operation.
   ``usSignatureLen``
      [in] handle of the key to be usedn.
   ``pData``
      [out] pointer to the buffer or NULL.
   ``pusDataLen``
      [in, out] pointer to the size of the output buffer, replaced by the length of the signature if
      the operation is successful.

`Description <#description>`__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

   ``FC_VerifyRecover`` verifies data in a single operation where the (digest) data can be recovered
   from the signature. If ``pSignature`` is NULL only the length of the signature is returned in
   ``*pusSignatureLen``.

   A user must log into the token (to assume the NSS User role) before calling ``FC_VerifyRecover``.

.. _return_value:

`Return value <#return_value>`__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

`Examples <#examples>`__
~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

.. _see_also:

`See also <#see_also>`__
~~~~~~~~~~~~~~~~~~~~~~~~

.. container::

   -  `NSC_VerifyRecover </en-US/NSC_VerifyRecover>`__