Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy with VT module #897

Merged
merged 2 commits into from
Mar 14, 2024
Merged

Proxy with VT module #897

merged 2 commits into from
Mar 14, 2024

Conversation

DocArmoryTech
Copy link
Contributor

Type of change

Modified the vt.py module so that the vt.Client reads the trustenv parameter from the module's config section if present.

Current functionality sees the trustenv parameter to vt.Client default to False. Unless the new config parameter is used, False remains the default.

Select the type of change(s) made in this pull request:

  • [ x] Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation (change or fix to documentation)

Fixes #896

Proposed changes

  • add a trustenv parameter to the vt module's config
  • modified vt module to read and use a trustenv parameter from the module config file (if present)

Added "trustenv" config parameter for the VT module
Modified the vt.Client instantiation to optionally read a value for trustenv from the modules config section.
@Rafiot Rafiot merged commit c4a79c7 into Lookyloo:main Mar 14, 2024
@@ -33,7 +33,7 @@ def module_init(self) -> bool:
self.logger.info('Not enabled')
return False

self.client = vt.Client(self.config['apikey'])
self.client = vt.Client(self.config['apikey'], trustenv=bool(self.config['trustenv'], False))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just FYI, the correct name of the parameter is trust_env, not trustenv. And bool(self.config['trustenv'], False) isn't a valid syntax. I guess you wanted to do something like self.config.get('trustenv', False)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😱 so sorry! Thanks for the catch!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries, it is fixed in the repo ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: push to misp silently fails accessing VT behind a proxy
2 participants