跳到主要内容

r/sysadmin


So do you think Apple new Watches Be Added to the Banned-Device List After Yesterday’s Announcement?
So do you think Apple new Watches Be Added to the Banned-Device List After Yesterday’s Announcement?
General Discussion

After yesterday’s creepy live rewind/siri recap announcement, I’m honestly surprised this hasn’t sparked more discussions and backslash

As I understand it, Apple is adding ambient conversation features to the Apple Watch that can listen to, process, and summarize what’s being said. Apple says the processing happens locally and is privacy-preserving, but I’m not sure that fully answers the security question:

What happens when the person sitting across from you is wearing one?

We already discourge employees to bring phones or recordung devices into very sensitive meetings. Are organizations now supposed to treat Apple Watches the same way? What a mess.

Maybe I’m overthinking it, and I’m still trying to work through the implications, but this seems like a pretty big unnessisary expansion of what an ordinary-looking wearable can do. I also think some of these features are a little silly anyway—as if the poor battery life weren’t enough—especially when Apple keeps adding capabilities without much obvious practical value. To me, this sounds way more significant than almost anything else announced this week, including the LG TVs story. That’s why I’m surprised it hasn’t gotten more attention and backlash.

I’d be interested to hear how others are thinking about this.


广告:Shadow IT is quietly exposing companies every day
Shadow IT is quietly exposing companies every day

We went hunting for Shadow IT using only public sources (mostly cert transparency logs) and basic enumeration. The results were... not great.

In just a few days, we found:

  • Exposed backups with source code, database dumps, and live FTP credentials

  • Unsecured Git repos leaking proprietary code and secrets for Redis, MySQL, OpenAI and more

  • Unprotected admin panels left online without authentication, some already hit by ransom notes

  • Propagated misconfigurations where one hosting provider spread the same flaw across ~100 sites

The scariest part? Attackers use these exact same simple methods every single day. If you aren't looking for these assets, they are. You can read the full research here. 

The good news is we’ve built Intruder to handle the annoying part for you: automatically discovering your external attack surface (new servers, APIs, subdomains) and scanning assets for weaknesses as soon as they appear. You won’t get blindsided by something you didn’t even know was live.

Start your free trial or book a demo to take control of your attack surface today.


So the engineers bought a tool.
So the engineers bought a tool.
Rant

The tool? A 3-d printer. I walked past and saw them assembling it and asked what it was - and they told me.

I asked if they wanted it on the network. Blank stares. Of COURSE they want it on the network.

Do I have a ticket? No? Why not? I got a ticket.

Figure out what port on the switch, change it to the Printer VLAN, get ready to plug it in - no network port.

Why isn't there a network port? We didn't think we needed one.

How does it get configured? With a USB drive (that we don't allow). How else? Wifi. We use our phone (NOT on the corporate wifi) to configure. So how does that get on the only wifi that can see the engineer workstations? Blank looks.

30 minutes. It would have taken 30 minutes to sit down with me to cover all the things we need to make this work smoothly.

I'll make it work. I'll pull out one of the corporate handhelds we haven't rolled out to the shop yet and use it. They're going to wait a day or so for me to dig out the mess. And I'm in no hurry to reward this.

30 minutes. And I've never turned down an equipment request. I get approval from their manager and the CFO if it's over the limit. That's it.

Thanks for listening.

ETA - Thanks for all the replies. The commiseration, the advice, and even the folks telling me to shut up and do the job.

The purpose of the rant is threefold:

  1. Get it off my chest. Anyone that keeps it all inside is in trouble. I needed to clear my head.

  2. Get advice from folks in the same boat.

  3. Get some uptight folks to tell me to shut up and do the job.

Thanks to ALL of you. It helps.


RDS issues after KB5122882 update on Server 2022
RDS issues after KB5122882 update on Server 2022

Spent most of the morning chasing a weird RDS issue. KB5122882 installed around 3:20am and a few hours later nobody could RDP into the server. Rebooted it and everything worked again, but about an hour later the exact same thing happened.

Existing sessions kept working, but new RDP connections would authenticate and then hang. Task Manager would freeze, but CPU, RAM and disk all looked totally normal. TermService was still running too.

Finally uninstalled KB5122882 and rolled back from 20348.5622 to 20348.5499. Everything has been working normally since.

Anyone else seeing this after the latest update? Pausing updates for now.