either create a cert group and give that group permission to the certs, or add a handler to distribute the cert+key on renew to your service’s folder, and change owner/group to whats relevant to the service
Note: the “live” folder only contains links to the archive folder
Are the links correct? @anoyongbot
Msn is google?
Run iperf internally to see if your bottleneck is switch/ap or fw. I set up a j1900 pfsense for my sisters family a while back to do qos (gamer bois in the house) amd it had no problem staying at 500mbps. No ids or other stuff.
Not built any opn/pf-sense in a while, but i always use intel server-nic’s. Used to have way better support than other stuff on bsd
He was a fucking prick - and you seem to be as well.
Yeah, but if your house burns down copies on different hdd wont matter much. Offsite like cloud will
Basically why i feel more comfortable with LXC than docker for my home lab services. It feels more like a VM in management.
We run a good mix of docker, vm’s and bare metal at work; no containers are auto-updated
Stick to strong keys and keep it on 22 for ease of use
No - ssh is very easy to secure, while an exposed web-service is very hard to secure. Theres no difference in the security of ssh without password and for example WireGuard.
I totally agree, this is just my thoughts on why. I vibe on the sunny side of the pond, but we are terrified to what donald can do to foreign policies- we are not yet prepared to handle our security our selves
some plants like raspberry can propagate through roots. Others like strawberries have stolons. And theres plants like blackcurrant where branches can root when they hit the ground.
But mostly its done by humans through cuttings.