If your firewall can set outbound rules, and you can control DHCP on your network so that you can reliably know the TV’s IPv4 address, you can block the TV from reaching beyond the local network there with a “deny all from source address of TV” type rule.
If your router/firewall is handling IPv6 though, it gets a lot more complicated, since the TV could have any number of addresses that change often.
I’d recommend a full battery calibration before running the command one more time, if you haven’t already (charge the battery fully, leave it on the charger at 100% for a while, then fully discharge until it shuts itself off, leave it for a bit, then fully recharge while off). If the calibrated values line up with a full:design ratio of ~80%, especially with a 10-year-old battery with almost 700 cycles on it, my take is that’s pretty great.
That said, I think the best way to get an accurate feel for the health of an old battery is to put it through one full cycle of normal use and time how long it takes to die.
If you’re genuinely worried about this, you shouldn’t be using untrusted machines for remote access.
Apache Guacamole might be a good option. “Clientless” (browser-based), supports various mfa, uses ssh/vnc/rdp on the backend.
However, if the data on that machine is sensitive, or if that machine has access to other sensitive things on your network, I’d suggest caution in allowing remote access from untrusted machines on the wider internet.
He volunteered.
Heyr himna smiður - a medieval Icelandic hymn, set to music by Þorkell Sigurbjörnsson
The only legitimate commands for a non-root shell are sudo -i, exit, and echo "yee haw"
powertop is a cool tool that can analyze your machine and provide a list of suggested power optimizations
That’s awful, I’m sorry :(
Is your ISP’s infrastructure based on RFC 1149?
DNS is what you’re looking for. To keep it simple and in one place (your adguard instance), you can add local dns entries under Filters > DNS Rewrites in the format below:
192.xxx.x.47 plex.yourdomain.xyz
192.xxx.x.53 snapdrop.yourdomain.xyz
Now that’s a name I’ve not heard in a loooong time.
What is your root filesystem installed on - lvm, zfs, or bare disk partitions? Are you booting with grub (legacy/bios) or systemd-boot (uefi)?
Altruistic behavior in social creatures improves the fitness of the group, and has positive evolutionary pressure. Strong, cohesive groups pass on their genes, so actually pretty probable!
I’m with you there. It’s all layer upon layer of vulnerability and false security, and then at the bottom of all of it lurks the Ken Thompson hack.
Still bad advice to tell people it’s okay to use an explicitly vulnerable OS, I think.
Would you advise your enterprise clients that running Windows unpatched is ‘not a big deal as long as you have patched web browsers and AV’? Of course not. Because that’s dangerous advice and could even open you up to legal liability.
So why would you advise otherwise to home users, who are often more vulnerable in the first place?
Not having security patches on a system you do things like go to your banking website on is actually a pretty big deal, and I don’t think it should be dismissed lightly. Also AV is mostly snake oil, and is in no way an adequate substitute for a properly patched OS.
Thank fucking god for the EU, for fighting for global digital rights where nobody else does.
The standard of “you will be prosecuted and punished for publicly criticizing the ruling party/leader” certainly disqualifies China from being called a democracy, regardless of how many students they massacred or why.
There should be a section in the configuration about dhcp, which is how ipv4 addresses are given out on your network. What happens is when a device first connects to the network, it sends out a broadcast with its mac address - the dhcp server (in this case, your router/firewall) hears this, and sends back a reply allocating an address. You should be able to see a list of currently allocated addresses, and hopefully configure reservations to make those allocations permanent. To reserve an ipv4 address for a specific device, you need that device’s mac address.
Each item on that current allocations list should have a hostname, a mac address, and an ipv4 address. If it’s not clear by the hostname which device is the tv, you can look up each mac address and deduce from there (the first part of each address is unique to a specific manufacturer).
Once you have an ipv4 address reserved for the tv, you can set your outbound firewall rule to block it.
Ipv6, as I mentioned, is much more complicated. It might be possible to disable it completely on your router, and that’s likely the only way to block the tv from using it, but then your whole network will lose ipv6 capability across that boundary (probably not a lot of downside to that, though).
Good luck!