Intel, AMD, Google Respond To US Government Meltdown/Spectre Inquiry

[Guest]

In a response to a U.S. government inquiry on the Meltdown/Spectre incident, Intel and other companies agreed that embargoing the disclosure of the vulnerabilities was the correct choice.

Intel, AMD, Google Respond To US Government Meltdown/Spectre Inquiry : Read more

 

[Snipergod87]

Why would they need to disclose it to them, it is not like there were fixes in place yet, maybe the NSA wanted to exploit them?

 

[Brian_R170]

Exactly SniperGod87

 

[Kennyy Evony]

because usa wants to control the world. its very greedy and they think everything no matter what it is or weather it is located even in another galaxy, usa has the right to put its name on it.

 

[derekullo]

because usa wants to control the world. its very greedy and they think everything no matter what it is or weather it is located even in another galaxy, usa has the right to put its name on it.

It's not like they traveled to another celestial object and placed a US flag on its surface .... O wait nvm

To be fair, the people who actually name stars, International Astronomical Union, are based in France.

Although a name like J05552+0724AP, hardly sounds French or American.

https://www.google.com/search?q=J05552%2B0724AP

And yes I do see the irony in the first letter being J and the last 2 being AP ...

 

[anthonywadie]

My thoughts exactly !

 

[USAFRet]

Intel did not say why it chose not to disclose the vulnerabilities to the U.S. government, but it did admit to disclosing the issues to some partners, however. In late January, rumors circulated that Intel had discussed the vulnerabilities during the embargo with Chinese firms that are closely connected to the Chinese government, but Intel did not name any specific firms in its letter.

This is the problem.
They disclosed to some 'partners', and the Chinese govt. But not the US or any other govt.

If you're going to tell 'some'...other entities WILL be pissed off.

 

[hannibal]

It was a good choise!
The attackers did get their exploitation tools ready very quickly after some madman did leak the information out.
If there would not have been leak, there would have been more time to make the patch right in the first place!
After this incident I would avoid giving any information to any Linux developers because they seems to leak everything out without caring the consequences... And that is pity! Because most Linux programmer are pro stuff and very reliable, but there are not so wise among them...

 

[redgarl]

AMD at that time was thinking they were almost immune. Why would the issue a statement if they were thinking their architecture was having almost zero risk?

Ohhh, that's right, because on TH AMD is evil... I get it now.

 

[rroot]

Enough time has been wasted on this alleged Google discovered CPU "bug" crap. These are not necessarily bugs. They are business and home users decisions that can be explained and both CPU and Operating System design should be allowed to go separate ways with most likely more expensive CPU and Operating Systems for users that depend on things like unprivileged users for security and not slowing down progress for environments that do not depend on unprivileged users in implementing security.

Again, it is not necessarily a bug for a kernel process to share memory space with a user process. Both CPU's and Operating System can change and will be slower that accommodate the need to not have that happen but that is not something that those organizations and home users that do not need to depend on unprivileged user type security as anything but a convenience should have forced upon us slowing down our computers and costing us more money.

 

[rroot]

Enough time has been wasted on this alleged Google discovered CPU "bug" crap. These are not necessarily bugs. They are business and home users decisions that can be explained and both CPU and Operating System design should be allowed to go separate ways with most likely more expensive CPU and Operating Systems for users that depend on things like unprivileged users for security and not slowing down progress for environments that do not depend on unprivileged users in implementing security.

Again, it is not necessarily a bug for a kernel process to share memory space with a user process. Both CPU's and Operating System can change and will be slower that accommodate the need to not have that happen but that is not something that those organizations and home users that do not need to depend on unprivileged user type security as anything but a convenience should have forced upon them.

Google has had enough publicity over this. They are simply wrong. These were not and are not necessarily bugs. AMD and Intel and most other CPU manufacture unless they clearly told people to depend on unprivileged methods for security in operating systems and hypervisors, etc., are simply not at fault.