I hereby claim:
- I am callowaysutton on github.
- I am calloway (https://keybase.io/calloway) on keybase.
- I have a public key whose fingerprint is 0F92 C7AD D8F0 CF46 7E2A 266C B3D0 C92B DB65 CA93
To claim this, I am signing this object:
// Use Gists to store code you would like to remember later on | |
console.log(window); // log the "window" object to the console |
I hereby claim:
To claim this, I am signing this object:
A game where the moon helps at the darkest hour, the sun helps always but maybe not as much.
Has a deep message where the everything is good when it's light out because everything is bright and happy but when the sun goes away and it becomes night time only the moon can help the main protagnast at the darkest point.
Maybe have it to where monsters come out during the night and you are on an adventure exploring the landscape and killing monsters that come out during the night.
The setting is a post-apocalyptic futuristic world that you have to explore.
A 2D Side-Scroller adventure game with art being a major factor.
HOW TO CRACK, by +ORC, A TUTORIAL | |
LESSON C (1) - How to crack, Cracking as an art | |
[BARCODES] [INSTANT ACCESS] | |
[BARCODES] | |
First of all, let me stress the importance of cracking in | |
our everyday life. Cracking it's not just about software, it's | |
about information, about all patterns of life. To crack is to | |
refuse to be controlled and used by others, to crack is to be | |
free. But you must also be yourself free from petty conventions |
Chapter I How to Crack | |
------------------------------------------------------------- | |
Let's start with a simple introduction to patching a program | |
using the DOS DEBUG program. The following article will in- | |
troduce you to the basic ideas and concepts of looking for a | |
certain area of a program and making a patch to it. | |
------------------------------------------------------------- |
Assembly for Crackers - v1.0 | |
---------------------------- | |
Hey, This is a very basic guide to assembly for all those people who couldn't be bothered learning the in's & out's of their computer just to be able to use mIRC without having to click on some guys face. :) | |
I'll basically go through the most necessary stuff that you need to know before you can begin to crack. I know it's not in a very logical order, but what d'ya want for free? ;)) | |
Oh yeah, you should view this with wordwrap on, otherwise it'll be a pain in the arse to follow ;) | |
VOL 1 NUM 1 | |
HOW TO CRACK, by +ORC, A TUTORIAL | |
Lesson A.1: Advanced Cracking: Internet Cracking (Unix) | |
-------------> INTERNET CRACKING: FIREWALLS | |
With each new company that connects to the "Information | |
Superhighway" new frontiers are created for crackers to explore. | |
Site administrators (Siteads) have implemented various security | |
measures to protect their internal networks. One of these is | |
xinetd, covered later. A more general solution is to construct |
apiVersion: v1 | |
kind: Pod | |
metadata: | |
name: ubuntu2 | |
spec: | |
containers: | |
- name: ubuntu2 | |
image: nginx:latest | |
resources: | |
requests: |
#include <linux/bpf.h> | |
#include <bpf/bpf_helpers.h> | |
// Define a per-CPU array map to keep the packet count | |
struct { | |
__uint(type, BPF_MAP_TYPE_PERCPU_ARRAY); | |
__uint(key_size, sizeof(__u32)); | |
__uint(value_size, sizeof(__u64)); | |
__uint(max_entries, 1); | |
} packet_count SEC(".maps"); |