Damn… You too?
Damn… You too?
Hello fellow homelabber
Nerfing things on a PVE game that’s supposed to be fun shows a lack of creativity.
You can buff the other things while finding better ways to increase the difficulty, instead of just boosting health and throwing more enemies, but that’s the “easy” button.
It is nice that you got it running, but when everything you end up doing is running services in low ports or needing specific IP address in different networks, rootless podman is just a PITA.
In my case I have one pihole running on a docker container and another one that runs directly on a VM.
Someone said before “what’s the point of running in a container”… Well, there really isn’t any measurable overhead and you have the benefit of having a very portable configuration.
I do think the compromises one has to go through for podman rootless are not worth in this case, for me, not even the rootful worked properly (a few years ago), but this is a nice walkthrough for people wanting to understand more.
It is user friendly, and technically incorrect, since nothing ever lines up with reality when you use 1000 because the underlying system is base 8.
Or you get the weird non-sense all around “my computer has 18.8gb of memory”…
I can’t say if you are overstating it but, only mention that I went through a similar path. I had it multiple scripts running and it was a neverending thing.
Since I have moved to small step I never had a problem.
The biggest advantage I got is for products like opnsense, you can do automatic renewal of certificates using your internal CA.
Generating new certs is still as simple (actually much easier for me) than relying on openssl or easyrsa scripts.
What? Every BIOS in the world still uses the same system. Same thing for me on Linux.
Only hard driver manufacturers used a different system to inflate their numbers and pushed a market campaign, a lot of people who didn’t even use computers said “oh that makes sense - approved”
People who actually work with computer, memory, CPU, and other components in base 8 just ignores this non-sense of “x1000”
I feel like you just confirmed exactly what I said, few people were able to beat it.
To be fair, very few people used to be better at go, let alone a lot better.
I have dealt with “only works in kubernetes” because developers couldn’t be bothered to make it even work on docker without all the hidden orchestration.
So, instead of documentation, they just make the service work in that one specific environment.
I would argue they are all the same since most are based on wlroots and if wlroots doesn’t support something neither does the “increasing amount of Wayland compositors”.
By secure they mean “the only way we can easily see everything you do”
Weird numbering system? Things are still stored in blocks of 8 bits at the end, it doesn’t matter.
When it gets down to what matter on hard drives, every byte still uses 8 bits, and all other numbers for people actually working with computer science that matter are multiples of 8, not 10.
And because all internal systems use base 8, base 10 is “slower” (not that it matters any longer.
While I don’t use TPM myself (I dislike being tied to a specific hardware) the way it protects you is:
Disk is protected through encryption, so you can’t remove and inject anything/hack the password.
If boot is protected/signed/authorized only, a random person can’t load an external OS and modify the disk either.
All this together would say, even if someone acquires your computer, they can’t do anything to it without an account with access, or an exploit that works before a user logs.
In a way, the attack surface can be bigger than if you simply encrypted your disk with a key and password protect that key.
Saying Waze and Google in the same phrase is, unfortunately, redundant
You can always compile your own Iosevka and adjust several pieces, I have done that selecting what I consider the best pieces a long time ago.
The compiled font lives in an easy to access internal webserver that I just grab from every computer I use (=
I really love the current trend in R&D PowerPoints
There are a few ways to do it, but you don’t use caddy for SSH.
Last option is how I run my Gitea instance, authorized keys is managed by gitea so you don’t really need to do anything high maintenance.
~git/.ssh/authorized_keys:
command="/usr/local/bin/gitea --config=/data/gitea/conf/app.ini serv key-9",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,no-user-rc,restrict ssh-rsa PUBLICKEYHASH
/usr/local/bin/gitea:
ssh -p 2222 -o StrictHostKeyChecking=no git@127.0.0.14 "SSH_ORIGINAL_COMMAND=\"$SSH_ORIGINAL_COMMAND\" $0 $@"
127.0.0.14 is the local git docker access where I expose the service, but you couldn’t different ports, IPS, etc.