cultural reviewer and dabbler in stylistic premonitions

  • 563 Posts
  • 948 Comments
Joined 3 years ago
cake
Cake day: January 17th, 2022

help-circle









  • Having some distrust in Wikipedia is healthy; you certainly shouldn’t take it as the final word about facts you’re depending on the accuracy of. But, it is very often a good starting point for learning about a new subject.

    Spending a minute or two reading that “source code” article (or another version of it which is likely available in your first language) would give you a much better understanding of the concept of source code (which is a prerequisite for understanding what “closed source” means) than any of the answers in this thread so far.







  • This is an excerpt of OP’s post in question:

    Last android piece of garbage I buy. Is there even a single good reason it restricts .local, as is commonly used for local domains in LAN DNS to some hellish nonsense no one’s ever used called multicast DNS?

    Is .local actually “commonly used for local domains in LAN DNS” or did you just see .local somewhere else (probably using mDNS) and decide to cargo cult it? I’ve never seen someone use it outside the context of zero-configuration networking.

    fyi, besides Android, most Linux distros also ship with mDNS enabled by default, as do all Apple operating systems since the feature was first introduced in an update to Mac OS 9 in 2001. It’s mostly just Windows that doesn’t.

    And before someone says “uhmm but m-muh RFC says so” - no. That RFC only suggests that some people MAY implement it as such, which yeah, sucks, because the RFC if it did it’s job right should forbid it altogether […]

    Which RFC says that? I just checked, and RFC6762 (Multicast DNS) says:

    This document specifies that the DNS top-level domain “.local.” is a special domain with special semantics, namely that any fully qualified name ending in “.local.” is link-local, and names within this domain are meaningful only on the link where they originate. This is analogous to IPv4 addresses in the 169.254/16 prefix or IPv6 addresses in the FE80::/10 prefix, which are link-local and meaningful only on the link where they originate.

    Any DNS query for a name ending with “.local.” MUST be sent to the mDNS IPv4 link-local multicast address 224.0.0.251 (or its IPv6 equivalent FF02::FB).

    Also, as per (the immediately prior) RFC6761 (“Special-Use Domain Names”), RFC6762 explicitly adds .local to the IANA registry of special-use domain names.

    HTH!










  • there is no provider on the planet that can freeze state of RAM in a way that would be useful for this

    You are very mistaken, this is a well-supported feature in most modern virtualization environments.

    Here are XenServer docs for it. And here is VMWare’s “high-frequency” snapshots page.

    Sometimes, law enforcement authorities only need to contact cloud provider A when they have a warrant for (or, perhaps, no warrant but a mere request for) data about some user C who is indirectly using A via some cloud-hosted online service B.

    A(mazon) will dutifully deliver to the authorities snapshots of all of B’s VMs, and then it is up to them if they limit themselves to looking for data about C… while the staff of company B can honestly say they have not received any requests from law enforcement. (sorry my best source on this at the moment is sadly trust me bro; I’ve heard from an AWS employee that the above scenario really actually does happen.)