He could have gone with the Samsung "Pro" drives, which have held out to 2PB of data writes before croaking; they at least pretend to not be consumer drives.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
I might suggest that you need to not be expecting a consumer SSD to hold up to an enterprise workload.
Would it kill you to read the article? Its not even that long.
ALL of my browser activity through Google?
1) No, SSL and incognito not included.
2) It does what just about every other "data saver" of this type have always done (BES compression, Opera data saver, I believe safari has an example as well)
What are you doing that's writing ~100-200TB / year?
For a do-nothing pc you should be using any of the hundred sub-$60 128GB ssds.
SELinux stops all memory exploit mechanisms? Thats AMAZING.
TIL OpenBSD has built in anti-trojan tools, and the ability to secure browsers from their own memory corruption holes! WOW!
The NSA is a spy agency. You want the FBI, who actually does go after these things.
I think his point is that there could be alternate reasons why the door would not open besides the position of the switch. Malfunctions, whether mechanical or electrical, CAN happen and HAVE happened.
They are rare, but he is correctly noting that we're speculating here.
String += String
Im in a 200 level java class. We're just learning inheritance. I could have told you why thats a bad way to do things.
Do people not study what arrays are and why its expensive to continually append to them anymore?
Maybe these folks need to go back to basics.
And you've provided no evidence or analysis why you're supposed mitigations are an insurmountable defense; at best they're only a stop-gap.
In THEORY breaking most encryption is just guessing the right 2048-bit code. At best, increasing the length from 1024 to 2048 is just a stopgap.
In reality, some attacks are so esoteric and hard to pull off (famous example: hard drive magnetic domain remnant detection) that they are not a real-world threat. MAYBE they could adapt this, but it already requires
A) a machine connected to the internet that is compromised (!)
B) an AIR-GAPPED, high-security machine directly adjacent to it (!!!)
C) That that air-gapped machine be compromised as well (!!!!!)
D) Sensors in both machines sensitive enough to detect incredibly minor fluctuations in temperature (given that a steady stream of air will be flowing through)
The proper security procedure is to analyze the chance of the risk, the annualized loss expectancy, etc, and then come up with mitigations. Ok, let me give this a shot.
1) DONT GET YOUR AIRGAPPED MACHINE INFECTED
2) probably dont stick it directly adjacent to non-airgapped machines
Neither does soapboxing on slashdot.
They used python and java. Sort of hard to develop a meaningful thesis on general programming when you're that far up the abstraction stack. Who knows, maybe python and Java suck at memory management (GASP).
Your existing m.2 SSD is on a slot with 1GB (8gb) of bandwidth. I really dont think you're going to be maxing that out with any non-enterprise SSD, so you're probably OK-- and even if you somehow did, I seriously doubt you would notice.