Cameron Tod cam8001

## set_java_home.sh
# @see https://stackoverflow.com/a/11542973/15088
export JAVA_HOME=$(readlink -f /usr/bin/java | sed "s:bin/java::")

## make_small_gif_ffmpeg.sh
#!/bin/bash
start_time=0:22
duration=2.5
scale=180
fps=15

palette="/tmp/palette.png"

filters="fps=$fps,scale=$scale:-1:flags=lanczos"

## imessage_dump.py
import os
import pwd
import shutil
from datetime import datetime, date

username = pwd.getpwuid(os.getuid()).pw_name
rootDir = "/Users/{}/Library/Messages/Attachments".format(username)
destDir = "/Users/{}/Desktop/imessage_dump".format(username)

IGNORE_STRING = "pluginPayloadAttachment"

## upgrade-python.sh
sudo -s
yum update -y
yum install -y python36
alternatives --set python /usr/bin/python3.6
pip install --upgrade pip
visudo
# Add /usr/local/bin to secure_path
source ~/.bashrc
# @see https://stackoverflow.com/a/40616976/15088

## dns-ubuntu.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                cam8001
                / dns-ubuntu.md
            
            
              Last active Jun 25, 2019
            
              
                Fixing broken DNS after dnsmasq freaks out on Ubuntu
              
          
      View dns-ubuntu.md
  
    
    FIRST - check what is going on with dnsmasq at /etc/dnsmasq.d/01-pihole.conf.
In my case, dnsmasq/pihole-FTL wasn't starting because it was binding to a non-existent network interface. I had moved an instance from t2.micro to t3.nano. t3.nanos use the nitro hypervisor, which presents network interfaces differently. So, my primary network interface name changed from eth0 to ens5.
Pihole's forked dnsmasq implemention is called pihole-FTL. Just try running that (type it into the console) and see if it fixes things.
If not:

In Ubuntu 16.04, 16.10, 18.04 and 18.10, dns is handled by systemd-resolved.
You can see how DNS is resolving by running systemd-resolve --status


## user_data.sh
#!/bin/bash
apt update && apt upgrade -y
snap install amazon-ssm-agent --classic
ln -fs /usr/share/zoneinfo/Pacific/Auckland /etc/localtime

## user_data.sh
#!/bin/bash
yum update -y
systemctl start amazon-ssm-agent
systemctl enable amazon-ssm-agent

## awscli.bash
# From here:
# https://blog.ashiny.cloud/page/awscli-query-quickref/

#!/bin/bash -ex
export AWS_REGION=your-region-here
export AWS_PROFILE=your-cli-access-profile-here
export AWS_DEFAULT_OUTPUT=text

# Get your user ARN
aws iam get-user --query 'User.Arn'

## purge_buckets.sh
#!/bin/bash
aws s3 ls | cut -d" " -f 3 | xargs -I{} aws s3 rb s3://{} --force

## all_apple_ips.txt
# Generated by:
# ASN=AS714; whois -h whois.radb.net -- "-i origin $ASN" | awk '/^route:/ {print $2;}' | sort | uniq
# @see https://ipinfo.io/AS714
#
# ASN=AS6185; whois -h whois.radb.net -- "-i origin $ASN" | awk '/^route:/ {print $2;}' | sort | uniq
# @see https://ipinfo.io/AS6185
144.178.0.0/18
144.178.0.0/19
144.178.48.0/21
144.178.56.0/21