284 karma · joined April 19, 2019
PS: Sometimes I think some researchers think they're helping themselves keep their research proprietary so they will able to monetize their special knowledge or implementation, especially if no one else can make it work ("knowledge" (job) security/silo). Why do the hard work of figuring out how to make a novel AI/ML algorithm if it can be readily commercially monetized without recompense? (Modern Western civ doesn't have a good patronage system to uniformly support arts, trades and sciences.)
Frankly, someone who hasn't:
- written a self-bootstrapping compiler
- designed and microcoded a branch-predicting, pipelined processor
- written a toy OS that works
- spent an inordinate time with assembly
- ran fuzzing against a library
can't legitimately call themselves an engineer. People who don't grasp the implications of their implementation decisions are vast the majority... and how many of them can fix things when something malfunctions at a layer that they they're unwilling/incapable of debugging? Either they can depend on some other specialists, find a local generalist engineer to fix it for them or they can "be the change they seek."
# change default shell to newer brew'ed bash
brew install bash && sudo dscl . change /users/$USER UserShell /bin/bash /usr/local/bin/bash
# change default shell to newer brew'ed zsh
brew install zsh && sudo dscl . change /users/$USER UserShell /bin/bash /usr/local/bin/zshHead transplantation is still too "out there."
Also, programs should be able to dynamically-serve the contents of "files" as well with an "activation symlink", i.e.,
/etc/resolv ->* resolvconf
The "the everything must be plain text" refrain is obsolete and unnecessary because it's trivial to serialize anything to any format since it would already be an universally-supported data structure both in tools and code.It's not 1978 anymore.
In previous life, I inherited a bunch of Win2k database servers that were running on unfiltered public IPs (yuck!).. and several of them had undetectable, stealth rootkit malware that wasn't economically-feasible to remove (Microsoft and Winternals were in the loop).. and because they "couldn't be reimagined," network rules were used to disconnect it from bot operations. Yuck. Don't put unsecured or fragile anything on public IPs because odds are they will be pwnes with variants of malware no AV has ever seen, and it will be a persistent threat (APT) that won't be evident until later.
The best defenses include, but aren't limited to:
- Never run untrusted code.
- Never allow untrusted write and execute.
- Don't do email / browser operations with admin credentials. Do it in a VM maybe or a separate machine as a normal, unprivileged user is best.
- Least privilege, all the things.
- Verify cryptographic signatures enforcing chain-/web-of-trust of source/binaries/packages.
- Holistic defense-in-depth.
- Minimalism/minimal attack surfaces.
- Don't run fragile, unconfigured OSes on unfiltered public IP's. (Please.)
Speaking of Hadoop: my vehicle is parked outside one of the HQ's of another top 10 Hadoop startup. It's one of the most expensive, nearly empty buildings in the highest rent areas of the Valley. (Money flushing sound here.)
Fun fact: one of the enterprise Hadoop CTOs is a broney.
And a combination of slow and rapid food price increases such that the eventual sole focus of nearly everyone's existence will be mass distractions from insanely unaffordable food, mass starvation and potential genocides. If a modern person wants food security, they better have a climate-controlled, well-defended and discrete area to grow enough for their family... otherwise X.X.