Search bar offers the following options:
Term presence. The below example searches for documents that
must contain “foo”, might contain “bar” and must not contain “baz”:
+foo bar -baz
Wildcards. The below example searches for documents with words beginning with “foo”:
Search in specific fields. The following search matches all objects
in "twisted.mail" that matches “search”:
Possible fields: 'name', 'qname' (fully qualified name), 'docstring', and 'kind'. Last two fields are only applicable if "search in docstrings" is enabled.
Fuzzy matches. The following search matches all documents
that have a word within 1 edit distance of “foo”:
Results provided by Lunr.js
Handling of RSA, DSA, ECDSA, and Ed25519 keys.
||Constants representing the supported formats of key fingerprints.|
||An object representing a key. A key can be either a public or private key. A public key can verify a signature; a private key can create or verify a signature. To generate a string that can be stored on disk, use the toString method...|
||Raises when unsupported fingerprint formats are presented to fingerprint.|
||Raised when a key isn't what we expected from it.|
||Raised when a public key signature algorithm name isn't defined for this public key format.|
||Raised when an encrypted key is presented to fromString/fromFile without a password.|
||Raised when a passphrase contains Unicode characters that cannot be normalized using the available Unicode character database.|
||This function returns a persistent
||Normalize a passphrase, which may be Unicode.|
This function returns a persistent
The key is loaded from a PEM file in location. If it does not exist, a key with the key size of keySize is generated and saved.
|location:||Where the key is stored.|
|key||The size of the key, if it needs to be generated.|
|A persistent key.|
Normalize a passphrase, which may be Unicode.
If the passphrase is Unicode, this follows the requirements of NIST 800-63B, section 220.127.116.11 for Unicode characters in memorized secrets: it applies the Normalization Process for Stabilized Strings using NFKC normalization. The passphrase is then encoded using UTF-8.
|passphrase:||The passphrase to normalize.|
|The normalized passphrase, if any.|
|if the passphrase is Unicode and cannot be normalized using the available Unicode character database.|