Best Products
Launches
Launch archive
Most-loved launches by the community
Launch Guide
Checklists and pro tips for launching
News
Newsletter
The best of Product Hunt, every day
Stories
Tech news, interviews, and tips from makers
Changelog
New Product Hunt features and releases
Forums
Forums
Ask questions, find support, and connect
Kitty Points Leaderboard
The highest scoring community members
Streaks
The most active community members
Events
Meet others online and in-person
Advertise
Subscribe
Sign in
Clear text
recent
p/netfox
by
Giovambattista Fazioli
•
1mo ago
The padlock that lied: what CoreWLAN's supportsSecurity really answers
... green closed padlock. One, by the look of its name, was a neighbour's smart vacuum showing its setup hotspot. Its radio didn't even do 802.11n, and it was supposedly speaking a protocol from 2018. system_
profiler
SPAirPortDataType agreed with my suspicion: Security: None . Netfox said Enhanced Open, Open . The code looked right This is the classifier as it shipped: private static let enhancedOpenModes: [CWSecurity] = [.OWE, .oweTransition] static func classifyAccess(for cwNetwork: CWNetwork) -> WiFiNetwork.Access { WiFiNetwork.Access.classify( open: cwNetwork.supportsSecurity ... ... Mixed. It's not a bug, it's a different question Once the table is in front of you, the pattern is clear. supportsSecurity(_:) doesn't answer "does this access point advertise this mode?" . It answers "could a
profile
2
3
Subscribe
Sign in