List of IAM Permissions
This is a list of controls that can be placed into an IAM policy document. All content comes from AWS documentation.
Something wrong? Try looking here.
Table of Contents generated with DocToc
##TCP FLAGS## | |
Unskilled Attackers Pester Real Security Folks | |
============================================== | |
TCPDUMP FLAGS | |
Unskilled = URG = (Not Displayed in Flag Field, Displayed elsewhere) | |
Attackers = ACK = (Not Displayed in Flag Field, Displayed elsewhere) | |
Pester = PSH = [P] (Push Data) | |
Real = RST = [R] (Reset Connection) | |
Security = SYN = [S] (Start Connection) |
Glossary:
command | description |
---|---|
cat /proc/mdstat |
show status of all raids |
mdadm --detail /dev/md0 |
detailed status of raid md0 |
sqlite3 /etc/pihole/gravity.db -header -csv 'select * from adlist' > adlist.csv | |
sqlite3 /etc/pihole/gravity.db -header -csv 'select * from vw_whitelist' > whitelist.csv | |
sqlite3 /etc/pihole/gravity.db -header -csv 'select * from vw_blacklist' > blacklist.csv |
When VPNs Just Work™, they're a fantastic way of allowing access to a private network from remote locations. When they don't work it can be an experience in frustration. I've had situations where I can connect to a VPN from my Mac, but various networking situations cause routing conflicts. Here are a couple of cases and how I've been able to get around them.
In this example the VPN we are connecting to has a subnet that does not conflict with our local IP, but has additional routes that conflict in some way with our local network's routing. In my example the remote subnet is 10.0.x.0/24, my local subnet is 10.0.y.0/24, and the conflicting route is 10.0.0.0/8. Without the later route, I can't access all hosts on the VPN without manually adding the route after connecting to the VPN:
##StevenBlack's list | |
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts | |
##MalwareDomains | |
https://mirror1.malwaredomains.com/files/justdomains | |
##Cameleon | |
http://sysctl.org/cameleon/hosts | |
##Zeustracker |
Tutorial and tips for GitHub Actions workflows
There exists common confusion about terminal colors. This is what we have right now:
Decoding the data in /proc/net/tcp: | |
Linux 5.x /proc/net/tcp | |
Linux 6.x /proc/PID/net/tcp | |
Given a socket: | |
$ ls -l /proc/24784/fd/11 | |
lrwx------ 1 jkstill dba 64 Dec 4 16:22 /proc/24784/fd/11 -> socket:[15907701] |