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

[Abuse SSL] Add info about loading variable #3194

Open
3 tasks done
Brazilianian opened this issue Dec 26, 2024 · 1 comment
Open
3 tasks done

[Abuse SSL] Add info about loading variable #3194

Brazilianian opened this issue Dec 26, 2024 · 1 comment
Labels
question use for asking information about a functionality or behavior

Comments

@Brazilianian
Copy link

Brazilianian commented Dec 26, 2024

Prerequisites

  • I read the Deployment and Setup section of the OpenCTI documentation as well as the Troubleshooting page and didn't find anything relevant to my problem.
  • I went through old GitHub issues and couldn't find anything relevant
  • I googled the issue and didn't find anything relevant

Description

I looked at abuse-ssl connector and found out that there is no any information about update_existing_data variable in README.md, config.yml.sample and docker-compose.yml.

self.update_existing_data = get_config_variable(

It would be really great to add additional information in sample files.

Environment

  1. OS (where OpenCTI server runs): Ubuntu 22.04
  2. OpenCTI version: OpenCTI 6.4.5
  3. OpenCTI client: python
  4. Other environment details: -

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Open open-ssl.py file, in __init__ function you can see loading update_existing_data variable
  2. Look at the file README.MD, config.yml.sample, docker-compose.yml. There is no any information

Additional information

I also can create Pull Request to fix it.

@Brazilianian Brazilianian added needs triage use to identify issue needing triage from Filigran Product team question use for asking information about a functionality or behavior labels Dec 26, 2024
@romain-filigran
Copy link
Member

Hi @Brazilianian. This configuration variable is obsolete and no longer has any effect. It should be removed from the code to avoid confusion.

@romain-filigran romain-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question use for asking information about a functionality or behavior
Projects
None yet
Development

No branches or pull requests

2 participants