Jul/090
PHP Dynamic Images Tutorial
PHP has a built-in image manipulation library called GD. You can use it to create and manipulate images in your PHP scripts. What we'll be creating here is a signature image that displays some statistics from a MySQL database.
- Create or load an image
- Allocate any colours that you wish to use
- Write or draw on the image
- Set the MIME type of the document
- Output the image
This tutorial was written by Burningmace on our forums, if you would like to see the full tutorial on PHP dynamic images then click here.
Jul/090
Recovering drives with mechanical failure
Tutorial was originally posted by burningmace on vorbb forums, which can be found by clicking here.
You're bound to get the "clicking of death" at some point when dealing with computers. When the mechanical parts inside hard drives fail, they make clicking and bumping noises. You may also get "delayed write failed" messages from Windows and some freezing and glitching. The number one thing to remember is don't wait to let it get worse. The longer you leave it, the less chance there is of recovering data. It's not a complicated procedure, and it doesn't require much effort.
To see the instructions click more.
Jul/090
Google OS Illustrated
While surfing the web, I came across a fairly amusing and well done picture. It is not mine, I am just posting it here to share it with everyone.
Jul/090
How Tor Works
This was post was made by burningmace on our forums, you can go to the original link by clicking here.
Networks such as Tor provide complete anonymity to their users, but how exactly does this work?
Each computer running on the network is called a node. A node can forward traffic from and to any other node, as well as a target. A simple communication might work as follows:
Brian sends a message to Jane.
Jane forwards the message to Mike.
Mike forwards the message to Kate.
Kate forwards the message to James.
James reads the message and writes a response.
James sends the message to Kate.
Kate forwards the message to Mike.
Mike forwards the message to Jane.
Jane forwards the message to Brian.
Brain reads the response.
Or, simplified:
Client -> Node 1 -> Node 2 -> Node 3 -> Server
Server -> Node 3 -> Node 2 -> Node 1 -> Client
Each message is assigned an identification (ID) number. The number is unique to the message, and can be very large in order to avoid repeats of the same ID.
When the client sends the message to node 1, it generates a message ID. Node 1 stores the message ID and the IP it came from. The same happens for the messages send from node 1 to node 2, and from node 2 to node 3.
Node 3 communicates with the server and sends the response back to node 2, along with the message ID. Node 2 looks up the message ID, and finds the IP address associated with it - the IP of node 1.
Node 1 does the same, looking up the IP associated with the message ID so it may find the client. The client now has the response from the server.
Each connection between the nodes is encrypted, which means that no single node knows the source (client) and the message. The client and exit node (in this case node 3) know each other's public keys so that an asymmetric cipher can allow private communication across the network.
Here's how the encryption works:
- Without encryption, create a path of nodes to your exit node. Use this path to ask for the exit node's public key, and tell it your own.
- Generate a key for a symmetric cipher (e.g. AES or Serpent).
- Encrypt the key with the exit node's public key (e.g. RSA).
- Send the encrypted key to the exit node through the path of nodes. The exit node can decrypt the symmetric cipher key using its private key.
- Encrypt your message and the details of the server to send it to using the symmetric cipher key.
- Send this encrypted message to the exit node via the path of nodes.
- 7) The exit node decrypts the message using the symmetric cipher key sent earlier, and talks to the server. It gets the response and then performs the same operations back to the client.
- The client decrypts the returned message and reads it.
Jul/093
Cabal NA Cracker and Username Leecher
I've decided to repost this since im not sure if the links on the old post are still working. The currently working and up to date cracker is Cabal Cracker 2B by BurningMace. Bunringmace greatly improved on my version, by adding multi-threading, safe cross-threading and the list goes on. For more information on the Cabal Cracker 2B edition click here to see the post on our forums with the download link.
As for the leecher, it can also be found on our forums by clicking here. But since most of the usernames on the highscores have been locked out due to login attempts, they may be useless. Burningmace and I managed to get a hold of a list that contains every cabal online account. There are just under 2 million usernames on this list. If would like to purchase some bulk names for cheap prices and get some good gear, then check out the post on our forums by clicking here.