on meltdowns
-
Vlad. — 7 years ago(July 04, 2018 10:59 PM)
I think the only logical conclusion with him is he's abusing a substance at night, likely booze, as every night he has an episode where he lashes out. Next day he's apologetic over how he behaved the night before.
Stop. -
djjsjfkemem3 — 7 years ago(July 04, 2018 11:00 PM)
just like my dad!
LIKE THIS ON FACEBOOK:
https://www.facebook.com/FilmBoards-IMDB-Message-Boards-Extension-1873692816293575/ -
djjsjfkemem3 — 7 years ago(July 04, 2018 10:07 PM)
this is kinda true. it seems like there's a conveyor belt of meltdowns on here and everyone takes a turn. in that case they kind of lose their punch i think - plus, it's hard to continue caring. desensitization and all that.
LIKE THIS ON FACEBOOK:
https://www.facebook.com/FilmBoards-IMDB-Message-Boards-Extension-1873692816293575/ -
-
djjsjfkemem3 — 7 years ago(July 04, 2018 10:19 PM)
i think the nicer and more stable the person is, the lower my desire to see them melt down. coincidentally, the likelihood of them melting down drops too. the ones who are immediately volatile already wear their emotions on their sleeve, so they are ones who have the true outbursts.
LIKE THIS ON FACEBOOK:
https://www.facebook.com/FilmBoards-IMDB-Message-Boards-Extension-1873692816293575/ -
Looksee — 7 years ago(July 04, 2018 10:31 PM)
Meltdowns are an effective way to lower social status, so as a power seeker, I welcome any and all meltdowns in my climb up the Filmboards ranks. I have never melted down and never will, either here or in Tinychat.
-
djjsjfkemem3 — 7 years ago(July 04, 2018 10:35 PM)
Meltdowns are an effective way to lower social status, so as a power seeker
very true!
LIKE THIS ON FACEBOOK:
https://www.facebook.com/FilmBoards-IMDB-Message-Boards-Extension-1873692816293575/ -
JaucySack — 7 years ago(July 04, 2018 10:17 PM)
this is kinda true. it seems like there's a conveyor belt of meltdowns on here and everyone takes a turn. in that case they kind of lose their punch i think - plus, it's hard to continue caring. desensitization and all that.
But what if On May 8, 1995, a paper called "The Intel 80x86 Processor Architecture: Pitfalls for Secure Systems" published at the 1995 IEEE Symposium on Security and Privacy warned against a covert timing channel in the CPU cache and translation lookaside buffer (TLB).[32] This analysis was performed under the auspices of the National Security Agency's Trusted Products Evaluation Program (TPEP).
In July 2012, Apple's XNU kernel (used in macOS, iOS and tvOS, among others) adopted kernel address space layout randomization (KASLR) with the release of OS X Mountain Lion 10.8. In essence, the base of the system, including its kernel extensions (kexts) and memory zones, is randomly relocated during the boot process in an effort to reduce the operating system's vulnerability to attacks.[33]
In March 2014, the Linux kernel adopted KASLR to mitigate address leaks.[34]
On August 8, 2016, Anders Fogh and Daniel Gruss presented "Using Undocumented CPU Behavior to See Into Kernel Mode and Break KASLR in the Process" at the Black Hat 2016 conference.[35]
On August 10, 2016, Moritz Lipp et al. of TU Graz published "ARMageddon: Cache Attacks on Mobile Devices" in the proceedings of the 25th USENIX security symposium. Even though focused on ARM, it laid the groundwork for the attack vector.[36] -
djjsjfkemem3 — 7 years ago(July 04, 2018 10:10 PM)
yes. i'm saving it for a particularly bad day.
LIKE THIS ON FACEBOOK:
https://www.facebook.com/FilmBoards-IMDB-Message-Boards-Extension-1873692816293575/ -
Rocketman — 7 years ago(July 04, 2018 10:13 PM)
that's a pretty lame ass excuse you should always use proper punctuation when you type stuff out it makes it easier for people to read it now re-write your op with proper punctuation.
please,
Throughout Heaven and Earth, I alone am the honored one. -
djjsjfkemem3 — 7 years ago(July 04, 2018 10:17 PM)
my punctuation is fine; it's pristine actually. i just didn't capitalize.
LIKE THIS ON FACEBOOK:
https://www.facebook.com/FilmBoards-IMDB-Message-Boards-Extension-1873692816293575/ -
JaucySack — 7 years ago(July 04, 2018 10:15 PM)
The Meltdown vulnerability primarily affects Intel microprocessors,[52] but some ARM microprocessors are also affected.[53] The vulnerability does not affect AMD microprocessors.[19][54][55][56] Intel has countered that the flaws affect all processors,[57] but AMD has denied this, saying "we believe AMD processors are not susceptible due to our use of privilege level protections within paging architecture".[58]
Researchers have indicated that the Meltdown vulnerability is exclusive to Intel processors, while the Spectre vulnerability can possibly affect some Intel, AMD, and ARM processors.[59][60][61][62] However, ARM announced that some of their processors were vulnerable to Meltdown.[53] Google has reported that any Intel processor since 1995 with out-of-order execution is potentially vulnerable to the Meltdown vulnerability (this excludes Itanium and pre-2013 Intel Atom CPUs).[63] Intel introduced speculative execution to their processors with Intel's P6 family microarchitecture with the Pentium Pro IA-32 microprocessor in 1995.[64]
ARM has reported that the majority of their processors are not vulnerable, and published a list of the specific processors that are affected. The ARM Cortex-A75 core is affected directly by both Meltdown and Spectre vulnerabilities, and Cortex-R7, Cortex-R8, Cortex-A8, Cortex-A9, Cortex-A15, Cortex-A17, Cortex-A57, Cortex-A72 and Cortex-A73 cores are affected only by the Spectre vulnerability.[53] This contradicts some early statements made about the Meltdown vulnerability as being Intel-only.[65]
On May 8, 1995, a paper called "The Intel 80x86 Processor Architecture: Pitfalls for Secure Systems" published at the 1995 IEEE Symposium on Security and Privacy warned against a covert timing channel in the CPU cache and translation lookaside buffer (TLB).[32] This analysis was performed under the auspices of the National Security Agency's Trusted Products Evaluation Program (TPEP).
In July 2012, Apple's XNU kernel (used in macOS, iOS and tvOS, among others) adopted kernel address space layout randomization (KASLR) with the release of OS X Mountain Lion 10.8. In essence, the base of the system, including its kernel extensions (kexts) and memory zones, is randomly relocated during the boot process in an effort to reduce the operating system's vulnerability to attacks.[33]
In March 2014, the Linux kernel adopted KASLR to mitigate address leaks.[34]
On August 8, 2016, Anders Fogh and Daniel Gruss presented "Using Undocumented CPU Behavior to See Into Kernel Mode and Break KASLR in the Process" at the Black Hat 2016 conference.[35]
On August 10, 2016, Moritz Lipp et al. of TU Graz published "ARMageddon: Cache Attacks on Mobile Devices" in the proceedings of the 25th USENIX security symposium. Even though focused on ARM, it laid the groundwork for the attack vector.[36]
On December 27, 2016, at 33C3, Clémentine Maurice and Moritz Lipp of TU Graz presented their talk "What could possibly go wrong with <insert x86 instruction here>? Side effects include side-channel attacks and bypassing kernel ASLR" which outlined already what is coming.[37]
On February 1, 2017, the CVE numbers 2017-5715, 2017-5753 and 2017-5754 were assigned to Intel.
On February 27, 2017, Bosman et al. of Vrije Universiteit Amsterdam published their findings how address space layout randomization (ASLR) could be abused on cache-based architectures at the NDSS Symposium.[38]
On March 27, 2017, researchers at Austria's Graz University of Technology developed a proof-of-concept that could grab RSA keys from Intel SGX enclaves running on the same system within five minutes by using certain CPU instructions in lieu of a fine-grained timer to exploit cache DRAM side-channels.[39]
In June 2017, KASLR was found to have a large class of new vulnerabilities.[40] Research at Graz University of Technology showed how to solve these vulnerabilities by preventing all access to unauthorized pages.[41] A presentation on the resulting KAISER technique was submitted for the Black Hat congress in July 2017, but was rejected by the organizers.[42] Nevertheless, this work led to kernel page-table isolation (KPTI, originally known as KAISER) in 2017, which was confirmed to eliminate a large class of security bugs, including the not-yet-discovered Meltdown – a fact confirmed by the Meltdown authors.[43]
In July 2017, research made public on the CyberWTF website by security researcher Anders Fogh outlined the use of a cache timing attack to read kernel space data by observing the results of speculative operations conditioned on data fetched with invalid privileges.[44]
Meltdown was discovered independently by Jann Horn from Google's Project Zero, Werner Haas and Thomas Prescher from Cyberus Technology, as well as Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from Graz University of Technology.[45] The same research teams that discovered Meltdown also discovered a related CPU security vulnerability now called Spectre.
In October -
djjsjfkemem3 — 7 years ago(July 04, 2018 10:27 PM)
quite.
LIKE THIS ON FACEBOOK:
https://www.facebook.com/FilmBoards-IMDB-Message-Boards-Extension-1873692816293575/