SOLDIERX.COM Nobody Can Stop Information Insemination

-----------------

For most of you out there, money is hard to come by. Until now:

With the recent advent of plastic money (credit cards), it is
easy to use someone else's credit card to order the items you have
always desired in life. The stakes are high, but the payoff is
worth it.

Step One: Getting the credit card information

First off, you must obtain the crucial item: someone's credit
card number. The best way to get credit card numbers is to take
the blue carbons used in a credit card transaction at your local
department store. These can usually be found in the garbage can
next to the register, or for the more daring, in the garbage
dumpster behind the store. But, due to the large amount of credit
card fraud, many stores have opted to use a carbonless transaction
sheet, making things much more difficult. This is where your
phone comes in handy.

First, look up someone in the phone book, and obtain as much

Before reading this article, it would be a very good idea to get a
book on photo offset printing, for this is the method used in
counterfeiting US currency. If you are familiar with this method
of printing, counterfeiting should be a simple task for you.

Genuine currency is made by a process called "gravure", which
involves etching a metal block. Since etching a metal block is
impossible to do by hand, photo offset printing comes into the
process.

Photo offset printing starts by making negatives of the currency
with a camera, and putting the negatives on a piece of masking
material (usually orange in color). The stripped negatives,
commonly called "flats", are then exposed to a lithographic plate
with an arc light plate maker. The burned plates are then
developed with the proper developing chemical. One at a time,
these plates are wrapped around the plate cylinder of the press.

by JRoger

I figure I would drop a line since I encountered this issue on a laptop that belonged to somebody in my major. Apparently, Comcast has released their own security suite in an attempt to make things more secure. Unfortunately, their software is extremely buggy and the uninstall leaves ComcastAntiSpy.exe on the computer and a registry entry exists for it. As a result, this file will max out one of the cores of a processor when it actually isn't doing anything. With that in mind, I suggest that those with this issue do the following.

1. Look in Add/Remove Programs and remove the program called "CA Realtime Protection." (This name is extremely shady to say the least since this is supposed to be a Comcast program.)
2. If it is still there, go to C:\Program Files\comcasttb\ (or whatever drive letter is acting as the root directory) and remove everything inside of it, then make sure that the startup for this program is fully removed manually.

The following is Amp's Opinion only. By reading this, you agree that he cannot be held liable for it.

It's no secret that I play videogames on a regular basis. However, in recent years the whole Motion Control fad in gaming has gotten out of control. This all started with Wii's battery chomping remotes, which get forced upon whoever buys the system. Then Sony decides to ape them and make their own rendition. The one motion control system that I hate the most though is the Kinect.

To me, the Kinect represents the idiocracy of videogames. The overwhelming majority of games that use it are subpar titles at best and the only halfway decent one is actually hindered by requiring a Kinect for the best experience. (Cough, Child of Eden) Furthermore, the Kinect really is not friendly with regard to those who are physically handicapped or have limited mobility. This is only one reason for my strong hatred for this high tech toy.

Nom

In the course of the past year, I have seen quite a few good and bad habits pertaining to programming. One reason for the bad habits is sadly, some of the subpar entry level books that really don't have good programming practices. As a result, I figure that I should mention a few tips for an object oriented programming language that may make programs more readable and more beneficial.

1. Do not make methods bigger than your head. Seriously, a good method should really never exceed 15 lines of code unless it absolutely has to. If need be, split it into smaller methods to handle various aspects of the task if it is more beneficial. If this cannot be done, then refactor the program or possibly restart from scratch on the method.

Before I proceed with my planned entry, I figure I should apologize for my recent absence. As RaT and some of the other SX members will mention, since the start of 2010 I have been going to school full-time with very short summer breaks. Hopefully though I can contribute something on a weekly basis even if it is something short.

As of recently I have noticed a horrendous trend on the forums that I would like to see disappear.

For some reason, just about every forum thread of recently has regarded Computer Repair, Virus Removal, Help me do this, etc.

I WANT TO BE CLEAR - LMGTFY posts about computer repair will put you on my ignore list for the forum.

I've pretty much blacklisted several forum members for posting non-stop garbage threads about crap they could goggle.

This is my personal warning to all forum members (may or may not reflect other Crew/High Council):

This is a forum for security concious individuals, operated by said individuals, for like minded people.
I do not care to help you with your Windows Install, Virus Removal or fixing your fucking printer.
I come to this forum in search of additional knowledge, if you are posting threads that do not relate to security I will promptly ignore you, not just your thread.

I absolutely love the nature of opensource: anyone can check your code for errors and patch any bugs. After talking a little with a random developer who's interested in libhijack, he found a bug where I'm accessing a variable after calling free() on it. The fix was simple and he provided a patch for it. I'm releasing version 0.5.1 of libhijack today to fix the bug. It's a minor release. I'd recommend everyone to use this release rather than 0.5 formal.

You can find libhijack at its usual spot on SX Labs.

Libhijack 0.5 has been released! This is an exciting major milestone release. The major features in this release include:

Uncached function searching
Hijacking within shared objects

This release has broken two external API calls:

MapMemory
FindFunctionInGot

You'll need to pay attention to any code you've written to make sure it still works. The above API calls are completely working, but the function prototypes have changed. I've worked very hard for this release and I hope it's bug-free. I've plugged quite a few memory leaks. Check out the Texts page on 0xfeedface.org's site for the Defcon presentation slides.