(no title)
speedyapoc | 2 years ago
These are for reproducible bugs in iOS, for which I've provided an isolated sample project with a 100% reproduction rate. It takes time to create a thoughtful and detailed bug report and the lack of replies are beyond frustrating. I'm glad to see this post and couldn't agree more.
crimsontech|2 years ago
Testing, reproducing, writing it up all takes time and effort. I didn’t want anything from them other than for it to be fixed, I have kids with iPhones.
It’s no different than other companies though, I sent a remote code execution to Cisco and they just replied that they already knew about it but the product was approaching end of life so they wouldn’t fix it.
I’ve stumbled across so many vulnerabilities over the years and I tend to just ignore them unless I’m being paid to find them. It’s not worth the frustration.
juliob|2 years ago
Huh? That sounds very different from Apple. In that instance, the communication is professional, mature, and respectful of your time and effort.
saagarjha|2 years ago
joenot443|2 years ago
TheTon|2 years ago
I also notice that response and fix rates have large variance across components / teams within Apple. Some of them are quite responsive and others are just /dev/null. I do tend to focus my energy on those components where I’ve had success in the past.
black_puppydog|2 years ago
xign|2 years ago
It's really disheartening when you try to file proper bug reports, with proper reproduction steps, my own investigative work and more details of it, etc. Then… silent. As if the app just outputs the bug to /dev/null or something.
jbverschoor|2 years ago