Firewall rules are evaluated in the following order:
Allow if secure with Override block rules selected in the Customize Allow if Secure Settings dialog box.
Block the connection.
Allow the connection.
Default profile behavior (allow or block as specified on the applicable Profile tab of the Windows Firewall with Advanced Security Properties dialog box).
Within each category, rules are evaluated from the most specific to the least specific. A rule that specifies four criteria is selected over a rule that specifies only three criteria.
Which means that this will block TCP port 1024 traffic to bar.exe:
The Block rules are inserted by Windows if you click “Cancel” on a dialog like this (note the lowercase path, despite the application being at C:\Program Files (x86)\Foo\Bar.exe):
A posting at Brave New Geek about limits on everything, for example limits on message sizes and numbers of in-flight messages in message queues. Interesting read.
On my research list: Home – Outpan as it is a key-value store of EAN (actually GTIN, so including GS1 UPC, EAN which means barcodes like UPC-12, EAN-8, EAN-13 and ITF-14).
1.1.1.1 [Wayback] DNS is broken in many areas (because of for instance AT&T, Vodafone, Cisco screwing up and 1.1.1.1 historically being marked for research purposes)
9.9.9.9 [Wayback] DNS has government affiliation (owned by Quad9, but the partner list below does not look nice)
The services on Docker Cloud that provide application, node, and swarm cluster management will be shutting down on May 21.
…
If you do not migrate by May 21, your applications running on the Docker node cluster management service will cease to operate.
Swarms will continue to function; however, if you do not retrieve your SSH keys for the Swarms being managed by our swarm cluster management service, you will be unable to access your swarms using your Docker ID. For instructions on how to retrieve and access your Swarms with SSH keys, please refer to the Docker docs.
Yes, AKS is Azure Container Services (go figure!).
Notes
For burning, Scott recommends [WayBack] Etcher: Burn images to SD cards & USB drives, safely and easily (which is now also available as experimental [WayBack] Etcher CLI), I tended to use a script like below since I’m a command-line person, but since Etcher does write and verify in one run, I’m considering switching:
find where the SD card is mounted on your Mac: diskutil list
sudo su -
execute this from the directory where you downloaded filling in targetDevice with the value from diskutil list
