![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
I’m really curious if that’s still true for debian 12, it’s using a 6.1 kernel and stuff isn’t nearly as old.
I’m really curious if that’s still true for debian 12, it’s using a 6.1 kernel and stuff isn’t nearly as old.
Been hosting my email about as long, thinking about turning it in, or at least only making smtp exposed.
The address argument is a cop out, Wireguard works fine always on now, even in your home wlan if you’re fine with hairpin nat. Ios and android handle it well.
I block China and Russia, tempted to add a few others but those are easy outs (haven’t been to China in years, will figure it out if I am).
🎶 Real men, of Genius… 🎶
My udm is basically running either debian or Ubuntu with all the major apt packages so everything should work, though I don’t think most of the logs go through syslog, many go into their mongodb database I think.
Not Sure Actually.
Agreed, though recommend nginx as proxy, have it do ssl, can set it up with letsencrypt, but mostly you can run multiple services off multiple internal hosts as subdirectories (assuming they cooperate).
Works great for me.
Probably not, look into wireguard or tailscale.
I was fine till I hit sussin.
So in the end, it doesn’t even matter?
That was so much more fun than it had any right to be.
The rules now are generally: bare metal if that’s all the box will do, or it’s main task, container if it’s one of many services, vm if it’s a larger application you might migrate and i/o isn’t your limitation.
The line between container and vm is fuzzy, but bare metal means you’re making a design choice for that machine and if that or another application breaks the machine you’re screwed.
In a way freebsd is amazing for this, you put all applications in jails and don’t use the main userspace much, but the virtualiztion story isn’t quite there yet.
Lvm can get you 80% of the way to basic zfs. I’m a bit similar, old school Unix who likes debian because it makes sense, but storage is one of my dominating constraints so zfs is mandatory (even if I hate stuff like the way the arc works by default).
I did not know -J, I rolled my own because I’ve been doing it forever and many of my tricks (non-ssh included) aren’t as easily portable across different os’s.
For some reason ssh-copy-id has been failing for me sometimes lately because it can’t reach the agent, while cat always works, but I never learned much about the user agent, let me look into that now, thanks for the tip!
Have an alias so trusted hosts can bounce through my authorization host and end up on a tmux session on the targetted host. It has logging and such but mostly it’s for simplicity.
If I plan to use that connection a lot there’s a script to cat my priv key through the relay.
Have an scp alias too, but that gets more complicated.
For more sensitive systems I have 2fa from gauth set up, works great.
You got that baby? Great, I’ll send the next 500 much faster, tell me when you drop one and I’ll slow down again.
You have a problem with agile methodology, you have a problem with me, and I suggest you let that one marinate.
I’m sorry dad, I wasn’t trying to have a miscarriage!
Strongly second vaultwarden, covets so many cases for me.
Imagine being able to autocomplete months.
Let me clarify:
Recordsize is basically hash block size. If you want to change things you will always write in blocks up to the recordsize, smaller if the file is smaller, then calculate the hash based on that.
Smaller only helps for randomish accesses inside a file.