Beacown (Linux WiFi Exploit)
github.com
Beacown (Linux WiFi Exploit)
1–10 of 26 posts
Re: Beacown (Linux WiFi Exploit)
#2Current discussion: https://news.ycombinator.com/item?id=33200171.
Re: Beacown (Linux WiFi Exploit)
#3[x] Catchy name
[ ] Catchy logo
Poor effort, only 50% of the way there. (No marks awarded for a working exploit, marketing doesn't care about that)
Edit: Marks should also be deducted for a lack of scary text claiming that everyone should panic.
Re: Beacown (Linux WiFi Exploit)
#4[x] Catchy name [ ] Catchy logo Poor effort, only 50% of the way there. (No marks awarded for a working exploit, marketing doesn't care about that) Edit: Marks should also be deducted for a lack of scary text claiming that everyone should panic.
Some sort of evil bee/cow hybrid with psychic (wifi) waves would work well as a logo, to help generate buzz.
Re: Beacown (Linux WiFi Exploit)
#5[x] Catchy name [ ] Catchy logo Poor effort, only 50% of the way there. (No marks awarded for a working exploit, marketing doesn't care about that) Edit: Marks should also be deducted for a lack of scary text claiming that everyone should panic.
I think we need a vulnerability buzzword bingo.
Re: Beacown (Linux WiFi Exploit)
#6[x] Catchy name [ ] Catchy logo Poor effort, only 50% of the way there. (No marks awarded for a working exploit, marketing doesn't care about that) Edit: Marks should also be deducted for a lack of scary text claiming that everyone should panic.
Just to be clear, everyone really should panic. Right?
Re: Beacown (Linux WiFi Exploit)
#7No post body was provided.
Re: Beacown (Linux WiFi Exploit)
#8[x] Catchy name [ ] Catchy logo Poor effort, only 50% of the way there. (No marks awarded for a working exploit, marketing doesn't care about that) Edit: Marks should also be deducted for a lack of scary text claiming that everyone should panic.
Just to be clear, everyone really should panic. Right?
Plenty of Android devices have kernels that are too old to be vulnerable. Versions 5.1 and newer are vulnerable.
Re: Beacown (Linux WiFi Exploit)
#9Quoted post unavailable.
Even as a Rust user, I'd prefer to reduce the attack surface by having a userspace network stack. Tanenbaum gets the last laugh.
Of course, once it's in userspace you can write it in whatever language you want. But as a network-facing component, yes, it should preferably be written in a memory-safe language as much as possible, since it's extremely high-risk and the first target for remote adversaries.