KVR Audio

cron · Post by **cron** » Wed Jan 03, 2018 2:28 am

edit: please move to this thread for more active discussion and thoughts from devs: http://www.kvraudio.com/forum/viewtopic ... 6&t=497566

Lovely start to the year, eh?

https://www.theregister.co.uk/2018/01/0 ... sign_flaw/

kbaccki · Post by **kbaccki** » Wed Jan 03, 2018 3:23 am

And this interesting little tidbit in the comments section...

Intel's CEO Just Sold a Lot of Stock
https://www.fool.com/investing/2017/12/ ... stock.aspx

cron · Post by **cron** » Wed Jan 03, 2018 3:54 am

Oh man, what a stupid move.

This guy wants to hope Intel stocks hold their value, else I suspect he may have some uncomfortable questions to answer with regulators.

kbaccki · Post by **kbaccki** » Wed Jan 03, 2018 4:23 am

An unfortunately-timed coinkidink, I'm sure.

cron · Post by **cron** » Wed Jan 03, 2018 12:23 pm

Any developers who care to estimate how this might affect VST performance? The full description of the bug is still embargoed, but clues aplenty.

chk071 · Post by **chk071** » Wed Jan 03, 2018 12:30 pm

OMG, a HORROR bug!! Let's hope we all get spared of the undead vermin.

cron · Post by **cron** » Wed Jan 03, 2018 12:36 pm

Mate, name a worse bug. HORROR is putting it lightly.

chk071 · Post by **chk071** » Wed Jan 03, 2018 12:43 pm

I'll rather wait until someone competent comments on this. Frankly, for now, this rather seems like a hoax, especially as there haven't been any precise infos about the "bug" yet, and, especially, about which CPU's are really affected. Rather seems like a press canard.

You also gotta love that stuff like this isn't rather reported to the respective companies in the first place, but, always surfaces on some blogs, or is headed directly to the press. Says LOADS about the people "discovering" it.

BTW, what surprises me most is that they haven't engaged a advertising company to develop a fancy name for this bug already. But, they probably already did, and just wait a few days to present the name, just like with Heartbleed.

cron · Post by **cron** » Wed Jan 03, 2018 12:56 pm

The Register is fairly reliable for what its worth. While we don't know the precise nature of that bug beyond the clues in AMD's statement, we do know the precise nature of the fix. And the 'fix' is... man...

But yes, I'd also love to hear developer's thoughts on this.

chk071 · Post by **chk071** » Wed Jan 03, 2018 1:02 pm

What surprises me is that at a specific day, all of a sudden, several newspapers report about this. And that MS is supposedly working on a fix for this since November last year... anyway, as i have no idea about the nature of this thing either, i'll just remain silent for now. It just seems very weird that all of a sudden, the whole press is all over this thing.

Anyway, from a sheer feeling, i'll say that those patches won't affect performance at all. Out of experience how the press ticks, always predicting the worst, and scaring people wherever possible.

cron · Post by **cron** » Wed Jan 03, 2018 1:09 pm

Fair play. I've toned the thread title down for now.

Scotty · Post by **Scotty** » Wed Jan 03, 2018 1:12 pm

I am wondering given that the exploit is theoretical and hasn't yet been realized to the best of our knowledge, would non enterprise users be able to skip the update altogether and perhaps with a good anti malware software bundle - be protected against it? It sounds like the cure is worse than the disease and a risk management approach may be better than low level surgery.

t3toooo · Post by **t3toooo** » Wed Jan 03, 2018 1:17 pm

http://www.kvraudio.com/forum/viewtopic ... 6&t=497566

Freaqpeak · Post by **Freaqpeak** » Wed Jan 03, 2018 1:24 pm

chk071 wrote:I'll rather wait until someone competent comments on this. Frankly, for now, this rather seems like a hoax, especially as there haven't been any precise infos about the "bug" yet, and, especially, about which CPU's are really affected. Rather seems like a press canard.

You also gotta love that stuff like this isn't rather reported to the respective companies in the first place, but, always surfaces on some blogs, or is headed directly to the press. Says LOADS about the people "discovering" it.

BTW, what surprises me most is that they haven't engaged a advertising company to develop a fancy name for this bug already. But, they probably already did, and just wait a few days to present the name, just like with Heartbleed.

It's not a hoax.

You don't know what has been happening behind the scenes. I'm glad it's out in the open now. Think for how long Russia, China, Iran, North Korea and USA has had the potenial to use this for their own purposes (yes, these are the countries most active in aggressive attacks). These things ends up being used by state sanctioned attacks. Lucky for us, this time it wasn't the NSA or the Russians who discovered it. Then we would been left knowing nothing.

Classic example of don't shoot the messenger. You should be thankful that this hits the surface now.

Codename "f*ckwit/kaiser", hehe.. I agree though that domain registering and advertising is mostly just annoying and unnecessary. On the other hand, people working every day on security needs to get some credit for their work. Few people can work for free you now..

Microsoft, AWS and Google has already flagged full reboots next week of every single instance they have.

cron · Post by **cron** » Wed Jan 03, 2018 1:27 pm

Thanks for the link. Much more active discussion and thoughts from devs over there, so I'm closing this thread and encouraging all to move over there.

http://www.kvraudio.com/forum/viewtopic ... 6&t=497566

(edit: OK, I assumed I had the power to close my own threads. Maybe not

)

Possible 5 to 30% slowdown after urgent OS patches to address Intel vulnerability (all platforms)