Intel processors are dead, so I have an AMD question

Page 5 of 6 [ 93 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6  Next

kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

18 Jan 2018, 10:39 pm

There have been warnings in the past about the pathetic state of the security of both Intel and AMD processors. This was in June, 2007:

Quote:
List: openbsd-misc
Subject: Intel Core 2
From: Theo de Raadt <deraadt () cvs ! openbsd ! org>
Date: 2007-06-27 17:08:16
Message-ID: 200706271708.l5RH8GkK024621 () cvs ! openbsd ! org
[Download message RAW]

Various developers are busy implimenting workarounds for serious bugs
in Intel's Core 2 cpu.

These processors are buggy as hell, and some of these bugs don't just
cause development/debugging problems, but will *ASSUREDLY* be
exploitable from userland code.


As is typical, BIOS vendors will be very late providing workarounds /
fixes for these processors bugs. Some bugs are unfixable and cannot
be worked around.
Intel only provides detailed fixes to BIOS vendors
and large operating system groups. Open Source operating systems are
largely left in the cold.

Full (current) errata from Intel:

http://download.intel.com/design/proces ... 327914.pdf

- We bet there are many more errata not yet announced -- every month
this file gets larger.
- Intel understates the impact of these erraata very significantly.
Almost all operating systems will run into these bugs.
- Basically the MMU simply does not operate as specified/implimented
in previous generations of x86 hardware. It is not just buggy, but
Intel has gone further and defined "new ways to handle page tables"
(see page 58).
- Some of these bugs are along the lines of "buffer overflow"; where
a write-protect or non-execute bit for a page table entry is ignored.
Others are floating point instruction non-coherencies, or memory
corruptions -- outside of the range of permitted writing for the
process -- running common instruction sequences.
- All of this is just unbelievable to many of us.

An easier summary document for some people to read:

http://www.geek.com/images/geeknews/200 ... __full.gif

Note that some errata like AI65, AI79, AI43, AI39, AI90, AI99 scare
the hell out of us. Some of these are things that cannot be fixed in
running code, and some are things that every operating system will do
until about mid-2008, because that is how the MMU has always been
managed on all generations of Intel/AMD/whoeverelse hardware. Now
Intel is telling people to manage the MMU's TLB flushes in a new and
different way. Yet even if we do so, some of the errata listed are
unaffected by doing so.

As I said before, hiding in this list are 20-30 bugs that cannot be
worked around by operating systems, and will be potentially
exploitable. I would bet a lot of money that at least 2-3 of them
are.

For instance, AI90 is exploitable on some operating systems (but not
OpenBSD running default binaries).

At this time, I cannot recommend purchase of any machines based on the
Intel Core 2 until these issues are dealt with (which I suspect will
take more than a year). Intel must be come more transparent.

(While here, I would like to say that AMD is becoming less helpful day
by day towards open source operating systems too, perhaps because
their serious errata lists are growing rapidly too
).



kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

18 Jan 2018, 11:35 pm

The recent discussions of CPU bugs reminds me of something from back in the late 1970s. Another grad student and I discovered a serious bug in the processor of an IBM mainframe.

On that processor there were rotate and shift instructions. The shift would shift the bits over a set number of places, effectively either multiplying by 2 or dividing by 2 and ignoring anything chopped off. The rotate was like a shift except that the bits that were shifted off were put back in at the left or right as the case may be.

There were versions of both instructions to do over two registers at once treating both together as a large piece of data.

I don't remember whether the bug involved shifts or rotates. For the sake of the discussion, I'll say it was a shift, but it may have been a rotate instead. If you did a double register shift using a specific set of registers, the number of bits actually shifted were greater than what was requested. I think it was like 8 bits more. For example, if you shifted the contents of the register by 2 bits, the result you actually got was the contents of the register shifted over by 10 bits. I seem to remember that you also had to have some other particular instruction either immediately before or immediately after the shift.

I wrote a program that showed the bug and took the listing over to the computer center at the college. As it turned out, trying to inform anyone was a waste of time because the stupid woman they had me talk to had no understanding of computers and refused to believe that there was such a thing as bugs. I was told in no uncertain terms that it was impossible for a computer to produce anything but correct answers.



XenoMind
Veteran
Veteran

User avatar

Joined: 12 May 2014
Gender: Male
Posts: 684
Location: Absurdistan

19 Jan 2018, 4:32 pm

kokopelli wrote:
Without zero chance that there could have been a china teapot in orbit, no burden of proof would have been required because a valid proof could not possibly exist.

Well, yes. However, the Russel's teapot principle is not about the comparison of the chances. It's about the burden of proof.



kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

19 Jan 2018, 5:09 pm

XenoMind wrote:
kokopelli wrote:
Without zero chance that there could have been a china teapot in orbit, no burden of proof would have been required because a valid proof could not possibly exist.

Well, yes. However, the Russel's teapot principle is not about the comparison of the chances. It's about the burden of proof.


It sounds like you had a freshman logic course and flunked it.



XenoMind
Veteran
Veteran

User avatar

Joined: 12 May 2014
Gender: Male
Posts: 684
Location: Absurdistan

19 Jan 2018, 5:45 pm

kokopelli wrote:
It sounds like you had a freshman logic course and flunked it.

You're too predictable. Try harder.



kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

19 Jan 2018, 6:12 pm

XenoMind wrote:
kokopelli wrote:
It sounds like you had a freshman logic course and flunked it.

You're too predictable. Try harder.


You need to learn some logic.

The stupidest thing about your argument is that Russell's Teapot analogy has absolutely no applicability to the question of whether AMD's processors might be vulnerable to Meltdown. That's even worse than the realization that AMD is unable to make the claims that you are making. The most they can say at this time is that they believe that their CPUs are not vulnerable to Meltdown.



XenoMind
Veteran
Veteran

User avatar

Joined: 12 May 2014
Gender: Male
Posts: 684
Location: Absurdistan

23 Jan 2018, 9:18 pm

kokopelli wrote:
The stupidest thing about your argument is that Russell's Teapot analogy has absolutely no applicability to the question of whether AMD's processors might be vulnerable to Meltdown.

Well, it seems that you're just beyond redemption. Good luck.



kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

24 Jan 2018, 7:12 am

XenoMind wrote:
kokopelli wrote:
The stupidest thing about your argument is that Russell's Teapot analogy has absolutely no applicability to the question of whether AMD's processors might be vulnerable to Meltdown.

Well, it seems that you're just beyond redemption. Good luck.


It's one thing to say "Russell's Teapot" as if they are some kind of magic words. It's another thing to show that the argument actually applies in any given situation.

Why don't you try to argue the point instead of just making assertions? Prove to us that "Russell's Teapot" applies. Prove to us that AMD CPUs are not vulnerable to Meltdown (something that AMD cannot do at present).



XenoMind
Veteran
Veteran

User avatar

Joined: 12 May 2014
Gender: Male
Posts: 684
Location: Absurdistan

24 Jan 2018, 11:09 am

kokopelli wrote:
It's one thing to say "Russell's Teapot" as if they are some kind of magic words. It's another thing to show that the argument actually applies in any given situation.

It applies to every single situation where you say that something exists or may exist without any proofs. And, as I said, good luck. Go read some good rational thinking book.



kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

24 Jan 2018, 2:57 pm

XenoMind wrote:
kokopelli wrote:
It's one thing to say "Russell's Teapot" as if they are some kind of magic words. It's another thing to show that the argument actually applies in any given situation.

It applies to every single situation where you say that something exists or may exist without any proofs. And, as I said, good luck. Go read some good rational thinking book.


No, it doesn't.

The analogy applies only to a situation in which someone says that we should assume a statement to be true simply because it cannot be proven false.

If it was as you claim, he would not have chosen as his example a china teapot in orbit well before we had any space shots. The only ways that such a teapot could be there is if it spontaneously formed there or if someone with space flight, not humans at the time, had dropped it off out there.

Furthermore, it would be an issue for you, not me. You are the one claiming, without any proof at all, that the vulnerability does not affect AMD CPUs. All AMD will say on the matter for now is that they believe it doesn't -- they cannot rule it out for sure.

I'm making no claim that Russell's Teapot analogy would apply to even if it meant what you think it means. I'm not making any claim that the Meltdown vulnerability affects AMD CPUs or that it doesn't -- only that we do not know for sure. That is, there is no proof, at this time, that it doesn't affect AMD CPUs. Neither do we have any proof that it does or does not affect them.

It doesn't surprise me that since you do not understand Russell's Teapot analogy, you can't apply it correctly.

For what it's worth, I recognize that you can't possibly prove that Meltdown does not affect AMD CPUs. It is not enough to have tried an attack written for another CPU and found that it didn't work on AMD CPUs, you have to show that no such attack of that type will work on AMD CPUs. The only way you can do that, other than trying all possible attacks, is by a very thorough analysis of the internal logic of each CPU AMD makes to show that there is no possible set of conditions that could expose memory to a process that it is not entitled to get. Even if you were AMD's lead expert on their CPUs, that would be an extremely formidable task. For you, it would be pretty much impossible.



XenoMind
Veteran
Veteran

User avatar

Joined: 12 May 2014
Gender: Male
Posts: 684
Location: Absurdistan

24 Jan 2018, 4:36 pm

kokopelli wrote:
No, it doesn't.

Go read the freaking book. Stop wasting my time.



kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

24 Jan 2018, 4:50 pm

XenoMind wrote:
kokopelli wrote:
No, it doesn't.

Go read the freaking book. Stop wasting my time.


You don't have the foggiest idea of what you are talking about. Your understanding of logic is clearly very poor. You don't understand the analogy and so you use it wrongly.

AMD doesn't claim that their CPUs are not vulnerable to Meltdown, but you do. Why is that, do you suppose? Do you know something AMD doesn't? Or do you just not have the logical capacity to understand what they are saying.

They say that they don't believe that their CPUs are vulnerable -- they clearly cannot prove that or they would have stated it in stronger terms like those they use for their GPUs which they unequivocally say are not effected by Meltdown. They would love to be able to claim that they aren't affected, but cannot.

If you can learn anything from this, your time is not being wasted. if you cannot learn from it, then you should go back to playing video games.



jikijiki53
Raven
Raven

User avatar

Joined: 22 Jul 2014
Age: 26
Gender: Male
Posts: 105
Location: Near Pittsburgh PA

25 Jan 2018, 12:04 pm

kokopelli wrote:
XenoMind wrote:
kokopelli wrote:
No, it doesn't.

Go read the freaking book. Stop wasting my time.


You don't have the foggiest idea of what you are talking about. Your understanding of logic is clearly very poor. You don't understand the analogy and so you use it wrongly.

AMD doesn't claim that their CPUs are not vulnerable to Meltdown, but you do. Why is that, do you suppose? Do you know something AMD doesn't? Or do you just not have the logical capacity to understand what they are saying.

They say that they don't believe that their CPUs are vulnerable -- they clearly cannot prove that or they would have stated it in stronger terms like those they use for their GPUs which they unequivocally say are not effected by Meltdown. They would love to be able to claim that they aren't affected, but cannot.

If you can learn anything from this, your time is not being wasted. if you cannot learn from it, then you should go back to playing video games.


How about you kokopelli and Xenomind go to this link and download Inspectre and see for yourself. It's free.

https://www.grc.com/inspectre.htm

The results from this tell me that on my 4th Gen Intel processor, it's protected from Meltdown but not Spectre and all I'm waiting for is the firmware update on the motherboard and the CPU for Spectre.



kokopelli
Veteran
Veteran

User avatar

Joined: 27 Nov 2017
Gender: Male
Posts: 3,657
Location: amid the sunlight and the dust and the wind

25 Jan 2018, 1:13 pm

jikijiki53 wrote:
kokopelli wrote:
XenoMind wrote:
kokopelli wrote:
No, it doesn't.

Go read the freaking book. Stop wasting my time.


You don't have the foggiest idea of what you are talking about. Your understanding of logic is clearly very poor. You don't understand the analogy and so you use it wrongly.

AMD doesn't claim that their CPUs are not vulnerable to Meltdown, but you do. Why is that, do you suppose? Do you know something AMD doesn't? Or do you just not have the logical capacity to understand what they are saying.

They say that they don't believe that their CPUs are vulnerable -- they clearly cannot prove that or they would have stated it in stronger terms like those they use for their GPUs which they unequivocally say are not effected by Meltdown. They would love to be able to claim that they aren't affected, but cannot.

If you can learn anything from this, your time is not being wasted. if you cannot learn from it, then you should go back to playing video games.


How about you kokopelli and Xenomind go to this link and download Inspectre and see for yourself. It's free.

https://www.grc.com/inspectre.htm

The results from this tell me that on my 4th Gen Intel processor, it's protected from Meltdown but not Spectre and all I'm waiting for is the firmware update on the motherboard and the CPU for Spectre.


For some of us the link is rather useless -- you have to use Microsoft Windows for the link to work.

Also, while AMD processors are believed to not be vulnerable to Meltdown, it cannot be ruled out completely at this point in time. We cannot say that all variants of Meltdown have been discovered.



jikijiki53
Raven
Raven

User avatar

Joined: 22 Jul 2014
Age: 26
Gender: Male
Posts: 105
Location: Near Pittsburgh PA

25 Jan 2018, 4:15 pm

kokopelli wrote:
jikijiki53 wrote:
kokopelli wrote:
XenoMind wrote:
kokopelli wrote:
No, it doesn't.

Go read the freaking book. Stop wasting my time.


You don't have the foggiest idea of what you are talking about. Your understanding of logic is clearly very poor. You don't understand the analogy and so you use it wrongly.

AMD doesn't claim that their CPUs are not vulnerable to Meltdown, but you do. Why is that, do you suppose? Do you know something AMD doesn't? Or do you just not have the logical capacity to understand what they are saying.

They say that they don't believe that their CPUs are vulnerable -- they clearly cannot prove that or they would have stated it in stronger terms like those they use for their GPUs which they unequivocally say are not effected by Meltdown. They would love to be able to claim that they aren't affected, but cannot.

If you can learn anything from this, your time is not being wasted. if you cannot learn from it, then you should go back to playing video games.


How about you kokopelli and Xenomind go to this link and download Inspectre and see for yourself. It's free.

https://www.grc.com/inspectre.htm

The results from this tell me that on my 4th Gen Intel processor, it's protected from Meltdown but not Spectre and all I'm waiting for is the firmware update on the motherboard and the CPU for Spectre.


For some of us the link is rather useless -- you have to use Microsoft Windows for the link to work.

Also, while AMD processors are believed to not be vulnerable to Meltdown, it cannot be ruled out completely at this point in time. We cannot say that all variants of Meltdown have been discovered.


I actually am using Windows. If it doesn't work, search up "InSpectre" (without quotes). That's why it should be tested if it is the case or not, however, there are different kinds of AMD processors (Like Intel) so it really depends on the processor's design and firmware.



Aristophanes
Veteran
Veteran

User avatar

Joined: 10 Apr 2014
Age: 43
Gender: Male
Posts: 3,603
Location: USA

26 Jan 2018, 9:02 am

There are so many better things to argue about than which microprocessor company has more STD's in it's product.