Working on porting #SafeStack to arm64 on #HardenedBSD. I'm getting closer and closer.
#systemd
@Gargron @KitRedgrave
Yes, systemd has democratized a whole bunch of good practices that some/many (?) people were previously ignoring.
OTOH, it has terrible design, with a sprawling mass of new deamons that are functionally-worse rewrites of existing stuff (networking, DNS resolution, NTP, ...) and tightly coupled to the init+service-manger.
Even the latter has pretty crucial features missing: https://vulpine.club/@kellerfuchs/892595
#FreeBSD 11.1-BETA3 Now Available https://lists.freebsd.org/pipermail/freebsd-stable/2017-June/087303.html #bsd #unix
Tomorrow, I'll be MFC'ing all the #StackClash fixes from #HardenedBSD 12-CURRENT to 11-STABLE. I'll also write up a blog post about how we've decided to mitigate it.
@natecull in the cloud, it works like this:
1. i tell the service provider to delete my data.
2. the service provider says that it has deleted my data.
3. the service provider retains my data anyway.
I've setup my own instance to learn more about how this all works. I'm going to switch over to the new account and stop using this one.
There is not sudo by default in OpenBSD. Our main user machine is now no longer Linux and is OpenBSD. I'm not installing sudo on the machine. Mainly because of all the students who assume they can use sudo on *my* server.
So one of my faculty members and I have come up with the idea of what we now call "sassy sudo". Sudo on the new server will be a wrapper around fortune pulling from a sudo database.
"sduo: command not found"
"sudo: removing user account"
etc.
:)
FreeBSD enthusiast and regular contributor. I have opinions!