• 0 Posts
  • 52 Comments
Joined 1 year ago
cake
Cake day: July 11th, 2023

help-circle




  • Yeah, I mistyped part of the sentence. Should have been “without some serious effort or illegal methods.” Serious effort is well beyond most ISP’s. They aren’t sniffing wireless AP’s then busting down doors to find out if its a 5g AP or an AP using their network. I actually know quite a bit about WiFi signals. I happen to be certified in Meraki (CMSS). If the uni said “no wireless signals” that would be a completely different story.



  • Sure, people might not care, but that doesn’t change the facts. Experts aren’t denying the legitimacy of the Panama or Paradise Papers, but they are saying that the idea of megacorporations secretly listening to your microphone and selling you products based on that is false. If they were doing that, it would be pretty easy to find out. Smartphones aren’t some mysterious black box; security engineers and hackers are constantly checking for these kinds of exploits. If corporations were actually spying on us through our phones, it would be the biggest topic at DEFCON. Believing that this could be kept secret would require assuming that all these experts are either paid off or in cahoots with the corporations, which veers into full-blown conspiracy theory territory.










    1. Generally to be “in-demand”, you need about 6 years of experience & highly desirable certifications (at least one security cert such as sec+ or CASP, dns-related cert such as Infoblox CDCA, and typically something else like cloud engineering or maybe automation engineering related). Getting into DNS is usually something that happens after you’ve already been an enterprise network engineer for a number of years. It’s highly specialized and rather difficult.

    2. Not possible. While AI can theoretically do the job, error is too expensive. AI already does much of my work, but I have to make risk assessment & I run the automation systems. I already automate much of my daily work. But when big stuff breaks, automation won’t fix it.



  • DNS engineer here.

    It’s always DNS because no one wants to hire us. We’re prima donnas that don’t work much and demand large salaries. Companies think they can get away with having some random network guy “learn a bit of DNS” and it works!!.. For a while… Then it fails catestrophically and the DNS engineer that was let go to “save costs” smugly watches them crash and burn. The job is super easy and simple until you’re 48 hours into troubleshooting and the CTO is lighting money on fire trying to get the network back online. A big company can easily burn a DNS engineers 10 years salary in costs if they have a single large DNS failure (security or downtime).