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
class SSHPublicKeyDatabase: (source)
Checker that authenticates SSH public keys, based on public keys listed in authorized_keys and authorized_keys2 files in user .ssh/ directories.
||Retrieve files containing authorized keys and check against user credentials.|
||Return a list of
||Validate credentials and produce an avatar ID.|
||A list of sub-interfaces of
||Check whether the credentials themselves are valid, now that we know if the key matches the user.|
Retrieve files containing authorized keys and check against user credentials.
Return a list of
FilePath instances for authorized_keys files which might contain information about authorized keys for the given credentials.
On OpenSSH servers, the default location of the file containing the list of authorized public keys is $HOME/.ssh/authorized_keys.
$HOME/.ssh/authorized_keys2 is also returned, though it has been deprecated by OpenSSH since 2001.
|A list of |
Validate credentials and produce an avatar ID.
|credentials||something which implements one of the interfaces in credentialInterfaces.|
Check whether the credentials themselves are valid, now that we know if the key matches the user.
|valid||A boolean indicating whether or not the public key matches a key in the user's authorized_keys file.|
|credentials:||The credentials offered by the user.|
|The user's username, if authentication was successful.|
|(as a failure) if the key does not match the user in credentials. Also raised if the user provides an invalid signature.|
|(as a failure) if the key matches the user but the credentials do not include a signature. See |