Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
#!/usr/bin/env bash | |
# set -x | |
if [[ $EUID -ne 0 ]]; then | |
echo "You must be root to run this script" | |
exit 1 | |
fi | |
# Returns all available interfaces, except "lo" and "veth*". |
^([0-9]+)\.([0-9]+)\.([0-9]+)(?:-([0-9A-Za-z-]+(?:\.[0-9A-Za-z-]+)*))?(?:\+[0-9A-Za-z-]+)?$
# ------------------------------------------------------------------------------ | |
# tlp - Parameters for power saving | |
# See full explanation: http://linrunner.de/en/tlp/docs/tlp-configuration.html | |
# dir: /etc/default/tlp | |
# Hint: some features are disabled by default, remove the leading # to enable | |
# them. | |
# Set to 0 to disable, 1 to enable TLP. |
#!/bin/bash | |
set -e | |
set -o pipefail | |
# Add user to k8s using service account, no RBAC (must create RBAC after this script) | |
if [[ -z "$1" ]] || [[ -z "$2" ]]; then | |
echo "usage: $0 <service_account_name> <namespace>" | |
exit 1 | |
fi |
⛔️ This Gist is no longer maintained ⛔
There is now to much old/mixed stuff, which makes it impractical to read/use.
I keep it for reference, but expect it to be delete at some point.
run tcpdump on a POD and then (live) see that information through wireshark locally on my machine. the magic of ssh and fifo | |
Topology | |
-------- | |
[laptop with wireshark] ------> [AKS Node] ----> [POD (tcpdump is here)]. | |
1. create the fifo on your local machine (where wireshark will run) | |
mkfifo /tmp/remote-capture.fifo | |
2. execute the following command to send traffic from within a POD to the stdout. This will then be redirected to the fifo locally |
Nginx can be configured to route to a backend, based on the server's domain name, which is included in the SSL/TLS handshake (Server Name Indication, SNI).
This works for http upstream servers, but also for other protocols, that can be secured with TLS.
nginx -V
for the following:
...
TLS SNI support enabled
A curated list of arrrrrrrrr!