rollwagen rollwagen

TL;DR (to inspect azure cli traffic)

start mitmproxy
set proxy environment variable
tell the Azure CLI to not validate SSL
run az commands

mitmproxy

esxi (on mac mini)

prepare USB boot install drive

Format USB drive: Master Boot Record scheme and format set to MS-FAT (aka FAT32).
Use unetbootin.app to flash iso to drive.
Alternatively / as backup approach see Create a Bootable ESXi Installer USB Flash Drive on macOS

adding a USB datastore

Listening...

python -m http.server
Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ...

Scapy
- Crafting and sending single TCP SYN packet

from scapy.all import *

Vagrant using libvirt on macos

Pre-reqs

   brew install qemu gcc libvirt
   brew services start libvirt
   vagrant plugin install vagrant-libvirt

lsof / netstat on macos

lsof - list open files

display (list) all open TCP+UDP ports and grep for listening ones

sudo lsof -i -P | grep LISTEN

COMMAND     PID           USER   FD   TYPE             DEVICE SIZE/OFF   NODE NAME
launchd       1           root   11u  IPv6 0x26dd73cb700390df      0t0    TCP *:22 (LISTEN)
....

arch linux arm on esxi fling (on raspberry pi 4)

create / Register VM -> Linux / Other 4.x or Later (64bit) -> ...
- CD/DVD Drive: use a Linux ISO that can boot into a recue shell e.g 'debian-10.9.0-arm64-netinst.iso'; make sure "Connect at power on" is selected
- VM Options / Boot options: Firmware "EFI" (should be the default anyways)
power On VM -> should see GNU GRUB welcome screen (from debian ISO/cdrom) -> Advanced Options -> Rescue mode
- go through menu selections (language, keyborad, etc) until you have a shell ('Execute a shell in the intaller environment')
partition the disk; see also ArchLinux Wiki Partition the disk

aws cloudformation "validation"

consider the following sample cloudformation yaml file y.yaml

Resources:
  S3SampleBucketinstacks3bucketF253E29D:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: "Test_S3SampleBucketinstacks3bucketF253E29D"
      BucketVersioningConfiguration: Enabled

Dynamo DB Data Models and Modelling

It’s a bad idea to model your data in DynamoDB the same way you model your data in a relational database. The entire point of using a NoSQL datastore is to get some benefit you couldn’t get with a relational database. If you model the data in the same way, you not only won’t get that benefit but you will also end up with a solution that’s worse than using the relational database!

from Alex DeBrie: The DynamoDB book


	sudo vi /Library/Preferences/VMware\ Fusion/vmnet8/nat.conf
	sudo vi /Library/Preferences/VMware\ Fusion/networking

	sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure
	sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
	sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

	sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure; sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop; sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

	from flask import *
	import requests

	app = Flask(__name__)

	@app.route('/follow')
	def follow_url():
	url = request.args.get('url', '')
	if url:
	return (requests.get(url).text)