pynessus
Client for the xml rpc interface of the Nessus vulnerability scanner v5+.
Methods mirror what is in the official API at http://static.tenable.com/documentation/nessus_5.0_XMLRPC_protocol_guide.pdf in a pythonic way so that you don’t have to care about json or xml.
Ongoing work
Features are being added, not all the API is mapped yet. As all the api calls kind of look the same, it is braindead work so pull requests are more than welcome.
Example usage
with Nessus('127.0.0.1:8443') as nes:
nes.Login('admin', 'pass$%&(#'%#[]@:')
logging.info('Feeds: %s', nes.Feed())
All calls can also be done asynchronously if needed:
with Nessus('127.0.0.1:8443') as nes:
def LoginCallback(result, error=None):
if error:
logging.warning('Error while logging: %s', error)
return
logging.info('Correcty logged in: %s', result)
future = nes.Login('admin', 'pass$%&(#\'%#[]@:', callback=LoginCallback)
futures.wait([future])
# At this point the LoginCallback is sure to have been called.
Metadata
Release files for pynessus 0.9.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pynessus-0.9.1.zip | 10.0 kB | Without provenance | Details for pynessus-0.9.1.zip |
Release files / pynessus-0.9.1.zip
| Download URL | pynessus-0.9.1.zip |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0aba6e0f52fd5ecfc6f25b9791b528a425d09f92f0e7fd0d3f4e4f400b07de9
|
|
BLAKE2b-256 checksum How to use checksums |
5003336b36ddbbb7de5effb1195a6511fa205e01373168448d6e8eb721572add
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pynessus 0.9.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.