Package Details: metasploit 4.12.22-1

Git Clone URL: (read-only)
Package Base: metasploit
Description: Advanced open-source platform for developing, testing, and using exploit code
Upstream URL:
Licenses: BSD
Submitter: None
Maintainer: anthraxx
Last Packager: anthraxx
Votes: 322
Popularity: 3.716133
First Submitted: 2005-12-07 00:45
Last Updated: 2016-08-30 23:23

Latest Comments

nsantiago2719 commented on 2016-08-30 15:39

@antrhaxx thank you I solved it. It is because I have a conflict repo in pacman.conf file. It seems that pacman detects a metasploit package from another repo and it tries to update it.

anthraxx commented on 2016-08-30 15:28

thats not my package, look at the version identifier. you are pulling from some other custom repository.

PS: You should keep an eye on this as metasploit will soon move to the community repo and the other repo overwrites that by its epoch=4

nsantiago2719 commented on 2016-08-30 15:27

@antraxx I run the sudo pacman -Syu to check any updates and install. In the update I this following packages:
fltk-1.3.3-6 java-environment-common-2-2
java-runtime-common-2-2 jdk8-openjdk-8.u102-1
jre8-openjdk-8.u102-1 jre8-openjdk-headless-8.u102-1
ruby-bundler-1.12.5-1 tigervnc-1.6.0-1 xorg-xauth-1.0.9-1

anthraxx commented on 2016-08-30 15:08

What update command, the msfupdate executable is removed on purpose. If you use the package, there is no supported auto-update mechanics other then waiting for a new package update.

nsantiago2719 commented on 2016-08-30 15:05

I successfuly installed the package but when I run the update command there is an update for metasploit. I agreed to install the update but when it comes to metasploit it has a bundler error.

evilgnome commented on 2016-05-11 16:44

Just in case someone else finds this useful:

sed -i 's;bundle install;PATH=/usr/bin:$(/usr/bin/ruby -rubygems -e "puts Gem.user_dir")/bin:$PATH bundle install;' PKGBUILD

will allow folks using rbenv to install this properly without a chroot or build user

anthraxx commented on 2016-04-14 13:17

sorry but I won't include workarounds/hacks for custom environments as such as that would mean to try to support any possible weird custom environments. I also had a guy once who insisted that i should replace all 'python' shebangs with 'python3' just because he replaced his 'python' symlink with 'python2'.

Custom environments are: custom. If you don't like to build in a clean chroot, you can simply create a new user called 'build' that does not expose rbenv environment variables.

evilgnome commented on 2016-04-14 00:13

FWIW: The pkgbuild will work for folks who use rbenv if you add this line to the beginning of build():

export PATH=/usr/bin:$(/usr/bin/ruby -rubygems -e "puts Gem.user_dir")/bin:$PATH

anthraxx commented on 2016-04-13 23:36

@evilgnome: sure but if you alter your environment than thats your environment that needs to be made compatible, not the build script. Feel free to build this package in a clean chroot using the devtools package.

evilgnome commented on 2016-04-13 23:27

@anthraxx: if someone has rbenv installed, and loaded with their shell profile, it will pick up on the file ".ruby-version" in the fetched source, and try to change the present shell environment to use the version of ruby specified in the file.

You should be able to reproduce the problem by installing rbenv and putting this in your shell profile:

eval "$(rbenv init -)"


All comments