ssh-from
simplifies common usage of SSH tunnels, and makes double (or triple) tunnels a piece of cake.
Here is an example, where I SSH to a computer that is behind two NATs, tunneling through each router:
Details coming to the blog soon.
#!/usr/bin/env python | |
import multiprocessing | |
import imp | |
import urllib2 | |
import urlparse | |
urllib = imp.new_module('urllib') | |
urllib.error = urllib2 | |
urllib.parse = urlparse | |
urllib.request = urllib2 |
let f = (...args) => args[0].filter(p => p.gender == "male" && p.age > 30 && p.age < 40) | |
/* | |
Example: | |
const ppl = [ {"name":"Dr David Darmanin","age": 31, "gender": "male"}, | |
{"name":"Diana De Jesus","age": 32, "gender": "female"}, | |
{"name":"Marc von Brockdorff ","age": 33, "gender": "male"}, | |
{"name":"Christian Nussbaumer ","age": 29, "gender": "male"}, | |
{"name":"Erik Näslund","age": 35, "gender": "male"}, | |
{"name":"Shira Harash","age": 41, "gender": "female"}, |
ssh-from
simplifies common usage of SSH tunnels, and makes double (or triple) tunnels a piece of cake.
Here is an example, where I SSH to a computer that is behind two NATs, tunneling through each router:
Details coming to the blog soon.
This program adds proxy support to ssh. Once installed, ssh
will obey
the ssh_proxy
environment variable (or all_proxy
as a fallback) and
will try to connect to the server through that proxy. Example:
export ssh_proxy="socks5://10.139.2.1:8066"
ssh example.com # will connect through SOCKS5 proxy
; a hand-made GIF containing valid JavaScript code | |
; abusing header to start a JavaScript comment | |
; inspired by Saumil Shah's Deadly Pixels presentation | |
; Ange Albertini, BSD Licence 2013 | |
; yamal gifjs.asm -o img.gif | |
WIDTH equ 10799 ; equivalent to 2f2a, which is '/*' in ASCII, thus starting an opening comment |
# OSX for Pentesting (Mavericks/Yosemite) | |
# | |
# A fork of OSX for Hackers (Original Source: https://gist.github.com/brandonb927/3195465) | |
#!/bin/sh | |
# Ask for the administrator password upfront | |
echo "Have you read through the script prior to running this? (y or n)" | |
read bcareful |
#!/usr/bin/env sh | |
# (run)$ ./Dockerfile-recovery.sh <IMAGE ID> | |
docker history --no-trunc "$1" | sed -n -e 's,.*/bin/sh -c #(nop) \(MAINTAINER .*[^ ]\) *0 B,\1,p' | head -1 | |
docker inspect --format='{{range $e := .Config.Env}} | |
ENV {{$e}} | |
{{end}}{{range $e,$v := .Config.ExposedPorts}} | |
EXPOSE {{$e}} |
; a hand-made GIF containing valid JavaScript code | |
; abusing header to start a JavaScript comment | |
; inspired by Saumil Shah's Deadly Pixels presentation | |
; Ange Albertini, BSD Licence 2013 | |
; yamal gifjs.asm -o img.gif | |
WIDTH equ 10799 ; equivalent to 2f2a, which is '/*' in ASCII, thus starting an opening comment |