…..pixie dust pixie dust every where you look
…..pixie dust pixie dust every where you look
Openx has been a pain in my ass for some time now (5 years). Even if you have the latest most up to date software release, you will still get append and prepend infections. I’m not sure if it comes from client browsers when they log in or some other reason. What I can assure you is that the file system in which openx resides is as secure as it can be while leaving openx functional (all files are owned by a different user than the web server process and are only readable by the web server. All directories, except two, are also owned by a different process than the web server and are read only….while two have to be writable by the web server process. The lamp stack is also up to date.). Anyways, even with these restrictions, clean code, clean db, limited plugins, and even checked the meta data of all image files for backdoors (I first learned about this technique in approx 2010 but here is an article from 2011 detailing this – PHP Code into JPEG Metadata: From hide to unhide ) we still get an occasional append/prepend infection.
How to stop it? This is pretty easy, I simply wrote a script that checks for append/prepend problems, logs if clean, logs and alerts if infected, and also disinfects. This only works, if the append and prepend is NOT being used in your ads.
I just bought this card to replace an older radeon 4500 series gpu. Here are the benchmarks (this is a quad-core amd with 16GB memory, sata drives):
$ sudo pyrit benchmark
Pyrit 0.4.1-dev (svn r308) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+
Running benchmark (59139.3 PMKs/s)... -
Computed 59139.26 PMKs/s total.
#1: 'CAL++ Device #1 'AMD GPU DEVICE'': 59710.6 PMKs/s (RTT 1.1)
#2: 'CPU-Core (SSE2)': 568.9 PMKs/s (RTT 3.0)
#3: 'CPU-Core (SSE2)': 572.3 PMKs/s (RTT 2.9)
#4: 'CPU-Core (SSE2)': 548.1 PMKs/s (RTT 3.0)
A long time ago, I created a database to hold passwords and their respective hashes for some 16 various hash types. It has approximately 310,261,848 passwords for each type and is growing nearly every day as more password lists become available. I found a pretty quick way to generate the hashes for these wordlists and wanted to share how it is done. These hashes only work with unsalted/unpeppered passwords.
First, lets look at my table schema, which is very simple and very effective. It uses an index on the hash + password column so there can not be any two hashes+passwords that are the same. The types table is a simple lookup table that references data.type 1 to a name like DES. The primary key is on the name column. I don’t claim to be a db administrator so if you spot any errors, let me know.
Some of the posts I am seeing on the internet regarding the wordpress password crack via botnet is pretty funny as various people offer suggestions to fix the problem. The quickest fix is simple and although it protects the wp-admin page, it wont protect you from the inbound traffic or sql injection.
My desktop computer is a couple of years old. It serves me well for what I do. I just got a new laptop. In terms of hardware, the laptop is much different. The desktop is a quad-core AMD 900 series with an ATI 4500 series gpu running backtrack 5r3. It has 8GB of memory and standard SATA drives. The laptop is an Intel i7 cpu, with SSD drive, NVIDIA 660M gpu, and 8GB memory running backbox 3. The internal SATA drive is slow as fuck (just putting that out there). I have the OS on the SSD drive and my home folder on the SATA drive.
Here are the specs as seen by pyrit list_cores from each along with the benchmark tests:
Backtrack has dbpwaudit in /pentest/database/dbpwaudit, however, it does not come with the java jar files required. So, first you have to go download them. The easiest way I found out to do that is by simply searching for the aliases and then googling them. You can get the aliases with the -L option:
user@HOST:/pentest/database/dbpwaudit$ ./dbpwaudit.sh -L
DBPwAudit v0.8 by Patrik Karlsson <firstname.lastname@example.org>
Oracle - oracle.jdbc.driver.OracleDriver
MySQL - com.mysql.jdbc.Driver
MSSql - com.microsoft.sqlserver.jdbc.SQLServerDriver
DB2 - com.ibm.db2.jcc.DB2Driver
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
./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….