I was toying with something like this a while ago, I was playing with the idea of being able to do this from a *nix box for VA purposes (With out the gui part, I just wanted a yes or no back).
It’s current state should not get many hosts, the list of passwords is limited.
Here is a list of hosts it will attempt to contact for updates.
220.127.116.11 jifr.info jifr.co.cc jifr.co.be qfsl.net qfsl.co.cc qfsl.co.be
Always check your firewall logs just to be safe.
Wikipedia as a good section on the current suspected members of LulzSec that have been picked up.
There is a few in there that I have not posted about, it’s worth catching up on.
For as little as 1,600 USD you too can do this.
Heck while you are at it order one for the car, cottage and RV!
I can think of a few ways for this to get someone in to trouble, I am suprised that no one else had thought of using it on an ATM pin pad.
Using the camera you can infer in what order the digits are also supposed to go in, based on the strength of the signal.
The latest version of the EXT file system is 4. The other previous version are 2 and 3, some of the improvements of 3 are improved indexing for larger directories and journaling.
EXT4 add more features;
- Volumes up to 1 exbibyte (EiB).
- Files up to 16 tebibytes (TiB).
- Extents, improvement of large file performance and reduction of fragmentation.
- Journal checksumming.
This is exciting, I will be leading a SANS mentor session in Winnipeg.
The sessions will run from January 26th, 2012 until March 29th, 2012.
This is Security 504, Hacker Techniques and Incident Handling. This material is excellent and is something even non-security people should take. It knowledge is valuable to anyone who needs to defend a network.
Lulzsec Exposed is still on the hunt for Sabu.
We now have to competing ideas on who he is.
One is a guy from New York, the other is from Portugal. Not that I am downing any of the theories but I am still on the fence on who is right if any of them.
I really don’t trust any of the evidence presented, but I also to agree with the conclusions they have made with the rebuttals. I wish they would tests them.
When I talk of evidence I mean any of it from anyone.
We also have to deal with the block pointers in the inodes. Each inode can store the address of 12 blocks to store the data. So what happens when you need more then 12 blocks to store the data?
You use indirect block pointers, instead of pointing at blocks of data. You point at blocks that point to the blocks. Basically lists of lists.
The first layer of this is called single indirect block pointers, the lists of lists. Then we go to double indirect block pointers. Lists of lists of lists. Then down to triple indirect block pointers, lists of lists of lists of lists.
The still short version of what happens when you need locate a file on the system is the following;
- The SuperBlock is read, to collect information about the file system.
- Next to the Group Descriptor Table (After the SuperBlock on the disk), collection of information about the block groups.
- Once the block group that the file resides in is determined, the group descriptor table is used to locate where the Inode Table is.
- The Inode Table will point us to the block root directory entries.
- That is opened to locate the folder that contains the file we are looking for.
- Now we have the inode of the folder, we then determine the block group it belongs to (we use information from the SuperBlock for that).
- Then we go to that block group and get the location of the folder.
- Now we can open the block the contains the folder.
Partitions are just fine, but how does the system get to a file on the disk?
On a EXT based system, the short answer is the information is stored in the Inode Table.
That really does not mean much if you don’t have understanding of what the filesystem looks like.
A little explanation is needed.
The first section of the filesystem is going to contain the Super Block (block 1), there could be boot code in front of that (Unused). The Super block contains information about the file system, such as block sizes, total number of inodes and the volume name to list a few.
Following the Super Block is the Group Descriptor Tables, this is what we need. This will have a backup of the Super Block, and contains the Block Bitmap, Inode Bitmap and group descriptor data structure for every block in group in the filesystem. These are the basic structures we need to locate information on the disk.