The mechanism: emergency injunctions against executive implementations.

The “switch” was not Congress changing SCOTUS authority. It was the Court becoming more willing to use existing tools:

* Supreme Court Rule 22 emergency applications

* All Writs Act (28 U.S.C. §1651)

* stay/injunction authority pending appeal

The important doctrinal shift was that the

Old model:

“We need to prevent irreversible harm while the courts finish deciding.”

Emerging model:

“We will temporarily block a major government policy while litigation continues.”

That distinction is what later became controversial.

Several forces converged:

ACA litigation created repeated emergency applications

The Affordable Care Act produced many disputes where:

* federal agencies were implementing rules,

* plaintiffs sought immediate relief,

* district courts and circuits disagreed.

Little Sisters (2013-2014) became THAT template, not the Clean Power Act of 2016.

(Deep-breath in, warning: rant)

This makes for a very problematic of continual hijacking AS link pathways between two hosts, notably between two countries.

BGPsec is well designed but remains largely unused (due to high-speed carrier-grade router's unwillingness to update firmware for new packet datagrams within BGP, not to mention requiring the addition of expensive de-crypt/re-crypte chipsets.

Interim SW-based solutions like BGP-ROA and BGP-ASPA are like HTTPS CAs, need to do PGP-style "trusting your friends' trusting other friends', ad naseum.

Alice trust Bob who trust Charles who trust Dave but Dave stabs Alice in the back. Um, no.

27 years of hosting my websites and DNSSec, but I can't prevent an island of Antigua to hijack my very own AS ... without all engaging in BGPSec. Unless all participate in BGPSec.

Crappy workaround such as the self-hosting of a RPKI API server is the HTTPS CA for that BGP AS hijack problem and it's still a wild, wild Internet.

Even then, that boondoggle infrastructure (Google/CloudFlare/DigiCert/LetsEncrypt) of mass Certificate Transparency (CT) monitoring station is trying to do fingerprint imprints of all the CAs' hash values for all websites; that design approach is time-sensitive and is a glaring weakness for not using dTLS/mTLS (where web servers ALSO authenticates its clients as well as the standard TLS client also authenticates web servers.

It is a lame brain scheme to ensure expansion of CT.

The correct architectual security stance is to prevent expensive audit scenario and ensure that the complexity moves from after-the-fact detection (CT) into stronger identity enrollment and authorization (DNSSEC, policy records, key continuity, CA constraints, possibly multi-CA approval).

People making more useless work, yet profit massively.

By doing individual CA with each websites, browser can then ditch the cookie tracking. And privacy restored (it leaks only to that website what you say)

But the $710B data collection industry will have questions.

I absolutely love the idea of auto-creating mTLS/dTLS for each client-website pairing at account creation time.

Ancillary infrastructure crumbles. Backends simplified. Things are faster and simpler for all parties involved (except those evil 3rd party scrapers/sniffer/email-reading scourges.

AI responded as: Benefits:

* eliminates password reuse

* reduces phishing surface

* eliminates many cookie-tracking mechanisms

* allows per-site identity isolation

* improves API/service authentication

the endpoints own the trust relationship; intermediaries provide transport, not identity.

Exactly how a well-designed military or critical-industrial equipment in the field should behave (to prevent inadvert usage of captured/hijacked endpoints)

/end-of-rant

Token rate is 0.091 per second.

Good for an overnight job.

Absorbent pad adds to the price also hides the "purge".

Harder to find meat without thousand poked holes (tenderizing)

Can't tell if meat are colorized to hide browness.

Time for me to visit my local butcher for a quarter cow, butchered.

Also a bigger freezer chest too!

"Packed On" or "Processed On" is the most accurate way to label meat, IMHO.

My home lab requires:

* Option 42 (custom NTP configuration)

* Option 66/67 (TFTP/PXE boot)

* Option 119 (Domain Search List)

* Vendor-specific options (43)

* Option 121 (Classless Static Routes)

* Custom enterprise options

+ DNS name Regex replacement (iPod/WII/Lucent DSLAM)

In RedHat dominated network, NetworkManager remains the dominant choice for:

* Enterprise desktops

* Laptops

* Many enterprise servers

* Complex managed networking in the Red Hat ecosystem

RedHat is still struggling to replace my network-manager's ultimate stackable network interfaces (VxLAN-VLAN-Bond-GRE-IPSec).

Furthermore, it isn't about hate. It is about KISS: it is about keeping PID 1 as simple as possible, something that all embedded systems and secured system should still aspire to do.

PId 1 should be pro forma and semantically secured as possible with minimal dependencies.

And process certainly should not be default all-privilege.

Simplicity of integration over complexity.

Think hard (time, money, resources)

Write down solution

Profit!

I always started with 3 words

POINT LASED CRUMB

This eliminates not only the most frequent letters but least frequent letters (Bloom filter), leaving rest of infrequent letter set to guess by narrow deduction.

Never failed me.

Skip the D2 vitamin.

Or a psychiatrist to tame the craxy LLMs

Or an elected leader to lead the Luddites.

https://github.com/vishal-dehurdle/state-harness

Coupled with SIT, pyrethroid, doramectin, ivermectin, debriding, dressing are just about 100% effective.

Thanks to our enlarged 230-strong Federal-contracted field workers.

For as long as LLM use the probabilistic predictive next-token for an algorithm, there shall be glaring errors when encountering a complex-logic (or even compound-logic).

In short, use AND, OR, NOR, XOR sparingly when doing AI prompt. Elevate your err-dar when doing so.

Unicorn is a nearly-true software-based CPU emulator for ARM, AArch64, M68K, Mips, Sparc, PowerPC, RiscV, S390x, TriCore, X86 CPU (and memory) architecture.

This pair-up is arguably the best set of software tools out there.

QEMU? No worry, that's way back in QEMU v1.4 days (emulation of Intel IMUL lb/DWORD OPC_IMUL_GvEvlb opcode getting tripped up by XOR opcode doing self-modified operand and TLB cache didn't flush, resulting in a double XOR; ROT13x2 anyone?)

Fabrice fixed it then and is still blazing at QEMU 10.0 now. Ain't he awesome?

Yeah, I actually ran portion of TLB of QEMU thru unicorn back then.

https://github.com/unicorn-engine/unicorn/issues/364

But wait, there's more: SSH config, resolv.conf, DNS RR setup.

A lomg checklist for successful SSHFP deployment:

https://egbert.net/blog/articles/dns-rr-sshfp.html

Ok.