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

Metapackage proposal: neo4j-community.vm #975

Closed
Menn1s opened this issue Apr 3, 2024 · 5 comments
Closed

Metapackage proposal: neo4j-community.vm #975

Menn1s opened this issue Apr 3, 2024 · 5 comments
Assignees
Labels
🌀 COMMANDO-VM A package or future to be used by COMMANDO VM 🆕 package New package request/idea/PR

Comments

@Menn1s
Copy link
Contributor

Menn1s commented Apr 3, 2024

Package Name

neo4j-community

Tool Name

neo4j

Package type

METAPACKAGE

Tool's version number

3.5.1.2024.04.03

Category

Utilities

Tool's authors

neo4j

Tool's description

A major graph database that is used as the DBMS backend for BloodHound.

Dependency

neo4j-community

Shim path

%PROGRAMDATA%\chocolatey\bin\neo4j.exe

Why is this tool a good addition?

This tool is needed for the use of BloodHound, commonly used for Active Directory analysis.

@Menn1s Menn1s added the 🆕 package New package request/idea/PR label Apr 3, 2024
@Menn1s Menn1s self-assigned this Apr 3, 2024
@Menn1s Menn1s added send PR Triggers a workflow that send a PR for the package issue 🌀 COMMANDO-VM A package or future to be used by COMMANDO VM labels Apr 3, 2024
@github-actions github-actions bot removed the send PR Triggers a workflow that send a PR for the package issue label Apr 3, 2024
@Menn1s
Copy link
Contributor Author

Menn1s commented Apr 3, 2024

@Ana06, turns out we don't need this package because of changes to bloodhound and neo4j, but do you know why this might be failing? https://github.com/mandiant/VM-Packages/actions/runs/8545039645/job/23412442246

Looked at very similar metapackage addition and couldn't spot the difference. This is what I was comparing to : https://github.com/mandiant/VM-Packages/actions/runs/7749888145/job/21135228735

@emtuls
Copy link
Member

emtuls commented Apr 5, 2024

Hi @Menn1s.

I took a look and it doesn't explicitly say it in that log view and the error is a bit misleading, but it looks to be an issue with the version number which is what the log is also showing.

image

You put the version number as 3.5.1.2024.04.03, which doesn't conform to the Versioning standard in the wiki noted here: https://github.com/mandiant/VM-Packages/wiki/Package-Structure#version

It should be 3.5.1.20240403. 🙂

Also, if the package is not needed, feel free to close the issue when you are sure that everything is good to go!

@Ana06
Copy link
Member

Ana06 commented Apr 9, 2024

As @emtuls said, it is because the invalid version format (you can only use 4th segments, see documentation in the wiki). If you edit the first comment of this issue to correct the version and add the label again, it should work. 😉

@Ana06
Copy link
Member

Ana06 commented Apr 9, 2024

@Menn1s

turns out we don't need this package because of changes to bloodhound and neo4j

should we then close this issue? 😃

@Menn1s
Copy link
Contributor Author

Menn1s commented Apr 9, 2024

Issue is good to close, thanks Ana!

@Menn1s Menn1s closed this as completed Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌀 COMMANDO-VM A package or future to be used by COMMANDO VM 🆕 package New package request/idea/PR
Projects
None yet
Development

No branches or pull requests

3 participants