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

medusa, metasploit not found but come preinstalled in kali #7

Open
007scorpio opened this issue Nov 22, 2016 · 10 comments
Open

medusa, metasploit not found but come preinstalled in kali #7

007scorpio opened this issue Nov 22, 2016 · 10 comments
Assignees

Comments

@007scorpio
Copy link

007scorpio commented Nov 22, 2016

It working now but can't find medusa and metasploit, opens-nasl
installation path...

@JonnyHightower
Copy link
Owner

The installer sometimes says it can't find medusa even if it can. I'll remove that particular check.
Metasploit integration won't work again until I patch it to use msfconsole instead of msfcli, which has been withdrawn by Rapid7.
Openvas-nasl - that's strange.
You can tell neet the location of openvas-nasl (and medusa if it's not already known) by doing this as root:
echo openvas-nasl=/path/to/openvas-nasl >> /opt/neet/etc/locations
You can do the same for medusa if it's not list in that file. I'll look into this issue.

@jcmoreno
Copy link

I'm facing the same issue.

On my Kali I have msfcli on /usr/share/framework2 folder, so I could point it there, but what variable do I use?

I don't see one for MSF on the locations file.

Now I do have OpenVAS but I can't seem to find openvas-nasl

@JonnyHightower
Copy link
Owner

The format of the locations file is:
executable=/path/to/executable
"Executable" can be any executable on your system; those not used by neet will be ignored.
You could add msfcli=/usr/share/framework2/msfcli but that's an ancient version of the Metasploit Framework, and the exploits in Neet (largely in /opt/neet/etc/vce.conf) were written for MSF3 and MSF4, before Rapid7 removed msfcli. I doubt very much that adding the above line would make anything better. I will be porting the exploitation commands to use the latest Metasploit Framework in the next few weeks so the msfcli issue shouldn't be around for long.
As it couldn't find openvas-nasl at install, the installer should have built it for your system and put it at /opt/neet/pkg/bin/openvas-nasl. I'll look into this on my Kali build, but am running out of time this week so might not get a chance to fix it before next Monday/Tuesday. I will keep looking at it though. Cheers!

@jcmoreno
Copy link

jcmoreno commented Nov 23, 2016

Sounds good. I'll stay tuned. I'm glad that I saw g0tmi1k's post recommending this tool. It's very interesting.

The openvas-nasl wasn't built on mine. I'll just watch the repo.

Thanks!

@JonnyHightower
Copy link
Owner

OK - it mostly works on Kali now. Openvas-nasl still doesn't build. I'll look at that next week. As I said, I still haven't fixed the Metasploit integration, but that will come over the next couple of weeks. I suggest you do a full re-install so the installer gets run from the beginning, rather than just doing a neet-update.
To be honest, it's been a bit of a surprise to me that people have found Neet. I just put it here so work colleagues could download it a few years ago :) I didn't see g0tmi1k's post - just found it. Thanks for letting me know!

@jcmoreno
Copy link

Sounds good. I'll do that.

It's good stuff!

In the meantime, do you recommend another linux distribution that may be fully supported like Ubuntu?

@007scorpio
Copy link
Author

Installed nice on Parrot OS but run with errors...

@JonnyHightower
Copy link
Owner

Well, Neet started out in its current form on Ubuntu 12.04. In terms of distro support, the main issue is just that package names differ between distros, and not everything Neet uses is available in all package repo's. Some stuff that isn't available in all repo's gets built by Neet at install time, but even that can fail if a dependency source package is missing. As far as I know, the Ubuntu 14.04 and 16.04 package lists are accurate, so it should install OK on those. I've never bothered using the non-LTS releases. I moved from Ubuntu to Mint a year or so back, so haven't actually tried Neet at all on 16.04 (though I've checked a sample of the package names online and they seem to be in Neet's list for 16.04). It worked great on 14.04 though. In general, I support what I'm using, which at the moment is Mint, but am happy to help with other Debian-based distros as the package management is pretty simple and reliable. Neet's biggest issue is the dependency on multiple tools that get deprecated and changed from one year to the next. As you may have realised, this is the first real development time I've put into it in the last couple of years, so it's taking a while to get it working seamlessly with newer library and tool versions etc. etc.
Incidentally, openvas-nasl now builds on Kali, and gets installed in /opt/neet/pkg/bin/openvas-nasl.

@jcmoreno
Copy link

That's great. Thx for puting thia effort. I know that it might have been meant for a smaller audience initially.

I'll deploy it on Ubunt 14 and 16 to compare, and give Mint a whirl.

@ghiocel30
Copy link

Grande lavoro!!!

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

4 participants