Yippie yi yay

vzpkg install <CTID> -p yum

Unique IP’s and amount of entries in access_log:
======================================
cat <path to log file> | awk ‘{print $1}’ | sort -n | uniq -c

Amount of unique IP’s:
===================
cat <path to log file> | awk ‘{print $1}’ | sort -n | uniq -c | wc -l

Amount of Bytes of data from files logged.
=================================
cat <path to log file> | awk ‘{sum+=$10}END{print sum}’

Unique files and the amount of times accessed
====================================
cat <path to log file> | awk ‘{print $7}’ | sort | uniq -c | sort -n -r

Unique files and there size in bytes
============================
cat <path to log file> | awk ‘{print $10, $7}’ | sort -n -r

Johnny Long’s talk at DefCon 17 from Dash Riprock on Vimeo.

I have been using feedparser module which is very simple to get Fedora users are able to simply install this via yum the package is

python-feedparser

.

If you are not on fedora check you package manager or down load the module from http://www.feedparser.org

Using feedparser is a simple task. First import the module and load your feed into your script like so:

#! /bin/env python
import feedparser 

# Lets import the feed of computer related posts from puredistortion.com.
feed = feedparser.parse('http://puredistortion.com/category/compstuff/feed/')

From here you are able to pull any data that you need from the feed. Feedparser formats the RSS feed into lists ad dictionaries to make working your way through the information a simple task.

For more information on how to extract the data from the feed once you have imported your RSS feed into your script have a look at http://www.feedparser.org/docs.

Or download a script that was the basis for what I am using to download podcasts to my home server here : get_rss.py (35)

dmidecode | grep "Serial Number"

Dmidecode shows heaps of information that I have yet to have a closer look at. The command is located in /usr/sbin

I have found the sealert GUI tool to be a great help when setting up and troubleshooting issues on a system, but have always struggled at the command line. Until I found a solution.

 sealert -a /var/log/audit/audit.log

This outputs the text of the sealert GUI to stdout and assists you in troubleshooting where SELinux is interfering with the system.

This is also handy as you can point any file that has audit log entries in it and it will assess this so if you are emailed the log entries. Dump them in a file and point sealert at it.

Also Checkout the SELinux HowTo on the Centos Wiki for heaps of other tips and tricks on troubleshooting SELinux.

That was until I saw a MyKi unit on a tram in he city. Could this bee that there will be an option for an RFID ticket for Metro train, tram and bus services? Don’t know (if you know more info on this leave a comment) but now it has me concerned about if they will be getting rid of the mag swipe paper tickets that exist now.

When these are released I will be getting a MyKi just to see what information is being stored on these tickets and what the affects of cloning one would be as just because RFID tags are in your wallet or bag does not mean that your ticket can not be stolen now. Especially with the automatic top up of you credit from a debit or credit card. I can see fraud being an issue.

Also he privacy will be interesting with how much of your travel data and history this system will need to give you the best ticket. What will be the availability of this information for law enforcement and the general public? I certainly don’t want travel habits stored on a server I don’t have control of.

If any one has a looked into these MyKi card and the info on them let me know and I will discuss with you on how to get your stuff up on here so that people can make an informed decision about whether the MyKi ticketing solution is a solution that is safe enough for them.

Though if we are not given a choice you can always get a RFID blockind wallet from ThinkGeek check it out.

Picks of the Pay station:

Pics of the Scanner on the tram:

I have setup this Wordpress blog so I have no excuse but to post a bit more often.

I have added some of the technical articles that I have on the old site here so they are easy for me to find.

Also all of the old posts you will be able to find at http://puredistortion.blogspot.com or http://blog.puredistortion.com.