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

2.38.1 Install Fails on Kali #533

Closed
Pavornoc opened this Issue Aug 11, 2017 · 8 comments

Comments

Projects
None yet
6 participants
@Pavornoc

Pavornoc commented Aug 11, 2017

Trying to perform a new install of the .deb package on Kali Linux. I receive an error saying mysql-server is not installed. MySQL is installed by default on Kali, and I've checked to make sure the service is running as well (tried it both running and not).

Here is the error message I get from dpkg:

sudo dpkg -i seccubus_2.38.1-0_amd64.deb 
Selecting previously unselected package seccubus.
(Reading database ... 379197 files and directories currently installed.)
Preparing to unpack seccubus_2.38.1-0_amd64.deb ...
Unpacking seccubus (2.38.1-0) ...
dpkg: dependency problems prevent configuration of seccubus:
 seccubus depends on mysql-server; however:
  Package mysql-server is not installed.

dpkg: error processing package seccubus (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 seccubus

Is there a way I can either reconfigure seccubus to try using a different DB, like PostgreSQL for example, or something I can provide to help you troubleshoot this?

Thanks for your time and all your effort on the project!

@jfbethlehem

This comment has been minimized.

jfbethlehem commented Aug 24, 2017

You need to install all dependancies.

Type: sudo apt-get install -f

@Pavornoc

This comment has been minimized.

Pavornoc commented Aug 24, 2017

That has already been done. All the dependencies ARE installed, which I mentioned in the original post. Seccubus is not recognizing that MySQL Server is already installed.

@seccubus

This comment has been minimized.

Member

seccubus commented Aug 31, 2017

Ubuntu and debian have configured MariaDB-server as an alias for mysql-server Kali doesn;t have this for some reason.

Don;t know how to fix that, yet.

@alirezakv

This comment has been minimized.

alirezakv commented Aug 31, 2017

apt install perl MariaDB-server libalgorithm-diff-perl libdbi-perl libdbd-mysql-perl libjson-perl libxml-simple-perl libwww-perl liblwp-protocol-https-perl libnet-ip-perl libtimedate-perl libhtml-parser-perl libcrypt-pbkdf2-perl libterm-readkey-perl libmojolicious-perl;
then install from source:
git clone ...
cd seccubus
./build_all
cd build
./install.pl --basedir /opt/seccubus
This is how i'm doing it on kali!

@gavinmporter

This comment has been minimized.

gavinmporter commented Oct 1, 2017

Confirmed still an issue with Seccubus version 2.40.0

Added bug on the Kali bug tracker: https://bugs.kali.org/view.php?id=4281

@gavinmporter

This comment has been minimized.

gavinmporter commented Oct 2, 2017

The problem in Kali is inherited from Debian. Debian Testing only provides 'default-mysql-server' and not 'mysql-server'.

Suggestion from Kali bug tracker, is to change the debian.control file of the package to include both options:
"mysql-server | default-mysql-server,"

@rhertzog

This comment has been minimized.

rhertzog commented Oct 2, 2017

The correct dependency to use is "default-mysql-server | virtual-mysql-server". If you want to keep compatibility for version older than stretch you might want to add a third alternative "default-mysql-server | virtual-mysql-server | mysql-server".

Thank you. (FTR I'm a Debian developer and a Kali developer)

@seccubus

This comment has been minimized.

Member

seccubus commented Oct 2, 2017

Thanks. I will make sure to adopt this.
I hope to be included in Kali one day.

@seccubus seccubus closed this in e80d68c Oct 2, 2017

seccubus added a commit that referenced this issue Oct 2, 2017

Merge pull request #579 from schubergphilis/533-kali-install-issues
This fixes #533 and adds .deb building to CircleCI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment