- Posts: 7880
- Joined: Fri Dec 09, 2011 1:05 pm
- Location: Hotel California, PH23
- Occupation: Voice Actor, Podcaster, I hold a Ph.D in Procrastination.
Internet Research Agency takes getting fired in a whole new direction:
https://themoscowtimes.com/news/infamou ... fire-63130
Surveillance footage published by FAN showed flames erupting at one of the empty workstations and a female staffer stationed on the opposite end quickly exiting the office.
“I believe this is tied to FAN’s activities,” its chief editor Yevgeny Zubarev said. “We’re most often attacked online, but these types of attacks have already taken place offline.”
FAN said its office came under another arson attack on the eve of the 2018 presidential elections in March.
St. Petersburg police told the RBC news website that they were looking for the culprit and planned to launch criminal proceedings.
A Purge is in the works of all the people involved in the meddling.
- Posts: 3392
- Joined: Fri Nov 16, 2012 6:02 pm
- Location: Happy Valley, MA
- Occupation: Damned if I know
asm("hcf" ::: "memory");
There's no way back
from there to here
- Posts: 3829
- Joined: Thu Jan 12, 2012 1:36 am
- Location: The great San Fernando Valley
- Occupation: Web developer
I wrote assembler on about a dozen different computers, including the 360, and yeah, no such animal. But I did encounter a computer where you could heat up and destroy a memory location!
On the backup air defense program (ca. 1968) our low level wait loop was a single instruction loop (jump *). On at least one machine, the continuous access of that memory location heated the wires (it was core memory) and burned out the memory. I said it was a hardware bug, but an Air Force person found in the specification the statement "Permanent memory should not be destroyed during operation.*" So we added a few NOP instructions to the loop.
* "Permanent memory" actually referred to the configuration data - location of air bases and radars, aircraft characteristics, etc. which were kept in memory. But after seeing where the statement was in the specification, and stopping laughing, we decided that since we could fix it, we should.
- Posts: 10
- Joined: Thu Jul 06, 2017 1:45 am
tek wrote: ↑
Tue Oct 09, 2018 11:11 am
asm("hcf" ::: "memory");
I got that reference!
- Posts: 1657
- Joined: Fri Jun 02, 2017 9:08 am
I can recall there were attempts to make malicious code that could cook a CPU, including trying to control the fan on boards that supported that, but that was a much more recent thing.
- Posts: 9696
- Joined: Mon Jan 09, 2012 11:36 am
Who needs bleach bit when you have thermite memory.