Why is Control Center on Monterey listening to port 5000 and port 7000? I have used these ports for years for local development, but now find them in use by Control Center. Is this worth filling a Feedback about?
Why is Control Center on Monterey listening on ports?
Thanks for sharing the comprehensive info. Instead of making any change I guess I just avoid using PORT range(5000,7000) for dev and debug.
I've also captured traffic that is malformed coming into my brand new Mac Apple Silicon. Port 7000 was open and bound to ControlCenter. The traffic I've captured (PCAP) respembles the airplay protocol RTSP. using a blist00 tag followed by a payload.
Interestingly, the attack traffic (dport 7000) has TCP options set. They are 12 bytes. 0101 and then 10 more bytes for an array of two timestamps. I'm pretty sure this is part of the attack payload.
Thank you.
Can we democratically vote to have whoever made the decision to occupy port 5000 fired? Or at least punched in the gut.
NB In Ventura they have moved the setting to "General | Airdrop and handoff". Because of course that is the first place I think of when looking for "Airplay receiver"...
Plus one above. This is seriously stupid Apple on so many levels - firstly using a known developer port is dumber than a rock. Secondly constantly changing the setting locations under cryptic naming conventions is idiotic as well. Do your Product managers really have such a skewed sense of intuitive organizational structure? Here is an idea -> try alpha sorting by service and functional category (General has no meaning at all lose it). See: https://en.wikipedia.org/wiki/Categorization Here is an example
Communication
Internet Accounts
Messages
Phone
etc.
Hardware
Displays
Energy Saver
Storage
Media Airplay Audio Players Video etc.
Network Bluetooth Firewall Thunderbolt USB VPN Wifi etc.
Operating System About Date & Time Desktop & Dock Screen Saver Wallpaper etc. Language & Region Login Items Sharing Sofware Update Start Up disk Time Machine
User Preferences Accessibility Appearance Control Center (have the ability to alpha sort anything and everything and frankly create and or rename categories) Focus Login Password Privacy and Security Screentime Siri & Spotlight etc.
I think you get the idea. This would be a meta organizational standard with a location design pattern, not some random organization stragegy that "seems" to make sense when in reality it does not, and also does not scale at all. the layout changes from OS iteration to OS iteration and makes solution finding nearly impossible as many search results are returned, one for each new change, that do not apply (as happened here). The fact that this is not more obvious a problem is unbelieveable and the same patteren repeats over and over with the Apple development model. C'mon folks do more research on optimal organizational construct logic, patterning, searchability, optimization, and scaling over time. And don't use known development ports for propietary service your users may or may not chose to use.