Horse shit. There is more "noise" (signal) in a 10-bpc source than an 8-bpc source OR an 8-bpc conversion of a 10-bpc source. You just can't see it as easily with your eyes.
I suggest no one do that, because it's fucking horse shit. I know the fucking document you're referring to, and it's wrong, wrong, wrong. There is no reason to use 10-bit encoding over 8-bit encoding unless you're using a shitty fucking encoder that introduces rounding errors at every step. Decent encoders work in a higher precision before shitting out the encoded result.
Address randomization would still help against physical dumps or exploits at the OS level that would allow processes to peek at memory they shouldn't be able to. Performance is very minimally impacted.
Performance is an issue, sure. It's an extremely minor one with the CPUs we have today, but for most cases I'd say the security benefits are worth the overhead.
Any existing software (that can't/won't be updated to go through the OS for shared memory) could: A - be white listed by the user B - be automatically handled by the OS if the OS knows the various threads/processes are part of an overall application or workflow and should have access to each other's shit C - be allowed to do whatever as long as it doesn't fuck with shared memory of a higher-privileged process
I've never gotten a satisfying explanation of why process X is allowed to overwrite memory belonging to process Y, thus causing Y to do BADSHIT when it jumps to that location.
I've also never gotten a decent explanation as to why stack overflow is still a problem or why process X can heap spray the fuck out of memory and have that shit affect process Y.
The OS should be managing memory. Address locations should be randomized. Memory should be zeroed out upon allocation (or deallocation, or both). Memory not allocated to a process should not be accessible by that process. If the stack fills up your shit should stop, not overwrite the heap. Etc.
The OS should be handling this shit, and the OS should provide the tools for interprocess communication, debugging, etc., either via an API, a privileged process, or whatever. If I want to debug process Y and read its memory, then I should need to respond to a security prompt (UAC or whatever) to do so.
Shared memory should be virtually mapped such that process X and process Y see two different addresses, but the OS knows both map to the same real address. Writing to shared memory should be done only by the OS, as you're loading shared libraries or whateverthefuck. Alternatively, any time shared memory is written to, it should be forked and unshared so each process gets their own copy - one with the changes and one untouched. We've got plenty of memory now, lets use it. You'd need to track who spawned whatever process tried to read/write that memory to determine what overall application "owns" that memory for instances where shared memory (with write access) is valid. This lets shit work without letting one process/application escalate its privilege level by fucking with shared memory a privileged process/application is using.
Windows users can download EMET to do this. It's from MS and it's free. It lets you force a bunch of shit (like ASLR), lets you set up certificate pinning for websites (trust only certain certs or block specific certs), etc. https://technet.microsoft.com/...
It's called "annealing", look it up. It has to do with heating and cooling materials to relieve stressed points.
"Quantum annealing" is related to "simulated annealing" which in turn is in no fucking way related to actual annealing. Some clown simply decided to refer to the time component as temperature for no fucking reason and whipped himself up into a fervent state of tumescence by conflating local maxima/minima in a discrete, finite search space with stressed points in a material.
Annealing is a physical process which alters an object such as a metal beam, a glass rod, or a band of rubber. "Simulated annealing" is a time-constrained search algorithm which produces a non-deterministic result (relying on PRNG) without altering the finite, discrete set over which it operates.
You better learn your fucking shit before you come stepping, boy, lest you trip like a little bitch.
You need to know what you're doing to do anything successfully dangerous (or dangerously successful) with this.
On the other hand, any schlub can create children, the world's nastiest petri dishes. Alternatively, any schlub can scrape up some black mold or whatever and gradually engineer it to resist chemicals, heat, cold, etc. by simply gradually exposing it to those things at a rate that still lets the colony grow. For bonus points, gradually change its diet to human skin and hair.
Slashdot Mirror
I'm glad I sent that caustic, hateful tweet about it. It surely played a role in this decision.
17.5 is 15.5 more than 2.
15.5 is 7.75 times 2.
17.5 is 8.75 times 2.
17.5 is 7.75 times more than 2.
.
It's real.
It's called a pozzing party.
I'll never solve the new captchas.
Not without the use of the word "and". And that's not a list anyway.
World yaps on about how Musk's farts smell the best.
No, it fucking isn't.
""Credible" Bomb Threat Closes, Evacuates All Los Angeles Public Schools"
According to the title, the bomb threat is "credible", and the bomb threat closes. Everything from the comma on is a language-raping jumble of shit.
That's a good WRONG. Love it.
Horse shit.
There is more "noise" (signal) in a 10-bpc source than an 8-bpc source OR an 8-bpc conversion of a 10-bpc source.
You just can't see it as easily with your eyes.
I suggest no one do that, because it's fucking horse shit. I know the fucking document you're referring to, and it's wrong, wrong, wrong.
There is no reason to use 10-bit encoding over 8-bit encoding unless you're using a shitty fucking encoder that introduces rounding errors at every step. Decent encoders work in a higher precision before shitting out the encoded result.
Applying Hillary Clinton logos and decals to my car and trading it in.
BRB.
Using eight 300W GPU slots
Dubbed "Big Sur," the hardware includes eight high-performance GPU boards of up to 33 watts
Quite a bit of difference...
String theorists are not physicists. They are mathturbators, at best.
Use. Use your preview, cows.
Posted too quick
Quickly. User your adverbs, people.
Address randomization would still help against physical dumps or exploits at the OS level that would allow processes to peek at memory they shouldn't be able to.
Performance is very minimally impacted.
Performance is an issue, sure. It's an extremely minor one with the CPUs we have today, but for most cases I'd say the security benefits are worth the overhead.
Any existing software (that can't/won't be updated to go through the OS for shared memory) could:
A - be white listed by the user
B - be automatically handled by the OS if the OS knows the various threads/processes are part of an overall application or workflow and should have access to each other's shit
C - be allowed to do whatever as long as it doesn't fuck with shared memory of a higher-privileged process
It should be.
I've never gotten a satisfying explanation of why process X is allowed to overwrite memory belonging to process Y, thus causing Y to do BADSHIT when it jumps to that location.
I've also never gotten a decent explanation as to why stack overflow is still a problem or why process X can heap spray the fuck out of memory and have that shit affect process Y.
The OS should be managing memory. Address locations should be randomized. Memory should be zeroed out upon allocation (or deallocation, or both). Memory not allocated to a process should not be accessible by that process. If the stack fills up your shit should stop, not overwrite the heap. Etc.
The OS should be handling this shit, and the OS should provide the tools for interprocess communication, debugging, etc., either via an API, a privileged process, or whatever. If I want to debug process Y and read its memory, then I should need to respond to a security prompt (UAC or whatever) to do so.
Shared memory should be virtually mapped such that process X and process Y see two different addresses, but the OS knows both map to the same real address. Writing to shared memory should be done only by the OS, as you're loading shared libraries or whateverthefuck. Alternatively, any time shared memory is written to, it should be forked and unshared so each process gets their own copy - one with the changes and one untouched. We've got plenty of memory now, lets use it.
You'd need to track who spawned whatever process tried to read/write that memory to determine what overall application "owns" that memory for instances where shared memory (with write access) is valid. This lets shit work without letting one process/application escalate its privilege level by fucking with shared memory a privileged process/application is using.
Windows users can download EMET to do this.
It's from MS and it's free. It lets you force a bunch of shit (like ASLR), lets you set up certificate pinning for websites (trust only certain certs or block specific certs), etc.
https://technet.microsoft.com/...
We definitely need more outsourcing and H1-Bs. That would surely fix this.
Is autistic.
Tries to "pass" as normal.
Creates username "king neckbeard".
The state always acts quickly to seize a citizen's money.
It's called "annealing", look it up. It has to do with heating and cooling materials to relieve stressed points.
"Quantum annealing" is related to "simulated annealing" which in turn is in no fucking way related to actual annealing. Some clown simply decided to refer to the time component as temperature for no fucking reason and whipped himself up into a fervent state of tumescence by conflating local maxima/minima in a discrete, finite search space with stressed points in a material.
Annealing is a physical process which alters an object such as a metal beam, a glass rod, or a band of rubber. "Simulated annealing" is a time-constrained search algorithm which produces a non-deterministic result (relying on PRNG) without altering the finite, discrete set over which it operates.
You better learn your fucking shit before you come stepping, boy, lest you trip like a little bitch.
It heats and cools materials to remove stresses?
No?
Then it's not fucking annealing.
You need to know what you're doing to do anything successfully dangerous (or dangerously successful) with this.
On the other hand, any schlub can create children, the world's nastiest petri dishes.
Alternatively, any schlub can scrape up some black mold or whatever and gradually engineer it to resist chemicals, heat, cold, etc. by simply gradually exposing it to those things at a rate that still lets the colony grow. For bonus points, gradually change its diet to human skin and hair.
Personally I'm working on a sentient Cheeto farm.