-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
Installation #228
Comments
I tried this on differnt machines |
It looks like the install helper scripts tries to get apt info on metasploit but apt returns:
This is on ubuntu 20.04 (the package does not exits) |
Hi @keesj-exset As far as I know the metasploit package is only available on Kali. I recommend to use the docker container with "sudo ./installer.sh -d". This installs only the cve-search and docker environment on your host. If you really prefer using the dev mode (usually there is no reason doing this) you could bypass the errors with disabling strict mode in the installer. But I'm not sure if you are going to get a working installation at the end. |
Hi, I indeed came to this conclusion. The install script depends on kalilinux. I created a vagrantfile (to generate a virtual machine with emba installed). I did not test much yet but the installation works. I did try a few other approaches documented in the install but quite frankly is was all a bit confusing (if you do not start with a kalilinux base). Perhaps .. somebody want to have a look at the vagrant based setup (this would also allow to "throw" away the virtual machine after use." |
Cool! I will include a note with a link to your repo in the wiki |
Now I included a link to EMBAbox in our wiki: https://github.com/e-m-b-a/emba/wiki/Installation#random-installation-topics Thanks for your great addition to EMBA. Will close this for now |
Describe the bug
I am getting an error during the installation near metasploit-framework
To Reproduce
set -e
git clone https://github.com/e-m-b-a/emba.git
cd emba
sudo ./installer.sh -F
Log;
"xit" command not found -> exit perhaps?
The text was updated successfully, but these errors were encountered: