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

Feature Request: #58

Open
1 task done
aryabharat opened this issue Jan 19, 2024 · 0 comments
Open
1 task done

Feature Request: #58

aryabharat opened this issue Jan 19, 2024 · 0 comments

Comments

@aryabharat
Copy link

Is your feature request related to a problem? Please describe.

The misp-stix utilizes misp-lib-stix2, a fork derived from the stix2 project. Challenges arise when concurrently employing pymisp, which relies on the official stix2 package. Notably, conflicts emerge due to the identical naming of the stix2 module in both misp-stix and pymisp

Describe the solution you'd like

In order to address the naming conflicts, I propose updating the stix2 module to misp_lib_stix2. This adjustment has been formalized through a pull request, which can be reviewed at PR #3 within the misp-lib-stix2 repository. Once this modification is merged, I intend to submit a subsequent pull request for misp-stix, ensuring compatibility with the refined module name, misp_lib_stix2. This solution aims to harmonize the integration of both packages seamlessly. Your consideration of this proposed resolution is greatly appreciated.

Describe alternatives you've considered

No response

Additional context

Let me know if we can take any other way.

Code of Conduct

  • I agree to follow this project's Code of Conduct
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

No branches or pull requests

1 participant