Nougat

Didn’t other Tesla models have catastrophic exploding suspension problems? Glad to see they fixed that.

C:\> They could steal your personal data without you knowing. </

Access is denied.

The solution must be a hammer, because I have one!

How is this remotely Google’s responsibility?

Other benefits:

• Multiple subscription profiles, so you can organize your subscribed channels into groups. “I want to watch stuff about cars and motorcycles - I choose ‘Motoring.’”
• SponsorBlock
• No stupid recommendations to drag you into despair, hate watching, and misinformation.
• Ability to never show shorts.

Downside:

• Max 1080

Shits.

It’s also possible to have Windows log in as a specific user at boot, without user input. Regardless of operating system, your logged on session is in the context of some user account, whether you interactively log in or the system does it for you.

The PIN is stored locally on the machine only. It doesn’t get synced with anything anywhere. It’s actually much safer to use a PIN for authentication because it’s four digits that you (well, maybe not you) don’t have to write down, and the only time it works is on the physical machine. The user account password can be long and/or complex, but if you’re only ever authenticating at the keyboard, all you have to remember is the PIN.

I’ll throw some more detail, still working from the “your computer” side.

Your computer is almost certainly configured with a couple of DNS server IP addresses, belonging either to your ISP, or to some publicly available DNS server. When you’re going to www.hotmail[.]com, your computer just asks a DNS server that it is configured to ask - it doesn’t go to a root server (although it could, every computer is configured with root server IPs).

But even before that, your computer first looks to its HOSTS file. That’s a local file that contains manually configured matches between DNS hostnames and IP addresses. Under normal circumstances, this HOSTS file would be empty, but it’s there. Side note: DNS (Domain Name System) is what replaced HOSTS files. Prior to DNS, a university network (for example) would distribute a hosts file for everyone to put on their computer, and that was it.

Okay, www.hotmail[.]com isn’t in my hosts file, what next? Not a DNS server yet - next your computer will look to its local cache. You visited www.hotmail[.]com a couple hours ago, you haven’t rebooted yet, computer looks in its local cache and uses whatever it finds there.

Not in the local cache? Now your computer asks the DNS server its configured to ask for everything. That DNS server has its own cache, so if anyone has asked it for www.hotmail[.]com recently, it already has it, and returns an answer to your query.

If that DNS server doesn’t have the entry cached, it may be configured with forwarders. This essentially means “If I, a DNS server, don’t have a listing in my own cache, I will always pass the query to my forwarder instead of going to a root server.” There may be multiple layers of this kind of behavior, maybe the next DNS server even knows who’s authoritative for hotmail[.]com, and says “go ask them.”

The last word, though, is always the root servers. Root DNS servers are authoritative for ‘.’ and they contain lists of TLDs and the DNS servers authoritative for those.

Another thing to be aware of is that if a computer doesn’t have an IP address for a particular hostname (and it is not configured with a DNS server to ask for everything), it only returns “go ask this other DNS server” to the computer making the query, and then that computer goes and makes the full query to that DNS server.

It is also important to make sure that the DNS server(s) your computer is configured to use are themselves trustworthy. “Dan’s Totally Not Sketchy I Promise Public DNS Server” could very easily be configured to believe it is authoritative for the hotmail[.]com domain, and hand you whatever IP address it is configured to hand out from its own “Totally Authoritative I Promise” zone file.

And I forgot about TTL (Time To Live). TTL is measured in milliseconds, and generally speaking, only gets as short as fifteen minutes. If a cached record is older than the TTL, then the DNS server (or your local cache) will discard it and go ask for a fresh one. This does not apply to hosts file entries, or to static entries in an authoritative DNS zone file; those never expire.

Yes, that’s true, but more generally speaking, an external attacker would need to first gain access. The governments who control their national TLDs already have that access. Could the UK do the same thing with the co.uk TLD? They could, but the UK government seems more trustworthy on that point than does the Russian government.

OP asked specifically about the “safety” of .ru sites. I answered that question in that context.

Something which has not been mentioned yet - Russia controls DNS resolution for any .ru site, and here’s how that works:

When you browse, say, www.yandex[.]ru, your computer needs to know the IP address of a server that hosts that site. Let’s say you are not using an ISP or public DNS server to get your name resolution from DNS hostname to IP address. (All of the following is essentially still what happens, just with a less complicated explanation.)

First, your computer contains a list of root DNS servers. Every DNS query starts with a root server, and those root servers are associated with the often-excluded ‘.’ at the end, like “www.yandex[.]ru**.**” - that trailing dot at the end always exists, we just don’t type it.

The root server says, “Here’s a DNS server which is authoritative for the .ru top-level domain, go ask them.”

Then your computer asks the .ru DNS server where to find www.yandex[.]ru, and the .ru DNS server says “Here’s the server that is authoritative for the “yandex” subdomain under .ru, go ask them where their “www” host is.”

Then your computer asks the yandex[.]ru DNS server where to find www.yandex[.]ru, then that DNS server says “Here’s the IP address that goes with that hostname,” and your computer asks the server at that IP for the website.

Again, Russia controls DNS resolution for anything at .ru. All they would need to do for any subdomain beneath .ru is provide their own authoritative DNS server for yandex[.]ru - or for any other whatever[.]ru DNS name. They could then redirect all browsing traffic to anything under .ru to anything they wanted.

Those FBI takedown pages? This is exactly how that is done. The FBI doesn’t reconfigure a server at the “correct” IP; they redirect DNS for the subdomain to their own IP and own web server in order to display the takedown page. That operation is performed within legal limits, but from a technical perspective, such an operation could just as easily happen outside of legal limits, especially when the party trusted to properly respond to DNS queries is Russia.

tl;dr: Russia can very easily redirect any traffic to any .ru site to anywhere they want.

e;

I’m guessing that alternative front ends (piped, FreeTube, whatever) don’t give YouTube the same metrics they would get if I was using YouTube directly? I will continue to deny them the data they so desire.

What if I’m an email administrator who came from Timex/Sinclair?

That’s dedication.

Oh, I totally agree, but for this situation where it appears to be for personal use, the Office Online applications would probably do just fine.

Word, Excel, and PowerPoint are free to use with the web interface.

https://www.makeuseof.com/windows-limit-reservable-bandwidth/

It’s not as scary as it sounds.