Actually, all P problems (which are "easy to solve") are also NP ("easy to verify"). But NPC then (NP and "no easier" than any other NP problem)... unless P=NP:)
I don't know how it generally is in other countries (than Denmark, where I am from), and I don't mean to sound arrogant or anything, but the CS education here aims to teach people to be able to use whatever language someone throws at them with a minimal effort.
The taught ML and Java when I got my degree, but these only served to exemplify functional and object oriented languages respectively. I code in C# in the job I have now, and knowing C, C++, a little Java and others, it was a no-brainer to adapt.
It seems there is a lot of confusion about what this actually does. We're talking about RAM, albeit an area not normally accessible outside the BIOS, so it's not more resilient than anything else hiding in RAM. The BIOS writes code into the SMRAM at reboot, so even if the RAM isn't cleared, it's overwritten.
This is unrelated to flashing the BIOS, unless there is some special protection that allows this only to happen in SMM, and normal exploits that manage to flash the BIOS would leave you pretty screwed, SMRAM-exploit or not.
Also, it needs to trigger a SMI to execute the code, so it would need to insert a vector somewhere at a lower level if the exploit code were ever to get executed. I don't see the big deal.
What does surprise me though is that Intel has made such an obvious mistake in their design. It compares to allowing a user mode app to poison the cache on some kernel memory address. The difference is, of course, that user mode is under MMU and access protection, while ring 0 (from where this attack would normally be launched) is not.
At any rate, at least root access (on Linux; more on Windows) is needed, at which point, as several people have pointed out, you're screwed to begin with. Only the ability to hide a bit better in memory (but not on disk) seems to be an advantage.
Of course you do realize that there has been quite a lot of improvements in the front-end, resulting in a drastically improved memory bandwidth?
I believe this is part of the justification for bringing back SMT to their CPUs.
Also, QuickPath doesn't really directly compare to anything in Core, since they have an off-die common memory controller.
Are they? Rather the ads are just compressed to a ridiculous extent to get the loudest possible output at the same volume. Compression hurts quality, but of course keeping the signal far too low also does, when using PCM.
It's a balance, but am I pretty sure the main issue is the compression of the ad sound.
Yes, in fact "The children of Húrin" was published in Unfinished Tales, under its Sindarin name Narn i Hîn Húrin (later corrected by CT to the more correct Narn i Chîn Húrin), and parts of it also contribute to The Silmarillion.
So I think it's just an independent edition in its own covers, as said, perhabs re-edited for the occasion:-). But this is all good, I think. I can highly recomend the "first age material" of Tolkien's, especially The Silmarillion.
The same goes for standard UNIX time stamps (following the POSIX standard), which of course has the advantage that each day has the same length and the disadvantages you described above for NTP.
Even consulting a table can't make previous timestamps 100% correct since the POSIX and NTP way is to repeat the same number two seconds in a row when a positive leap second occurs. This can make past timestamps ambiguous. Should a negative one occur, they will skip a second instead.
Well, but Linux is obviously not a common-person operating system.
You need an 'expert' to set-up and maintain such a system, and for many people that isn't worth the time or effort. And let's face it, although there are exceptions, the look and feel of Linux just can't stand up to OS X; At all.
I agree, and most consumers do, I am sure (as do most geeks, since we "know" that ogg-vorbis for instance, is as good or better than the other formats).. unfortunately this is the flip side of the free market:-(.
Yeah, I have that problem. I can connect from Tiger to Windows (although only sometimes from the Finder; otherwise I have to use smbclient), and from/to my Linux server. I can connect from/to the Linux server from Windows as well, but not from Windows to the Mac. It just keeps on failing no matter what.
Under Panther (at least), Finder doesn't like samba options such as force user or similar, which I use to reach my root mount-point on my local server. Finder will not be able to write files into places it thinks it can't - apparently without checking if it really is the case. Conversely, Finder will attempt to write into places it thinks it can, but it can't, only to fail with a somewhat weird error message. I don't know if this has been fixed under Tiger.
Actually, it seems from what I have seen that Core Image is not
"there" if your graphics card is too old e.g. G-Force 440MX, so those
things aren't done in the CPU; They aren't done at all (for instance
certain animations when dragging widgets to the dashboard). There
is also Quartz 2D extreme which is probably more what you are
refering to (also not available on older gfx cards btw).
CSS2 has some internal contradictions which essentially makes it impossible to create a conforming implementation. However, applying common sense will resolve these, and indeed CSS2.1 resolves them to, what I think, most people would expect.
Curiously, the CSS2.1 abstract does not address this issue, even though it is, IMO, the most important ones (i.e. having internal contradictions is one of the worst thing a standard can have).
Now, why w3 is so slow pushing 2.1 to a standard (it's in a proposed state), is a mystery to me.
Slashdot Mirror
Actually, all P problems (which are "easy to solve") are also NP ("easy to verify"). But NPC then (NP and "no easier" than any other NP problem)... unless P=NP :)
I don't know how it generally is in other countries (than Denmark, where I am from), and I don't mean to sound arrogant or anything, but the CS education here aims to teach people to be able to use whatever language someone throws at them with a minimal effort.
The taught ML and Java when I got my degree, but these only served to exemplify functional and object oriented languages respectively. I code in C# in the job I have now, and knowing C, C++, a little Java and others, it was a no-brainer to adapt.
It seems there is a lot of confusion about what this actually does. We're talking about RAM, albeit an area not normally accessible outside the BIOS, so it's not more resilient than anything else hiding in RAM. The BIOS writes code into the SMRAM at reboot, so even if the RAM isn't cleared, it's overwritten.
This is unrelated to flashing the BIOS, unless there is some special protection that allows this only to happen in SMM, and normal exploits that manage to flash the BIOS would leave you pretty screwed, SMRAM-exploit or not.
Also, it needs to trigger a SMI to execute the code, so it would need to insert a vector somewhere at a lower level if the exploit code were ever to get executed. I don't see the big deal.
What does surprise me though is that Intel has made such an obvious mistake in their design. It compares to allowing a user mode app to poison the cache on some kernel memory address. The difference is, of course, that user mode is under MMU and access protection, while ring 0 (from where this attack would normally be launched) is not.
At any rate, at least root access (on Linux; more on Windows) is needed, at which point, as several people have pointed out, you're screwed to begin with. Only the ability to hide a bit better in memory (but not on disk) seems to be an advantage.
only the super high desk tops have Quick Path and Triple channel DDR3 and the bigger joke is the that there will be 2 differnt 1 cpu desktop Socket.
also the mobile will not have Quick Path.
...but then, they won't have as much to use QuickPath for either.
Of course you do realize that there has been quite a lot of improvements in the front-end, resulting in a drastically improved memory bandwidth? I believe this is part of the justification for bringing back SMT to their CPUs. Also, QuickPath doesn't really directly compare to anything in Core, since they have an off-die common memory controller.
"In this respect", the OP clearly meant. Time and trial have hardly proven otherwise with that in mind.
Right. The attacks that are mitigated in the current OpenSSL are some earlier, simpler ones; not the main one described in the paper.
I guess that's why they still call him admiral in 'Torn' which is two episodes after Pegasus went down? :-p.
Are they? Rather the ads are just compressed to a ridiculous extent to get the loudest possible output at the same volume. Compression hurts quality, but of course keeping the signal far too low also does, when using PCM. It's a balance, but am I pretty sure the main issue is the compression of the ad sound.
Yes, in fact "The children of Húrin" was published in Unfinished Tales, under its Sindarin name Narn i Hîn Húrin (later corrected by CT to the more correct Narn i Chîn Húrin), and parts of it also contribute to The Silmarillion.
:-). But this is all good, I think. I can highly recomend the "first age material" of Tolkien's, especially The Silmarillion.
So I think it's just an independent edition in its own covers, as said, perhabs re-edited for the occasion
The same goes for standard UNIX time stamps (following the POSIX standard), which of course has the advantage that each day has the same length and the disadvantages you described above for NTP. Even consulting a table can't make previous timestamps 100% correct since the POSIX and NTP way is to repeat the same number two seconds in a row when a positive leap second occurs. This can make past timestamps ambiguous. Should a negative one occur, they will skip a second instead.
Well, but Linux is obviously not a common-person operating system. You need an 'expert' to set-up and maintain such a system, and for many people that isn't worth the time or effort. And let's face it, although there are exceptions, the look and feel of Linux just can't stand up to OS X; At all.
I agree, and most consumers do, I am sure (as do most geeks, since we "know" that ogg-vorbis for instance, is as good or better than the other formats).. unfortunately this is the flip side of the free market :-(.
Yeah, I have that problem. I can connect from Tiger to Windows (although only sometimes from the Finder; otherwise I have to use smbclient), and from/to my Linux server.
I can connect from/to the Linux server from Windows as well, but not from Windows to the Mac. It just keeps on failing no matter what.
Under Panther (at least), Finder doesn't like samba options such as force user or similar, which I use to reach my root mount-point on my local server.
Finder will not be able to write files into places it thinks it can't - apparently without checking if it really is the case.
Conversely, Finder will attempt to write into places it thinks it can, but it can't, only to fail with a somewhat weird error message.
I don't know if this has been fixed under Tiger.
Actually, it seems from what I have seen that Core Image is not "there" if your graphics card is too old e.g. G-Force 440MX, so those things aren't done in the CPU; They aren't done at all (for instance certain animations when dragging widgets to the dashboard). There is also Quartz 2D extreme which is probably more what you are refering to (also not available on older gfx cards btw).
CSS2 has some internal contradictions which essentially makes it impossible to create a conforming implementation. However, applying common sense will resolve these, and indeed CSS2.1 resolves them to, what I think, most people would expect.
Curiously, the CSS2.1 abstract does not address this issue, even though it is, IMO, the most important ones (i.e. having internal contradictions is one of the worst thing a standard can have).
Now, why w3 is so slow pushing 2.1 to a standard (it's in a proposed state), is a mystery to me.