The comma makes this title read very weird.
this post was submitted on 02 Oct 2024
45 points (90.9% liked)
Cybersecurity
5680 readers
77 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Notable mention to [email protected]
founded 1 year ago
MODERATORS
Didn't know Christopher Walken was into netsec.
Now imagine: I use arch, by the way 😅😂
I can't seem, to parse it for the life of me
I would have called this a comma splice, but apparently what I was taught that is - just a comma incorrectly inserted into a sentence - is not the entirety of what a comma splice is.
Who uses Bluetooth passcodes?
They are used for most pairing sequences, but we don't type them in anymore. They are used more to validate that it's you that are connecting two devices.
In other words, this vulnerability isn’t that big of a deal.
Maybe? There are a ton of shitty BT implementations in the wild that will never get patched. This does seem quirky at first glance, but could just as easily affect millions of vehicles, as an example.
If I was so inclined, I would camp out in a busy parking lot with an antenna just to see what I could find.
This vuln is not new, it was published 3.5 years ago: https://nvd.nist.gov/vuln/detail/CVE-2020-26558