If you run fix-splash on a backtrack installation and get:
$ sudo fix-splash
[*] Fixing Initrd
[*] Extracting Initrd
181100 blocks
cpio: File ./initrd grew, 46361600 new bytes not copied
181100 blocks
[*] Reboot and bask in the joys of BootSplashThe fix is really simple…..
You might also want to see my article Installing JTR On Backtrack for Multiprocessor Cores
I am too lazy to restore the old version of this file from my old website (it was hosted for years on mambo and I am just too lazy to do the db conversion). Anyways, this website serves a couple of purposes, first is to keep some of my own notes handy and second to help others. With that in mind, here is a collection of tips on using john the ripper:
Prepare Linux Shadow Passwords
umask 077
./unshadow /etc/passwd /etc/shadow > mypasswds
Lets face it, John the Ripper has been around a long time and the reason its been around a long time is because its damn good at cracking passwords. Yea, hashcat and oclhashcat are great for gpu cracking, but it doesn’t support as many algorithms as JTR. So, imagine my surprise when I fire up John The Ripper on backtrack 5 64 bit and find out it is using a single CPU. That is letting a potential 75% of my system sit there wanting to do something. Luckily the fix is easier than fixing a sandwich.
If you already have jtr installed, you may want to see my john tips article.
First, lets grab the jumbo sourcecode….
When you upgrade pacman, you will get a message that says “run pacman –init” and when you do from a console (like on a remote server), you will then be presented with the following message:
# pacman-key --init
gpg: Generating pacman keychain master key...
Not enough random bytes available. Please do some other work to give
the OS a chance to collect more entropy! (Need 282 more bytes)
I created this because I always forget the command to enumerate snmp and I am often too lazy to read man pages 
#!/bin/bash
# By Ed Wiget
# This script takes an input ip or domain and performs a snmpwalk using common community strings
# 20120204 - initial script
function proghelp (){
echo ""
echo ""
echo "Help:"
echo "./eds-smtpwalk.sh ip_address"
echo ""
echo "Example:"
echo "./eds-smtpwalk.sh 127.0.0.1"
echo ""
echo ""
}
if [ $# -ne 1 ]
then
clear
proghelp
exit
fi
# set up the first input value
if [ "$1" == "" ]; then
echo "What is the ip address to query?"
read SVRIP
else
SVRIP=$1
fi
if [ -f wordlist-common-snmp-community-strings.txt ]; then
for COMSTG in `cat wordlist-common-snmp-community-strings.txt`
do
# removed below in favor of auto list
# set up the second input value
#if [ "$2" == "" ]; then
# echo "What is the community string?"
# read COMSTG
#else
# COMSTG=$2
#fi
snmpwalk -v2c -c ${COMSTG} $1 system
done
else
echo "wordlist-common-snmp-community-strings.txt does not exist.......fetching now......please wait"
echo ""
wget http://fuzzdb.googlecode.com/svn/trunk/wordlists-misc/wordlist-common-snmp-community-strings.txt
echo ""
echo "please run again....."
fi
#!/bin/bash
# By Ed Wiget
# This fixes dropbox sync issues on linux
# get a list of files executable now
find ~/Dropbox -type f -perm -u+x > /tmp/dropbox_files-`date +%Y%m%d`
# fix the permissions
sudo chown -R $USER ~/Dropbox
sudo chmod -R u+rw ~/Dropbox
sudo chown -R $USER ~/.dropbox
sudo chmod -R u+rw ~/.dropbox
# remove any conflicting files from the file list above step 1
grep -v -e "conflicted copy" -e "Case Conflict" /tmp/dropbox_files-`date +%Y%m%d` > /tmp/dropbox_files-`date +%Y%m%d`.txt
# set the executable permissions back
for files in `echo /tmp/dropbox_files-\`date +%Y%m%d\`.txt` ; do chmod u+x "${files}" ; done
# remove any files that are in conflict
find ~/Dropbox -type f -name \*"conflicted copy"\* -exec rm -f "{}" \;
find ~/Dropbox -type f -name \*"Case Conflict"\* -exec rm -f "{}" \;
# remove temp files
rm -f /tmp/dropbox_files-`date +%Y%m%d`
rm -f /tmp/dropbox_files-`date +%Y%m%d`.txtAnyways, this script will fix the problems. Make sure you adjust the path if your linux install does not have dropbox at ~/Dropbox.
Everybody knows I have been an avid daily linux user since…..1995 or so, and I switched to linux as my primary desktop around 1997. The ONE struggle I have had since day 1 is that I do photography as a hobby and since I started using photoshop (I think around version 3), I have never been able to find a permanent solution for linux. I have used gimp, I even used gimp in the photography classes I taught but it is lacking in several areas…..one being 16+ bit support, the second being layered tiffs, and the third being its just not photoshop. Then, along came lightroom while I was actually beginning to use gimp with digikam more….and that pretty much moved me back to photoshop again.
So, I have been fighting with trying to keep photoshop and lightroom working on wine and really just wishing adobe would come out with a photoshop and lightroom version for linux (I think they would make a freaking killing), trying Bibble again and trying to decide if I wanted to pay the price (I actually went to purchase it and for the life of me couldn’t figure out how….so you guys lost a sale just because there was no way to make a purchase from my signed in account with my expired trial license)…..when I came across Darktable. Darktable aims to be a replacement for Lightroom. Its really easy to install too.
Installation
One of the easiest ways to set up a subversion server that is lightweight is to use an existing linux server with sufficient free space available to hold your repositories. This is much more lightweight because it really doesn’t require any additional software or services, outside of subversion which is likely already installed if you use the svn client; and ssh which is probably already installed and running.
I will give the steps I used for centos, but it will work with other linux distributions if you apply the correct package management steps (pacman, apt-get, yum, emerge, etc):
First, make sure we have subversion and openssh installed:
yum install subversion openssh-server
So, I use linux exclusively….for everything except my photography post-processing. I don’t care about the rants and raves people give me about gimp, my workflow has included photoshop since Photoshop v3.0 (like mid-1990′s), and its just too hard to switch…..so I keep one windows machine around just to do photoshop tasks.
Now that I have my fluxbox bliss on my 16GB Quad-core machine dual booting with the factory Windows 7….I thought it would be nice to be able to run windows 7 inside of Linux. In the past, I always did the “virtualbox from new installation”. Its kind of a pain in the ass and a huge waste of disk space.
Doing some quick research, I found several articles on booting the physically installed windows in virtualbox and after many trials and errors, I found a simple solution that works.
Here is how I set it up…..
£ðllðw mê