It looked like QEMU guest-to-host DoS, so I prepared the fixing patch and decided to send it to QEMU security team. Yes, I'm doing responsible disclosure, folks :-) Then the crawling fun began. [6/n]
-
-
[Jan 22] me: pinging in the ML again about this fix and unit-test! [Jan 22] Mr1: I asked Mr2. He promised to take a look very soon! [Jan 23] Mr2: merged. https://github.com/jnsnow/qemu/commits/ide … WOW! Really?!! [17/n]
Prikaži ovu nit -
And now can you guess who created this bug back in 2015? Yes, it was Mr2. LOL! Maybe that is why he was delaying the fix that killed it. That was weird story. Hope you liked it. Happy end! ========================= [n/n]pic.twitter.com/cqqSUDX9aX
Prikaži ovu nit -
And let me thank Mr1 once again! He is cool! I would not be able to become a QEMU contributor without his help :-) [n+1/n]
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.