Slashdot Mirror


Microsoft Offers New Data-Security Scheme

bingly_beep writes "The BBC is reporting Microsoft's new user security measure, whereby users sensitive information is stored on their PC rather then online, as in their previous offerings, such as Passport. This sounds like a good idea, but any such system would surely require that the user definitely erases the HD on any machine they sell. Perhaps Microsoft should include an option, like 'Prepare this computer for resale,' which utterly destroys all data."

62 of 309 comments (clear)

  1. In future headlines... by Caspian · · Score: 4, Funny

    Pimp offers new "disease-free guarantee".

    --
    With spending like this, exactly what are "conservatives" conserving?
    1. Re:In future headlines... by mboverload · · Score: 3, Informative

      I made a guide to using eraser, which would do the same thing. http://mboverload.no-ip.org/tech/recyle.html

  2. Aw hell... by werewolf1031 · · Score: 5, Insightful
    Perhaps Microsoft should include an option, like 'Prepare this computer for resale,' which utterly destroys all data."

    Yeah, like THAT won't be hacked all to fvck by virus-writers. Great suggestion!

    1. Re:Aw hell... by rbarreira · · Score: 4, Insightful

      Virus writers don't need that to destroy the data of a windows pc...

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
    2. Re:Aw hell... by nine-times · · Score: 3, Insightful
      You know what, I actually really like the idea. Maybe it shouldn't be too simple, but in theory, all user data SHOULD be kept in the user's profile. I hate when some application developer doesn't follow this, but it really should be kept there, and every user should have full access to their own profile anyway.

      So, if you had some user-friendly (but clearly labeled, and with warning messages) option to "secure delete" user profiles, it seems like it would be a nice security measure. It's not technically difficult, and not anything a virus/trojan couldn't do on it's own, and if all user data really is being stored in the user profile, it's not complicated.

    3. Re:Aw hell... by werewolf1031 · · Score: 5, Insightful
      and not anything a virus/trojan couldn't do on it's own

      Not quite. Think about it: In this particular scenario, we're keeping all our personal/important/sensitive data in one place, and more dangerously, a place that's standardized, ie. easy to find. At least with users scattering their personal stuff all over the hard drive, it's easier to "mask" from a virus/trojan looking for that data.

      But with this new setup, the data's all in one spot. In the SAME spot, regardless of the machine or the user. (Cuz you just know that MS is gonna create a standard folder for this.)

      So, by doing this, it'd actually make the malicious program writer's job easier.

    4. Re:Aw hell... by MoonBuggy · · Score: 3, Insightful

      Even if it were made completely secure (let's say it could be done, for argument's sake) how many users would be willing to wait for 120GB+ to be randomly overwritten 5+ times? I know that using the '8 way random write' option on my OSX install CDs to nuke a 120GB drive before I sold my old Mac took one hell of a long time to run (multiple days, the kind of time a regular user is not going to enjoy waiting).

      AFAICS they simply wouldn't bother waiting for this unless it was made significantly faster, and since I assume it's a pretty simple task I don't really see how that could be done.

    5. Re:Aw hell... by nine-times · · Score: 2, Insightful

      All that sort of data should be kept in a standard place anyway. Scattering it about the hard drive only means that users need higher access levels to more directories, which INCREASES the damage a virus is able to do (assuming users aren't running as admin, which they shouldn't be, and assuming a virus isn't exploiting a security hole to elevate its privileges, which there isn't much you can do to prevent it from wreaking whatever havoc it wants at that point).

    6. Re:Aw hell... by werewolf1031 · · Score: 3, Informative
      assuming users aren't running as admin, which they shouldn't be

      You're absolutely right, they shouldn't be. But they are, a great many of them, because unfortunately many 3rd-party apps, especially games, require admin rights to run properly -- and who wants to exit and login as a different user every time they want to play a game? (Which in itself is a separate rant.)

      With so many users running with admin rights, it'll be a no-brainer to compromise this particular setup.

    7. Re:Aw hell... by nine-times · · Score: 3, Insightful
      You're absolutely right, they shouldn't be. But they are, a great many of them, because unfortunately many 3rd-party apps, especially games, require admin rights to run properly -- and who wants to exit and login as a different user every time they want to play a game? (Which in itself is a separate rant.)

      With so many users running with admin rights, it'll be a no-brainer to compromise this particular setup.

      I guess that, when Microsoft talks about their future plans for "improving security", I assume that the first assumed step is to rectify that particular problem. Perhaps I'm naive to attribute even this small measure of care and competence to Microsoft's developers. However, any other security steps are pointless until this issue is rectified. Frankly, it's obscene that Windows has been encouraging users to run as admin for so long, and failing to discourage developers from requiring administrator access to run simple applications. It's pointless and it's stupid.

    8. Re:Aw hell... by sqlrob · · Score: 4, Informative

      The "Designed for XP" label requires the ability to run as a lower privileged user. I don't know how much more MS can really do to enforce it.

      The problem with games is that they use low level access for copy protection tests, and need admin level to do that.

    9. Re:Aw hell... by Anonymous Coward · · Score: 2, Informative

      Frankly, it's obscene that Windows has been encouraging users to run as admin for so long, and failing to discourage developers from requiring administrator access to run simple applications. It's pointless and it's stupid.

      To put it bluntly, you don't know what you're talking about.
      As a software developer, I know firsthand that Microsoft is trying to get application developers to stop writing programs that require the users to be Admin level. If you know anything about .NET logo certification, you would know that in order for your application to pass the test, it has to be able to be successfully installed at all login levels (except Guest, I think).

      Yes, you may have glazed over this when you mentioned "future plans for improving security" but it's no fault of Microsoft's (that I'm aware of, at least) that for a long while there were a bunch of application developers who had no idea what they were doing. That's what the whole idea of the .NET framework is about - standardization.

    10. Re:Aw hell... by sokoban · · Score: 2, Funny

      ...installing windows takes care of that pretty well already.

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 is the magic number.
    11. Re:Aw hell... by MoreDruid · · Score: 2, Interesting
      Why then don't the developers create something like Nero Burning Rom does? Create a separate group for gaming, with all appropriate permissions. Shouldn't be that hard.

      On another note, I'd like Windows to have simple profile switching. No, not the user profile, but the system settings. 1 gaming profile with all the systray stuff out of the way except for AV-software and the firewall, no background services bloat etc. Another profile for strictly browsing and e-mailing with super-restricted access to the lower layer API's or everything sandboxed or whatever. Third profile for productivity apps. E-mailing and web browsing are almost a must here so this may make profile 2 not needed (except in the home for your kids maybe?) but this also needs to be sandboxed. I don't mind waiting for an extra 5 seconds loading my mailclient for security reasons. If Microsoft could make this work (aw with so much money in the bank, they ought to be) they'd have a very powerful feature on their hands. It increases their security (which is mediocre at best) and improves on the user experience. The only problem I can think of is the load time of these profiles. That should be kept to a minimum.

      --
      The best weapon of a dictatorship is secrecy, but the best weapon of a democracy should be the weapon of openness.
  3. Windows already has such a feature... by Anonymous Coward · · Score: 3, Funny

    Doesn't installing windows automatically come with built in features that "destroy all data"?

    The problem with the feature right now is that it happens when you least expect it, rather than when you'd actually want it to occur.

    1. Re:Windows already has such a feature... by The+Bungi · · Score: 2, Funny

      Yes. It's called "Knoppix".

  4. Ready for sale by Mononoke · · Score: 2, Funny
    Perhaps Microsoft should include an option, like 'Prepare this computer for resale,' which utterly destroys all data.
    I think they called that Windows 3.1
    --
    NetInfo connection failed for server 127.0.0.1/local
  5. MS coverup? by rokzy · · Score: 2, Interesting

    there was a story a few minutes ago about a report that Windows security was better than Linux but then it came to light afterwards that it was MS funded but undislosed.

    it seems to have disappeared and been replaced by this advert for MS doing good things for security?

  6. Both sides of the coin by 00+Agent+Kid · · Score: 5, Interesting

    This could be good or bad. The data, stored on the computer, would not be on the Internet all the time and thus be safer. On the other hand, .Net has great security. A user with little computer knowledge would not protect his/her computer well enough from hackers, etc., which would leave the data "out there." I think that the latter is safer, however.

    And, as stated in the article, there had better be a way to destroy all sensitive data if the user wishes to sell the computer.

    --
    INACTIVE ACCOUNT
  7. Either solution is flawed by Jailbrekr · · Score: 5, Insightful

    So you either store the information locally, and run the risk of a local exploit thanks to the latest and greatest security hole, or you store the information online, and run the risk of the central site being compromised. The first will be more common but limit the data theft to only a single person, whereas the second will be much less frequent but will limit the data theft to the entire customer base.

    In the grand scheme of things, they are both as flawed, just in differing ways.

    --
    Feed the need: Digitaladdiction.net
    1. Re:Either solution is flawed by nine-times · · Score: 2, Insightful
      Very insightful post. I think part of what turns people off about a centralized server, however, is the possibility of snooping by the very people running the server. Also, whenever you talk about storing data on a remote server, there's the question of the up-time of that server (which is something users don't have control of themselves.

      On the other side, data stored in a centralized server is more readily accessible anyway. Also, data-redundancy and backups are usually more cost/time efficient when done on a large scale.

      So again, there are trade-offs between the two methods.

    2. Re:Either solution is flawed by real_smiff · · Score: 3, Interesting
      ah but for any individual, the choice is real. for example, *i* may feel happier looking after my own data. someone less geeky might well feel safer letting a big corporation do it for them (and indeed may well be safer that way). and since this issue is mostly about peace of mind anyway*, and both are flawed as you say, it is a valid distinction i think. if you give people the choice and explain the pros and cons i dont see a problem. (i have not RTFAd).

      * and i would say unlikely threats, for any one individual, and compared to all the risks everyone faces in life. imho.

      --

      This is my Sig, this is my Gun. One is for Slashdot and one is for Fun.

  8. rather then by ezzzD55J · · Score: 5, Funny
    rather THAN

    rather THAN damnit

    please continue

  9. Oh Please by finkployd · · Score: 5, Funny

    This sounds like a good idea, but any such system would surely require that the user definitely erases the HD on any machine they sell.

    Yes, because today it is perfectly ok to sell a system without erasing the hard drive. I mean for real, who stores private or important data on a computer?

    Finkployd

  10. ok so i will spoof by bird603568 · · Score: 2, Interesting

    whereby users sensitive information is stored on their PC rather then online, as in their previous offerings, such as Passport.
    wouldn't that lead to easyer spoofing?

  11. Re:this is a duplicate people by Tony+Hoyle · · Score: 2, Informative

    No it isn't.

    Have you even looked at both links? They're entirely different.

    I even believed you for a minute... it's not like dups are uncommon on slashdot, but WTF has storing data on your own hard disk got to do with a dodgy research paper?

  12. The assumption being by popo · · Score: 5, Interesting

    MSFT's assumption is apparently that data stored on personal computers is more secure than on servers.

    I'm not sure that this is necessarily true.

    When you consider that the vast majority of computer users have no idea what a "firewall" is, and that MSFT's track record for security is poor to say the least -- its not obvious that storing sensitive data in designated locations on PC's is the safer route at all.

    Some might say this is MSFT's way of passing the buck of responsibility to the end user rather than fixing the problem. Now if data is compromised fault could arguably lie with mom and pop rather than a Microsoft server.

    --
    ------ The best brain training is now totally free : )
    1. Re:The assumption being by SilentChris · · Score: 2, Insightful

      "Now if data is compromised fault could arguably lie with mom and pop rather than a Microsoft server."

      It's a classic situation of "damned if you do, damned if you don't".

      Microsoft releases Passport, "secure online identity system", onus on MS not to screw things up (legally liable). Everyone hates it.

      Microsoft releases new system, "secure offline identity system", onus on user not to screw things up (legally liable). Everyone hates it.

      I don't think there's anyway for MS (or any other company) to "win" this battle. Personally, I think the onus of responsibility should be on the computer user. MS, Apple, etc gives you the tools to be secure (as long as you stay up-to-date with the patches), and people continue to ignore them.

      Just the other day someone said their home computer was flashing "notes by the clock" that "their system needed to be updated". Did they update, I asked. No. Did they want MS to install things without asking? No. Now who's responsibility is it here when the machine gets hacked?

  13. Is it just me, or... by FlyByPC · · Score: 3, Insightful

    ...is there something fishy about trusting Microsoft to manage confidential data?

    Yeah, it's better than Passport, where they not only manage the data but store it too -- but for true privacy, shouldn't the relevant code be open for all to see? At least the encryption algorithm, anyway...

    --
    Paleotechnologist and connoisseur of pretty shiny things.
  14. What happens if I press this button? by dauthur · · Score: 2

    I think that Microsoft fails to see the only way to make their data secure: Disconnecting it from the internet completely.

    Just running any Windows box online is a security risk, and until Microsoft figures out that our "precious" data can only be secure by having absolutely no connection to it, will anyone have no breakins. It would make more sense for Microsoft to offer some sort of "data security lock-box" on their own machines, where their data is stored on disconnected machines, where if needed, a direct request to Microsoft can be given.

  15. Insecure Cookies by The+Amazing+Fish+Boy · · Score: 5, Insightful

    Read the article. Sounds like they've made cookies, but more than one site can read them. My guess is you'd have to authorize the site to read them, but this is bad news.

    If a site can trick you into hitting "OK," they could get your info.

    Of course the site probably has to be registered with MS in some way. Maybe this is a way for Microsoft to offer a "secure browsing experience" that is also convenient. IE7 will likely view MS-approved sites as "higher security" than SSL approved sites.

  16. Erasing the HD? by SiO2 · · Score: 4, Informative

    Erasing or otherwise formatting a hard drive doesn't do any good to eradicate personal information. I've used these guys on numerous occasions to successfully recover data from hard drives that have been formatted, imaged, etc.

    If you're going to sell a computer, swap out the drive containing your data for a new one. They're cheap. Hold onto the drive that houses your data.

    SiO2

  17. The big upside for Microsoft by rewt66 · · Score: 2, Interesting

    If the data gets compromised in a central Microsoft server, Microsoft is the only one to blame. If the data gets compromised on your home PC, Microsoft will blame you for failing to secure it properly.

  18. Prepare Computer For Resale by topgeek · · Score: 2, Funny

    I like the idea of a button with this function. But at the same time, it should back-up my Outlook addresses, save my bookmarks, transfer my MP3s to my file server, and then post my used computer listing on eBay.

    --
    Geek Of The Day, "A geeky place for geeky faces."
  19. Utterly destroying all data by Ars+Dilbert · · Score: 3, Insightful
    "Perhaps Microsoft should include an option, like 'Prepare this computer for resale,' which utterly destroys all data."

    They are probably afraid of getting customer support calls from people who used that option to "see what it did", or from people who changed their mind and wanted their data recovered, or folks who thought that MS didn't really mean it when they said (with a huge red bold and blinking disclaimer no less) that all data would be erased. Ahd then they'd sue MS, OEM, and CompUSA for the emotional distress caused by the loss of their data.

  20. just shred it by budgenator · · Score: 4, Interesting

    One little linux command is all it takes, insert linux live CD and su -c"shred /dev/hda" and even the NSA would have trouble getting any data off the harddisk, windows license isn't transferable anyways. Fight software piracy, shred used Windows hard disks!

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
  21. "Prepare computer for resale" by Bifurcati · · Score: 2, Funny

    Microsoft Windows is preparing your computer for resale. Please insert your Red Hat Linux CD now.

  22. To utterly destroy all data... by Webmoth · · Score: 2, Interesting

    You could use Autoclave, but since it's being end-of-lifed, you could follow the Autoclave author's recommendation and use Darik's Boot and Nuke instead.

    --
    Give me my freedom, and I'll take care of my own security, thank you.
  23. Resale? by Racter · · Score: 2, Funny
    Perhaps Microsoft should include an option, like 'Prepare this computer for resale,' which utterly destroys all data."

    Or, as we like to call it, 'Prepare this computer for confiscation.'

  24. Re:Cleaning up HD by mike5904 · · Score: 2, Informative

    For general purposes, yeah, but if someone is intent on getting at your data, with a lot of work they can still get to it. All deleting a partition with fdisk does is destroy the partition information, so it looks like unallocated space on the drive. It never actually deletes the data.

  25. Re:Permanent Data Deletion Tool by SirTalon42 · · Score: 2, Informative

    Or you could do "shred -z /dev/hda" which is MUCH more secure. It will write over the drive 25 times w/ random data (you can change it with the
    -n' switch to any number you want), and then write zeros to the disk.

  26. The most practical way to permanently erase a HDD by karlandtanya · · Score: 4, Insightful
    is with thermite.

    You can use a 5/7/9 pass DOD overwrite. Or a 39-step Gutmann overwrite. Or the ultrasuperduperTFH method of... You get the idea. It takes a looonng time.

    HDDs are cheap, especially one you've used so long you're going to sell the computer.

    Take it apart & melt the disks. If you have a lot of them, just use a fish cooker.

    --
    "Reality is that which, when you stop believing in it, it doesn't go away." - Philip K. Dick
  27. Re:Cleaning up HD by mboverload · · Score: 2, Insightful

    All that does is write over your data with a 0. It is complicated, but it is VERY easy to recover formatted data. What you need to do is white is 7+ times with random data.

  28. Puff stuff by Obstin8 · · Score: 2, Interesting
    This reads like a pure piece of Microsoft fluff. Raise the spectre of 1 billion in fraud committed against 25%(!) of the UK population. Well, not really a full 25%, but they might know someone, who knew someone else, who heard about a guy once who....

    We can probably assume that Microsoft's previous "Safe ID" a.k.a. Passport can account for a portion of the high-tech (i.e. non-"other means") ripoffs. 200 million potential vulnerabilites and it's "popularity suffered". A masterful understatement.

    If they have proven themselves completely inept at securing at storing 200 million passwords on one password server system, why would anyone think they could possibly secure one password on 200 million password server systems?

    I suspect they're just drumming up new lock-ins for Longhorn. FTA: "would not confirm however whether the new info cards ID system will be built into the current Windows XP version or Longhorn". If i were a betting man...

    --
    Remember, it's never too late to have a happy childhood!

  29. April 1 yet? no, not yet. by idlake · · Score: 2, Interesting

    Prior to hare-brained schemes like Passport, where exactly does Microsoft think people stored sensitive information? That's what we have had keychains, vaults, and client certificates for, supported by browsers, operating systems, and add-ons.

    Maybe this whole story is an attempt to create the false impression that this is new, breakthrough technology so that Microsoft can then patent "local disk storage of personal information"? Or maybe it's just an April's Fools joke.

  30. Resale by bourne_id · · Score: 2, Interesting
    Prepare this computer for resale, which utterly destroys all data

    Which would probably wipe the harddrive so that M$ would have to sell the new schmuck a new Windows license.

    JMD

    --
    When all else fails, feel free to panic.
  31. Faster yet by ari_j · · Score: 2, Funny

    I use a .308 Win. 2500fps beats your solution and guarantees every sector you hit will be unreadable.

    1. Re:Faster yet by slazar · · Score: 3, Funny

      2500 fps!?! That's Unreal®!

  32. Think again! by flithm · · Score: 2, Informative

    From the shred manpage:

    CAUTION: Note that shred relies on a very important assumption: that
    the filesystem overwrites data in place. This is the traditional way
    to do things, but many modern filesystem designs do not satisfy this
    assumption. The following are examples of filesystems on which shred
    is not effective:

    * log-structured or journaled filesystems, such as those supplied with

    AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)

    Ie, shred is useless. Also of note is someone's idea to write /dev/null to /dev/hd? is also useless for this same reason.

    Also of note is that this applies to Windows users (NTFS) as well!

    For more information check http://http://www.infoanarchy.org/wiki/index.php/F ile_Wipe

    The basic idea is summarized here:

    There are several ways to securely wipe files when using journaling filesystems:

    1. Store data that needs to be wiped on a partition (slice, volume, or drive) that uses a non-journaling filesystem. For example, users of Windows can use a Z: drive formatted with FAT32, and users of GNU/Linux can use a partition formatted with Ext2.
    2. Store data that needs to be wiped on a partition that is encrypted using Hard Disk Encryption. This eliminates the need to use a secure wiping mechanism for individual files.
    3. Store data on a temporary partition using any journaling or non-journaling filesystem. When it is time to wipe all files, use a tool such as Eraser or Wipe to securely wipe the entire partition.
    4. Physically destroy the hard drive after use by melting the hard drive. (Passing a magnet over the hard drive will not work.)

    Ie... There is no method for proper undelete protection of journalled drives. Better have your thermite ready!!

  33. windows XP filevault equivalent? by bloosqr · · Score: 2

    Someone pointed out to me that it seems a bit odd that when berkeley got their laptop stolen w/ everyone's computer data that apparantly berkeley can't be bothered to do what nearly everyone who uses a laptop on a mac and anything vaguely "sensitive" (typically quicken data etc) takes for granted: Encrypted file system. On a mac this is as easy to do as clicking "security" from system preferences and hitting filevault on. Given the number of times Los Alamos, CIA, colleges keep losing sensitive info on laptops there's got to be an equivalent on windows? (My understanding is its something called EFS) Does anyone here use it? I am curious why this isn't enabled by default on laptops or administrators of laptops in universities, feds etc etc etc. On a mac its trivial to turn this on (its AES 128 bit). Linux has cryptfs which is blowfish 128 bit. Surely this is in place in the windows world at this point?

    -bloo

    1. Re:windows XP filevault equivalent? by TheAwfulTruth · · Score: 4, Informative

      Yes and it has been for years.

      But just like Mac (now) and Linux it is off by default.

      One main reason is that in order to use it (on any OS) you have to use your brain. Basically you have to rememeber to properly handle your user data before mucking about with user accouts or you can permanetly lose everything. This problem has already been demonstrated repeatedly in the Mac user space WRT iTunes downloads which are pinned to used accounts. Destroy a user account before transferring ownership of the data and yo ulose your songs.

      Of course, this is the point. But what happens is, 99 out of 100 people that lose everything do so in situations where they didn't really want to.

      Thus, use of the systems by people that don't know how they work or what the drawbacks are are more likely to have problems with their data by using the system than by not using it. So, in all cases, the EFS remains turned off by default.

      --
      Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
  34. Re:Hard Drive Forensics by AtariAmarok · · Score: 2, Funny
    "Keeping the disk, pulverizing it completely, or throwing it into Mount Doom would seem to be the most reliable methods of ensuring security"

    Frodo tosses hard disk into volcano. Not very far away, a tower in Redmond crumbles as a giant bespectacled eye glaces around in terror. Outside the Gates of mordor, a troll-like figure is about to stomp on the penguin's head. When the hard drive melts, Ballmer lifts his mishapen head, takes his foot off the penguin, and shambles confusedly into the night.

    --
    Don't blame Durga. I voted for Centauri.
  35. No, you Think again! by V. · · Score: 2, Informative


    Keep reading that man page. That only comes into play if you are shredding a mount point/filesystem. Just shred the device file and you are golden.

  36. This Does Not Work on Modern Computers! by flithm · · Score: 3, Informative
    Despite what they tell you, these erasure programs do not work on drives using journalled filesystems (ie almost every drive there is these days... including you Windows users with NTFS, and Linux users with Reiser, Ext3, XFS, etc).

    For more information check out this link.

    For the lazy, here is a summary:

    Many modern operating systems such as Windows XP (NTFS), Mac OS X ( [[HFS+]] ), and GNU/Linux with a kernel version greater than 2.4 (Ext3, JFS, ReiserFS, and XFS) have the ability to use a journaling filesystem that makes complete erasure of data unlikely.

    There are several ways to securely wipe files when using journaling filesystems:

    Store data that needs to be wiped on a partition (slice, volume, or drive) that uses a non-journaling filesystem. For example, users of Windows can use a Z: drive formatted with FAT32, and users of GNU/Linux can use a partition formatted with Ext2.

    Store data that needs to be wiped on a partition that is encrypted using Hard Disk Encryption. This eliminates the need to use a secure wiping mechanism for individual files.

    Store data on a temporary partition using any journaling or non-journaling filesystem. When it is time to wipe all files, use a tool such as Eraser or Wipe to securely wipe the entire partition.

    Physically destroy the hard drive after use by melting the hard drive. (Passing a magnet over the hard drive will not work.)

    So, basically... there is no proper way of protecting yourself from undelete data recovery methods, if you use a journalled file system, aside from keeping some thermite handy!

    If you ask me, we should all be encyrpting our data partitions by now!

    1. Re:This Does Not Work on Modern Computers! by werewolf1031 · · Score: 2, Informative
      Ok, while all that sounds technically competant, I must disagree... and agree.

      Data stored on a hard disk (or floppy disk, or any other magnetic-based medium) uses the polarity of a tiny portion of the disk (eg. a "sector") to determine if that portion contains data equating to a one or a zero.

      When the write head of a HDD applies a magnetic charge to a portion of the disk, it has just enough strength to change the surface polarity to the intended bit value. If it uses too much, it'll spill over onto adjacent portions; not enough, and the polarity of the magnetically sensitive material beneath it will interfere with the intended bit value.

      This is how professional-grade data recovery labs retrieve "lost" data, because the polarity of the material "underneath" the exterior portion may be different, and thus allow retrieval of erased data.

      On the OTHER hand... it does make it really damn difficult to truly erase disk data. As the above implies, just writing over it with the HDD's normal write head, even while formatting, may not be enough to conceal what was previously written by "professional" grade retrieval methods.

      So basically: Regardless of the file format used (which doesn't affect how the HDD's read/write heads interact with the platters), use a bit of common sense and forethought when storing sensitive personal data.

      Geez, talk about the long way around. :)

    2. Re:This Does Not Work on Modern Computers! by flithm · · Score: 2, Interesting

      Well... aside from that one there's also the shred manpage which discusses this:

      CAUTION: Note that shred relies on a very important assumption: that
      the filesystem overwrites data in place. This is the traditional way
      to do things, but many modern filesystem designs do not satisfy this
      assumption. The following are examples of filesystems on which shred
      is not effective:

      * log-structured or journaled filesystems, such as those supplied with

      AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)

      I can't really find any other good info on this, but given what I know about how journaled file systems work I certainly believe this.

      Having said that, if anyone has any real information on this I'd be interested to know as well.

    3. Re:This Does Not Work on Modern Computers! by DM9290 · · Score: 2, Interesting

      When the write head of a HDD applies a magnetic charge to a portion of the disk, it has just enough strength to change the surface polarity to the intended bit value. If it uses too much, it'll spill over onto adjacent portions; not enough, and the polarity of the magnetically sensitive material beneath it will interfere with the intended bit value.

      What you are saying is true. If you only overwrite the data a single time, it is easy to determine what the previous value was.

      However secure erase tools will overwrite data up to 35 times with random data.

      This makes it much more difficult to recover the data and have confidence in what you are recovering.

      Another thing to keep in mind is that the original data was also only written barely strongly enough to record the intended bit. It isn't like the original data was burned in with a laser and only the subsequent overwrites are faint. every pass is just strong enough to record the desired bit.

      --
      No one has a right to their *own* opinion. They have a right to the TRUTH.
    4. Re:This Does Not Work on Modern Computers! by DM9290 · · Score: 3, Interesting

      Despite what they tell you, these erasure programs do not work on drives using journalled filesystems (ie almost every drive there is these days... including you Windows users with NTFS, and Linux users with Reiser, Ext3, XFS, etc).

      This is not entirely correct.

      Journaled file systems by default only use the write ahead log or "journal" for metadata changes, and not for data itself.

      This means, when you overwrite the file 35 times in place, the journal is not involved in this operation.

      When the secure delete program, then issues a DELETE, that operation is logged. Some time shortly thereafter the directory structure is updated to reflect that deletion. However, the data would have been overwritten 35 times (using the defaults in the eraser program) notwithstanding that the delete may be deferred.

      As long as the filing system allows software to bypass the write-behind disk cache this works.

      If your disk controller hardware has its own cache this may very well interfere.

      a journaling filing system makes it more difficult to hide the fact that a deleted file ever existed, but it typically will not interfere with writing data into that file.

      Additionally the article expresses concern that a journaling system may move a file to a new location on a write.

      You will want to confirm for your specific filing system, but typically this would be very very inefficient on a hard disk.

      AFAIK ext3, reiser, NTFS, BeFS (the only journaled filing systems I have much experience with) do not move files around on the partitian simply because the data within the file is modified.

      Since hard drives support random access, on a hard drive there is very little likelyhood that a superior location to store that file will be found than the original location chosen (and there is no reason to NOT use the original location). Hard drives fill up over time. The overhead in choosing a better location in very expensive.

      Someone please correct me if I am wrong.

      In fact, (with those FSs that I mentioned) unless you defragment or something, files are left in the original locations they were allocated, and any modifications occur on the same disk locations.

      Another factor to consider. The journal is typically implemented as a fixed size circular buffer, and it is overwritten frequently.

      If you want to help insure this happens soon perform the following operation.

      1: create a directoy X.
      create a 0 byte file Y inside inside directory X.
      2:
      open Y. append 1 byte.
      close Y.
      move Y to the parent directory of X.
      open Y. append 1 byte.
      move Y back inside X.
      rename Y to some random name.
      rename directory X to some random name.
      touch X
      touch Y
      copy Y to a new file Y!
      delete Y
      let Y! now be the new Y (for future iterations)
      3: repeat all steps from 2: until 3: a hundred thousand times or so.

      Do that with your disk cache turned off (or a sync operation between every step) and that will probably irradicate whatever is in the journal.

      This loop causes a ton of meta data changes which must be written into a write ahead log. Moving and renaming the file may or may not be considered a metadata change depending on the FS, it may simply be a data change to data in a directory (I believe this is the case in ext3; but if I recall, in BeFS file renaming and moving is a metadata change.

      Finally.. since the journal doesn't track data itself, the only thing it may contain are filenames, paths and perhaps filesizes. Your data is not there.

      in any event, while there is merit to the concerns expressed in the article, they are somewhat overstated.

      If you ask me, we should all be encyrpting our data partitions by now!

      I agree with you there.
      Storing plain text is absurd.

      --
      No one has a right to their *own* opinion. They have a right to the TRUTH.
  37. Data loss? by mageofchrisz · · Score: 2, Funny

    Perhaps Microsoft should include an option, like 'Prepare this computer for resale,' which utterly destroys all data.

    Start > Run > explorer

    Consider data loss guaranteed

  38. Update on This by flithm · · Score: 3, Insightful

    Just wanted to update and say that, you can safely erase an entire hard drive (even with a journalled filesystem) if you unmount it, and wipe it (ie side step the filesystem driver). This is pretty easy to do in Linux, not sure about Windows... although I know one good method would be to use the hard drive manuacturers low level formatter (running it 3 or 4 times should be enough).

    But once again, be wary of any file erasure programs like the one mentioned by the grandparent post. You need to take care that your usage of them is not in vain!

  39. Only disks - Attack of the clueless accountant by dbIII · · Score: 2, Funny
    I once watched a clueless accountant completely trash a not paticularly old server with a hammer in case financially sensitive information could be gleaned from its CPU, RAM, side panels, keyboard, monitor ot terminals. In hindsight, the stuff on the disks would probably be found interesting in a crimianl court, so not understanding how computers work he was destroying everything he thought could potentially be evidence.

    Either that, or he really hated the thing and wanted to destroy it, or hated the techno geeks that wanted to take it home.

  40. Prepare this computer for resale by rodgster · · Score: 3, Insightful

    Sledgehammer followed by a bonfire or wood burning stove ought to do it. Ever wonder why there are no harddrives at government auctions?

    --
    Who will guard the guards?