network/framework: Removed (obsolete - use metasploit)

Upstream changed the name from framework to metasploit.

Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
This commit is contained in:
Robby Workman 2013-03-02 22:54:13 -06:00
parent 9ed971c0bf
commit 274c69f96c
8 changed files with 0 additions and 256 deletions

View file

@ -1,13 +0,0 @@
The Metasploit Framework is a development platform for creating security tools
and exploits. The framework is used by network security professionals to
perform penetration tests, system administrators to verify patch
installations, product vendors to perform regression testing, and security
researchers world-wide. The framework is written in the Ruby programming
language and includes components written in C and assembler.
This is just a repackaged version of the installer you get from the Metasploit
download page. This is an all-in-one installer with Metasploit own versions of
Ruby, Java and PostgreSQL.
Take a look at README.SLACKWARE for important build requirements and upgrading
suggestions.

View file

@ -1,45 +0,0 @@
You will need "postgres" user and group before running the installer, if you
haven't installed SlackBuilds PostgreSQL you should run these commands to be
compatible:
# groupadd -g 209 postgres
# useradd -u 209 -g 209 -d /var/lib/pgsql postgres
otherwise, you're already setup. Also, remember to add something like:
# Start Metasploit Framework PostgreSQL
if [ -x /etc/rc.d/rc.framework-postgres ]; then
/etc/rc.d/rc.framework-postgres start
fi
to /etc/rc.d/rc.local to start the shipped PostgreSQL daemon and something
like:
# Stop Metasploit Framework PostgreSQL
if [ -x /etc/rc.d/rc.framework-postgres ]; then
/etc/rc.d/rc.framework-postgres stop
fi
to /etc/rc.d/rc.local_shutdown to stop the service.
Default database server listening port is 7175, if you want to use another
port, just export the PG_PORT variable when running the SlackBuild, like this:
# PG_PORT="5454" ./framework.SalckBuild
An optional cron script to keep the framework up to date is distributed inside
the /usr/doc/framework-${VERSION} directory and it's called "msfupdate.sh",
there also is a logrotate config file called "msfupdate.logrotate" which can
be useful.
With older version of the framework, if you used the autoupdate script, future
package updates could break your current working copy, tainting the .svn
metadata. To avoid doing so, the tip was to run:
# removepkg framework
# rm -rf /opt/metasploit3
both as root, before proceeding with the package update.
Starting with Metasploit Framework 3.6.0, the installation directory changed
again, this time to /opt/framework-${VERSION}. Unless there will be any other
changes from upstream, this is a great solution as it will enable seamless
upgrades between svn and packaged versions, just remember to backup PostgreSQL
data stored inside "/opt/framework-${OLDER_VERSION}/postgresql/data/".

View file

@ -1,21 +0,0 @@
config() {
NEW="$1"
OLD="`dirname $NEW`/`basename $NEW .new`"
# If there's no config file by that name, mv it over:
if [ ! -r $OLD ]; then
mv $NEW $OLD
elif [ "`cat $OLD | md5sum`" = "`cat $NEW | md5sum`" ]; then # toss the redundant copy
rm $NEW
fi
# Otherwise, we leave the .new copy for the admin to consider...
}
# Keep same perms on rc.framework-postgres.new:
if [ -e etc/rc.d/rc.framework-postgres ]; then
cp -a etc/rc.d/rc.framework-postgres etc/rc.d/rc.framework-postgres.new.incoming
cat etc/rc.d/rc.framework-postgres.new > etc/rc.d/rc.framework-postgres.new.incoming
mv etc/rc.d/rc.framework-postgres.new.incoming etc/rc.d/rc.framework-postgres.new
fi
config etc/rc.d/rc.framework-postgres.new

View file

@ -1,136 +0,0 @@
#!/bin/sh
# Slackware build script for Metasploit Framework
# Copyright 2010-2011 Marco Bonetti <sid77@slackware.it>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
PRGNAM=framework
VERSION=${VERSION:-4.0.0}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
# Unless $ARCH is already set, use uname -m for all other archs:
*) ARCH=$( uname -m ) ;;
esac
fi
CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}
BASEINSTDIR="opt"
INSTDIR="$BASEINSTDIR/framework-${VERSION}"
# PostgreSQL user and group
PG_UID=${PG_UID:-209}
PG_GID=${PG_GID:-209}
# On which port is PostgreSQL listening to?
# Default is 7175, set PG_PORT to any other value if you want to customize it.
PG_PORT=${PG_PORT:-7175}
# Bail out if user or group isn't valid on your system
# For slackbuilds.org, assigned postgres uid/gid are 209/209
# See http://slackbuilds.org/uid_gid.txt
# Other popular choice is 26/26
if ! grep ^postgres: /etc/group 2>&1 > /dev/null; then
echo " You must have a postgres group to run this script."
echo " # groupadd -g $PG_GID postgres"
exit 1
elif ! grep ^postgres: /etc/passwd 2>&1 > /dev/null; then
echo " You must have a postgres user to run this script."
echo " # useradd -u $PG_UID -g $PG_GID -d /var/lib/pgsql postgres"
exit 1
fi
if [ "$ARCH" = "i486" ]; then
INSTALLERARCH=""
elif [ "$ARCH" = "i686" ]; then
INSTALLERARCH=""
elif [ "$ARCH" = "x86_64" ]; then
INSTALLERARCH="-x64"
fi
set -e
rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
# Install Metasploit Framework DIRECTLY under /opt/framework-${VRESION} (sorry!)
echo "Installing the Metasploit Framework..."
chown root:root $CWD/framework-$VERSION-linux$INSTALLERARCH-full.run
chmod 755 $CWD/framework-$VERSION-linux$INSTALLERARCH-full.run
$CWD/framework-$VERSION-linux$INSTALLERARCH-full.run \
--mode unattended \
--unattendedmodeui minimal \
--postgres_port $PG_PORT
# Stop Metasploit Framework PostgreSQL
echo "Stopping Metasploit Framework PostgreSQL..."
/etc/init.d/framework-postgres stop
# Move install dir
mkdir -p $PKG/$BASEINSTDIR
mv /$INSTDIR $PKG/$BASEINSTDIR/
# Fix init script and move it to the right directory
# This script is not handled by the uninstaller and the user should not call
# the uninstall script anyway, so no problem if we made it more Slackware-ish
echo "Fixing Metasploit Framework PostgreSQL init script..."
mkdir -p $PKG/etc/rc.d
mv /etc/init.d/framework-postgres $PKG/etc/rc.d/rc.framework-postgres.new
chown root:root $PKG/etc/rc.d/rc.framework-postgres.new
chmod 755 $PKG/etc/rc.d/rc.framework-postgres.new
# Install /usr/bin links
mkdir -p $PKG/usr/bin
echo "Installing links into /usr/bin..."
( cd $PKG/usr/bin
for file in $(ls ../../$INSTDIR/app/msf*); do
ln -sf $file $(basename $file)
done
# also links armitage
ln -sf ../../$INSTDIR/app/armitage armitage
)
# Every useful doc is included inside the framework folder, just copy over the
# README which contains the important copyright disclaimer and the cron script
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a $PKG/$INSTDIR/msf3/README $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/msfupdate.sh > $PKG/usr/doc/$PRGNAM-$VERSION/msfupdate.sh
cat $CWD/msfupdate.logrotate > $PKG/usr/doc/$PRGNAM-$VERSION/msfupdate.logrotate
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
cat $CWD/README.SLACKWARE > $PKG/usr/doc/$PRGNAM-$VERSION/README.SLACKWARE
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/doinst.sh > $PKG/install/doinst.sh
# Do NOT chown -R root:root or it will bork the shipped PostgreSQL
# installation: the bitrock installer should have taken care of permissions
cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}

View file

@ -1,10 +0,0 @@
PRGNAM="framework"
VERSION="4.0.0"
HOMEPAGE="http://www.metasploit.com/"
DOWNLOAD="http://downloads.metasploit.com/data/releases/archive/framework-4.0.0-linux-full.run"
MD5SUM="198a40fd0210985b7dd068858fed0ca6"
DOWNLOAD_x86_64="http://downloads.metasploit.com/data/releases/archive/framework-4.0.0-linux-x64-full.run"
MD5SUM_x86_64="60a027a115d50206a01d8dc513ee5049"
REQUIRES=""
MAINTAINER="Marco Bonetti"
EMAIL="sid77@slackware.it"

View file

@ -1,10 +0,0 @@
/var/log/msfupdate.log {
daily
rotate 5
compress
delaycompress
missingok
notifempty
create 0644 root root
}

View file

@ -1,2 +0,0 @@
#!/bin/sh
/usr/bin/msfupdate >> /var/log/msfupdate.log 2>&1

View file

@ -1,19 +0,0 @@
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description. Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in. You must
# make exactly 11 lines for the formatting to be correct. It's also
# customary to leave one space after the ':'.
|-----handy-ruler------------------------------------------------------|
framework: The Metasploit Framework (http://www.metasploit/)
framework:
framework: The Metasploit Framework is a development platform for creating
framework: security tools and exploits. The framework is used by network
framework: security professionals to perform penetration tests, system
framework: administrators to verify patch installations, product vendors to
framework: perform regression testing, and security researchers world-wide.
framework: The framework is written in the Ruby programming language and
framework: includes components written in C and assembler.
framework:
framework: