1 karma · joined March 4, 2021
Tweets make excellent momentary entertainment. Let's stop using them for anything else.
> It seems like the important stuff that differentiates the expert from someone with casual knowledge isn't documented.
Experience is the biggest driver of expertise, and most people just don't document the things they find out unless they have to. But often the information does exist, if it's been around for a while. Ask yourself how the expert became an expert. What other fields might they have studied? What jobs might they have had? What similar subjects might reveal some of the details?
> Sometimes its not, but the knowledge seems to be locked in the brains of a few individuals or organizations and can only be unlocked if your'e lucky enough for them to take you in
Yep. Working with others is an important part of building expertise. Building relationships opens up new pathways to find information.
> On the other hand, a minority of the experts I know are nearly completely self taught and I'm struggling to figure out how to manage.
Relax. Expertise is not something you can force, it comes with time. Some things are easier than others, but if you continue to slowly work at it, you'll get better.
> Generally as a hobbysit Like I said every time I've tried to deep dive I reach a point where I'm not sure what I'm missing, where to find it.
Not every fish can be found by diving deep. Searching for knowledge is a normal part of building expertise; don't stress if you're not immediately sure where to look. If you get stuck, start again from the basics and question your assumptions. Try thinking about it from both a low-level and high-level view. Try to change your perspective. You will invariably come up with new places to search.
As you search, write down questions. If you get stuck on one, start looking into another. Remember to take breaks and get enough sleep, exercise, good diet. We learn best when we are stress-free, healthy and happy.
Comparatively, the kids aren't dying, they don't have bills to pay, they don't work overtime. Their parents may even be able to pull them from school, or homeschool. Worst case they might be held back a year.
The students will survive this, but the teachers literally might not.
People tend to forget that big companies are really just collections of normal people who are not lawyers and don't even think about licenses. If 5 levels of managers haven't all been explicitly instructed to read random software licenses or they're fired, the engineer's not gonna do it unless they feel like it, and most don't feel like it. It mostly only comes up when legal goes out of their way to make a stink about it, and they're not just continuously demanding license information.
That would require removing emotion from our biology. Maybe shoot for something smaller.
If your corporate IT group regularly asks users to send in their passwords via e-mail in order to perform some remote maintenance, then the users will be habituated to sending their password to a familiar e-mail address. If someone from outside their company asked them for their password, they would immediately say no. But an e-mail with the right "From: " address, they would quickly fall for. So it becomes easy to trick the users into sending their password to an attacker in some circumstances, because of the assumptions they make.
Security by obscurity is just another form of this: a practice which isn't really secure, but people may think is secure, because it seems to avoid the simplest, most stupid attacks. But literally any action you take could prevent the simplest, most stupid attacks. That doesn't mean that any action you take makes you "more secure".
Hiding a key under a door mat or in a sun visor isn't "more secure" than leaving it in plain view. Anyone who's not a total moron will find it, and if that's your whole security posture, you're screwed.
Protocol-wise, isn't it common now for the NP on higher end stuff to handle L4 and higher protocols? Or are those still largely managed by the CPU?
I know everybody likes Fail2ban, but these two iptables rules (or something just like them) actually work better and don't fill up your logs:
iptables -t mangle -A PREROUTING -p tcp --dport ssh -m conntrack --ctstate NEW -m recent --set
iptables -t mangle -A PREROUTING -p tcp --dport ssh -m conntrack --ctstate NEW -m recent --update --seconds 60 --hitcount 4 -j DROP
To actually protect the network layer, use some kind of VPN with MFA.Unlike Lady Justice, cops are not blind at all - they can pick and choose when to enforce the law. I forget what it's called, but the police are literally given the option for some laws to just not enforce the law if they don't want to. If the cop is in a good mood, they can decide to just let it slide. If they're in a bad mood (or they don't like the color of your skin) they might prefer to enforce it.
It's pretty easy to write your own Distro and pair it down to the essentials, and pairing it down that way allows you to strip out complexity, making it easier and more reliable to patch it. But that then means you are now maintaining this custom thing forever. If you're Amazon, that might be fine, but I suspect that this will be dropped when it is no longer profitable or a competing project supplants it - meaning in 5 years this thing might be gone. (A common theme of custom Linux distributions)
And then there's troubleshooting. With a stripped-down distro, you will eventually need more tools to debug the thing, meaning you have to build and maintain packages to do that. Bottlerocket's answer to this is "run them in containers and use our API!", but I'm not sold on this. Have you ever tried to do debugging between host and container, or container to container? There's a lot of b.s. you have to hop through, and most Unix tools were not written with it in mind. I highly doubt that it will magically work for everything. If that's the case, then this "don't worry, because magic" idea is not really saving you work over maintaining a traditional OS.
Moreover, you don't need a custom distro to do live patching. There are simple tricks you can use to juggle files and processes during a live patch, to say nothing of "checkpoint process && 'mv old_file new_file' && thaw process", etc. Kernels support live patching too. So if the argument is "well it's easier to patch", i'm not sure you're not trading away "easy" in one place for "pain in the ass" in another (see above). All of this also argues that it's just as effective to treat live-patched systems as you treat immutable infrastructure, and I'm not convinced of that argument either. The former is just more complex, and complexity attracts failures.
Ultimately I think what you'll find is Bottlerocket will get a niche following, but also some people will get annoyed by it and go back to regular distros which already have well defined methods.
# In your CI pipeline, something like this:
$ cat Dockerfile
ARG release_tag
FROM baseimg:${release_tag}
# etc; i think the container metadata keeps the base version, or you can store it in the container with a RUN line
$ base_version_tag=$(./get-latest-versioned-tag.sh some-docker-repo:my_prefix/my_image:stable)
$ new_container_version=$(./make-new-version.sh)
$ docker build -t my_img:${new_container_version} --build-arg release_tag=${base_version_tag}
Then you run your tests on the new image, maybe do a gradual deployment, and can quickly roll back to the last base image or skip broken versions. Your own container version is always rolling-forward, and you can revert the base image version at any time.If you do this with a specific stable tree (like debian:8-stable or something) you should only get security updates, but if you use :latest, that's a total nightmare.
From a stability, reliability, and CI/CD performance standpoint, I would discourage building your own Python. Things break more the more often your base version changes.
If you don't use Docker containers, use some other form of Immutable Infrastructure like Packer VM images. But those are huge and clunky, so you should really get used to Docker containers. You could instead make Linux packages, but they don't make for as Immutable a system as the OS state constantly changes, and packaging is more work in general.
Docker containers builds are extremely repeatable. You run some software called Artifactory, which keeps the built versions of your artifacts, including base image tags. You store your applications in there, as well as the Docker containers that you built. If you need to go back a version, you pull it out of Artifactory. This is industry standard at this point.
This isn't containerization best practice, this is just plain old Ops best practice that we've been doing for decades. The new part is doing it with containers and building immutable images rather than continuously muting state.
Also, a bunch of the people reading HN work for different vendors, so light up the comments about specific problems with specific products and we can take them directly to the people who can fix it.