jmingov

# get total requests by status code
awk '{print $9}' /var/log/nginx/access.log | sort | uniq -c | sort -rn

# get top requesters by IP
awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head | awk -v OFS='\t' '{"host " $2 | getline ip; print $0, ip}'

# get top requesters by user agent
awk -F'"' '{print $6}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head

# get top requests by URL

jmingov

if [ ! -f .env ]
then
  export $(cat .env | xargs)
fi

jmingov

#![feature(mpsc_select, box_syntax)]

use std::io;
use std::process::Command;
use std::sync::mpsc::{channel, Receiver, Select};
use std::string::FromUtf8Error;
use std::thread::spawn;

#[derive(Debug)]
enum PipeError {

jmingov

<?php

/**
 * Session Helper Class
 *
 * A simple session wrapper class.
 *
 * Recommended for use with PHP 5.4.0 or higher. (Not required.)
 * 
 * Usage Example:

jmingov

package main

import (
	"fmt"
	"log"
	"math/rand"
	"time"
)

type Threader struct {

jmingov

GitHub for Bug Bounty Hunters

GitHub repositories can disclose all sorts of potentially valuable information for bug bounty hunters. The targets do not always have to be open source for there to be issues. Organization members and their open source projects can sometimes accidentally expose information that could be used against the target company. in this article I will give you a brief overview that should help you get started targeting GitHub repositories for vulnerabilities and for general recon.

Mass Cloning

You can just do your research on github.com, but I would suggest cloning all the target's repositories so that you can run your tests locally. I would highly recommend @mazen160's GitHubCloner. Just run the script and you should be good to go.

$ python githubcloner.py --org organization -o /tmp/output

jmingov

#/bin/bash
#
# Download toolschains:
# git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7 toolchain
# git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9 -b  marshmallow-release toolchain64
#
# Instructions to set toolchain for build:
# source setupenv 64

case "$1" in

jmingov

wget https://storage.googleapis.com/golang/go1.8.1.linux-armv6l.tar.gz
sudo tar -C /usr/local -xzf go1.8.1.linux-armv6l.tar.gz
export PATH=$PATH:/usr/local/go/bin

wget https://nodejs.org/dist/v7.10.0/node-v7.10.0-linux-armv7l.tar.xz 
tar -xvf node-v7.10.0-linux-armv7l.tar.xz
cd node-v7.10.0-linux-armv7l

jmingov

#!/boot/bzImage

# Linux kernel userspace initialization code, translated to bash
# (Minus floppy disk handling, because seriously, it's 2017.)
# Not 100% accurate, but gives you a good idea of how kernel init works
# GPLv2, Copyright 2017 Hector Martin <marcan@marcan.st>
# Based on Linux 4.10-rc2.

# Note: pretend chroot is a builtin and affects the current process
# Note: kernel actually uses major/minor device numbers instead of device name

jmingov

	// TLS config, do not set InsecureSkipVerify to true in production
	// since it will accept all certificates
	config := &tls.Config{
		InsecureSkipVerify: false,
		ServerName:         host,
	}

	c, err := smtp.Dial(server)
	if err != nil {
		log.Fatal(err)