File: index.rst

package info (click to toggle)
thunderbird 1%3A140.4.0esr-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 4,609,432 kB
  • sloc: cpp: 7,672,442; javascript: 5,901,613; ansic: 3,898,954; python: 1,413,343; xml: 653,997; asm: 462,286; java: 180,927; sh: 113,489; makefile: 20,460; perl: 14,288; objc: 13,059; yacc: 4,583; pascal: 3,352; lex: 1,720; ruby: 1,222; exp: 762; sql: 715; awk: 580; php: 436; lisp: 430; sed: 70; csh: 10
file content (75 lines) | stat: -rw-r--r-- 1,749 bytes parent folder | download | duplicates (22)
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_signencryptupdate:

FC_SignEncryptUpdate
====================

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

.. container::

   FC_SignEncryptUpdate - continue a multi-part signing and encryption operation

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

.. container::

   .. code::

      CK_RV FC_SignEncryptUpdate(
        CK_SESSION_HANDLE hSession,
        CK_BYTE_PTR pPart,
        CK_ULONG ulPartLen,
        CK_BYTE_PTR pEncryptedPart,
        CK_ULONG_PTR pulEncryptedPartLen
      );

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

.. container::

   ``hSession``
      [in] session handle.
   ``pPart``
      [in] pointer to the data part.
   ``ulPartLen``
      [in] length of data in bytes.
   ``pEncryptedPart``
      [in] pointer to the location which receives the signed and encrypted data part or NULL.
   ``pulEncryptedPartLen``
      [in] pointer to the length of the encrypted part buffer.

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

.. container::

   ``FC_SignEncryptUpdate`` continues a multi-part signature and encryption operation. After calling
   both ``FC_SignInit`` and ``FC_EncryptInit`` to set up the operations this function may be called
   multiple times. The operation is finished by calls to ``FC_SignFinal`` and ``FC_EncryptFinal``.

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

.. _return_value:

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

.. container::

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

.. container::

.. _see_also:

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

.. container::

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