The Home Stretch
-
Put it in [spoiler][spoiler][/spoiler][/spoiler] tags. Google won't be able to defeat those! ;-)
-
Is it just me who keeps misreading the topic title as "The Home Stench" ?
Probably only non-native (or non-American?) speakers would do this. The actual title is a cliché, and not likely to be misread as something else.
-
EDIT: How the hell does SO make money? Just the stupid jobs page? I can tell you that ain't lucrative business.
Internet Bubble 2.0. (or did I miss some others?)
-
I've known plenty of homes like that, sad to say, It's one of the reasons I really don't want to go visit my father today.
-
!LikeBot remember BlakeyratsSecondLaw The longer a discussion continues on Discourse, the more likely it becomes that the discussion will be about how broken Discourse is.
-
Remembered 'The' as "The longer a discussion continues on Discourse, the more likely it becomes that the discussion will be about how broken Discourse is.".
-
fucking broken
-
!LikeBot remember BlakeyratsSecondLaw The longer a discussion continues on Discourse, the more likely it becomes that the discussion will be about how broken Discourse is.
!LikeBot forget The
-
Remembered 'BlakeyratsSecondLaw' as "The longer a discussion continues on Discourse, the more likely it becomes that the discussion will be about how broken Discourse is.".
Forgot 'The'.
-
Well, while we're here.
This still hasn't been fixed.
-
Directory.CreateDirectory() creates directory entries that don't have any fucking NTFS permissions (like they are LITERALLY missing - can't view, edit, take ownership, ANYTHING. Because the permissions metadata just isn't fucking there
That says to me that the encryption product is hooking the filesystem, which it absolutely should not need to do. Transparent disk- or volume-level encryption is the Right Thing, in my opinion; people who use filesystem-level encryption are just asking for trouble.
-
As of now, we've completely abandoned that product. The Patent Troll firm that bought the vendor cuts support at the end of the month anyway.
We do not have any IT Security authorized replacements. Every disk/volume level solution they've evaluated falls short (often on 'need to enter a password at boot')
We bought a NAS filer cluster that supports transparent encryption, but it needs to be set up at the cluster level and, well, it wasn't (and you have to delete and recreate all your volumes to change it. Which ain't gonna happen).
And then someone happened to mention 'hey, we bought a cloud NAS thingy and have no idea what to use it for' (basically VM appliances sit on premesis and act as caches/encryption engines that stuff the data, heavily encrypted, in commodity cloud storage).
Our data is like .1% hot at any point and will conveniently fit in a cache. AWS storage is SUPERCHEAP compared to our datacenter storage. Security isn't terribly pleased, but they can't find any reasons to object to us trying it out.
-
Every disk/volume level solution they've evaluated falls short (often on 'need to enter a password at boot')
If you can just boot the system to read it without a problem, how is it secure?
-
That depends on the problem you're trying to solve with encryption. In our case, it's not access control (the OS does a fine job of that) and it's not theft (that's what the datacenter security team is for). It's ensuring dead and replaced drives don't contain anything useful.
-
A sledgehammer would probably be cheaper, more reliable and most satisfying.
-
A sledgehammer would probably be cheaper, more reliable and most satisfying.
Or a small blowtorch. Get that platter over its curie temperature, and there will be no data left.
-
Or one of these:
https://www.youtube.com/watch?v=ibEdgQJEdTAor its big brother:
https://www.youtube.com/watch?v=sQYPCPB1g3oddrescue that, bitch
-
ddrescue that, bitch
Might be doable. But only if it was Linux hardware to begin with.
wooshes and calling me stupid incoming in 3... 2...
-
Might be doable. But only if it was Linux hardware to begin with.
I see you like jigsaw puzzles…
-
Might be doable
Gather all the pieces in a bucket and send them back to Seagate for warranty replacement. Betcha they'd do it, too.
Edit: I wonder how many hard drives you'd have to shred with that thing before it became completely clogged with high-strength magnets.