3 ms·
Good writeup on the process, but the amount of negative spin in the article left a bad taste in my mouth. He says he didn't bother reporting the issue at first
by Aurornis 2y ago
Good writeup on the process, but the amount of negative spin in the article left a bad taste in my mouth.
He says he didn't bother reporting the issue at first (!) but then later criticizes Rabbit for not responding to his July 12th e-mail in less than 2 business days.
However, Rabbit had already fixed the issue and released a security advisory on July 11th, a day before he finally decided to contact them. You can see their security advisory on their website, dated July 11th ( https://www.rabbit.tech/security-advisory-071124 https://www.rabbit.tech/security-advisory-071124 ) To be fair, the post does bury this at the very end of the article, but it spends most of the opening sections talking about how much it "sucks" and leans heavily on the logging issue and their lack of response before eventually admitting that it was already fixed.
> As of 11 July, we’ve made the following changes:
> Pairing data can no longer be used to read from rabbithole. It can only trigger actions.
> Pairing data is no longer logged to the device.
> We have reduced the amount of log data that gets stored on the device.
> The Factory Reset option is now available via the settings menu. Customers should use this option to erase ALL data from their r1 prior to transferring ownership.
- wmf 2y agoThere's an acrimonious relationship between Rabbit and hackers and both sides seem to keep escalating.
- Retr0id 2y agoJust grouping together your other similar comments in this thread, so people can read the existing replies rather than duplicating conversations: - https://news.ycombinator.com/item?id=40988915 https://news.ycombinator.com/item?id=40988915 - https://news.ycombinator.com/item?id=40988541 https://news.ycombinator.com/item?id=40988541
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]