Parasites tend to do that to their host...
Darkassassin07
joined 2 years ago
Same, though I'm using acme.sh and DNS-01. (had to go look at the script that triggers it to remember, lol)
I check the log file my update script writes every few months just to be sure nothings screwy, but I've had 0 issues in 7 years of using LE now.
A paid cert isn't worth it.
I can't speak for OP; but I'm interested in exploring the entire toolbox, not just 'the official family'/what the one set of developers make.
https://docs.pi-hole.net/guides/dns/cloudflared/
I use pihole+cloudflared to translate all DNS requests on my LAN to DoH requests. Regular DNS isn't permitted to leave my network. (port 53 outbound is blocked)
Can't redirect/modify/monitor DoH requests like you can plain DNS.
The maths a little off, it wont last him 30+ years; but he's absolutely correct with that final statment. If he chugs a gallon of gasoline; he won't need to eat for the rest of his life.
Dress for the job you want...
If they are like me, they have probably already found ways to watch porn, monitor their crush's computer, read their email, and get into their webcam.
I got into quite a bit of similar mischief as a (pre)teen; but I didn't do any of it on equipment that I knew was monitored (at least, monitored and signed out to me....)
And again; I think that's a bit of a separate issue. These devices shouldn't be equipped with cameras, let alone have the camera monitored/accessible.
The actual activity happening on the device; running applications, what's on screen/in storage, even it's location (with informed notice of said tracking) sure. but there's no need to monitor/access the camera regardless of how or where the device is used.
A simple piece of tape fixes this problem. (plus education to teach students why, ofc)
kids take these computers home
I feel like that is the bigger problem. These aren't private/personal devices; students shouldn't be treating them as personal devices. Especially knowing it's a monitored device.
Properly educating students on the use of these devices is the solution. Not telling schools to turn a blind eye to the use of their own equipment.
Yeah, when i was in school; there were no devices issued to students. We had 'computer labs'. Ie; a room full of computers for student use. There was always one computer for the teachers to use that had a remote-desktop interface monitoring every screen in the room live. They could always see what you were doing, lockout your keyboard/mouse, blank your display.
This really doesn't seem any different.
I could understand outrage if students were require to install this on their own hardware; but school issued devices are under the schools monitoring and control. Always have been.
Why not both?
My primary DNS is pihole on a rpi dedicated to the task; but I run a second instance of pihole via my main docker stack for redundancy. Should one or the other be unavailable, there's a second one to pick up the slack.
I just provide both DNS IPs to LAN clients via DHCP.
Gravity Sync is a great tool to keep both piholes settings/records/lists in sync.