Slashdot Mirror


New Tool Hides Data In Plain Sight On HDDs

Trailrunner7 writes "A group of researchers has developed a new application that can hide sensitive data on a hard drive without encrypting it or leaving any obvious signs that the data is present. The new steganography system relies on the old principle of hiding valuables in plain sight. Developed by a group of academic researchers in the US and Pakistan, the system can be used to embed secret data in existing structures on a given HDD by taking advantage of the way file systems are designed and implemented. The software does this by breaking a file to be hidden into a number of fragments and placing the individual pieces in clusters scattered around the hard drive."

136 comments

  1. scandisk will just remove this by Anonymous Coward · · Score: 0

    scandisk will just remove this

    1. Re:scandisk will just remove this by X0563511 · · Score: 1

      Unfortunately it won't remove your comment.

      Scandisk hasn't been used since.... February 2000.

      Snark aside, yea, this does sound "dangerous" - it might hide it in plain sight, but it also fixes it in a very fragile state.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    2. Re:scandisk will just remove this by xOneca · · Score: 1
      Scandisk doesn't do the job, but a defragmenter tool.

      The software does this by breaking a file to be hidden into a number of fragments and placing the individual pieces in clusters scattered around the hard drive.

      Have they re-invented FAT file system?

  2. Sounds familiar by xs650 · · Score: 0

    "The software does this by breaking a file to be hidden into a number of fragments and placing the individual pieces in clusters scattered around the hard drive."

    NTFS has been doing that for years.

    1. Re:Sounds familiar by Anonymous Coward · · Score: 5, Funny

      yeah, but unlike NTFS, this is supposed to allow you to read that data in the future

  3. Re:Defrag and die by megla · · Score: 2

    They hide data by splitting it into small pieces, writing it to disk in random order and marking that sector empty. Sounds like a disaster to me, all you need to do is to use the disk, just defrag it and your hidden data is gone.

    Yeah that was my thought too. Although you could consider defrag to be a secure destruct mechanism... ;)

  4. My first thought... by Anonymous Coward · · Score: 0

    When I read the headline, I immediately thought of putting sticky-notes on HDDs.

  5. 20 MB in 160 GB ?! by lomedhi · · Score: 1

    The authors estimate that it would be feasible to hide about 20 MB of data on a typical 160 GB HDD.

    Wow, isn't that useful.

    --
    Did you say "insightful" or "inciteful"?
    1. Re:20 MB in 160 GB ?! by axx · · Score: 4, Insightful

      I thought the same thing at first, but in all fairness 20 MB of critical data can go a long way.

      Hiding stuff doesn't have to mean hiding video. A .pdf file can be all you want to hide in some cases, and you might want to do so without attracting attention with cryptography.

      Let's just say this could have its uses.

      Especially since I don't know of another steganography FS that is being maintained ? (RubberhoseFS was a nice idea)

      --
      No wit here.
    2. Re:20 MB in 160 GB ?! by bytethese · · Score: 2

      Yes because text files and VGA/SVGA/XGA quality images are large files sizes...

    3. Re:20 MB in 160 GB ?! by MightyYar · · Score: 3, Interesting

      Wow, isn't that useful.

      It rather depends on what is in that 20MB. How many diplomatic cables would fit into 20MB? Or 200MB, since 2TB drives are commodities now.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    4. Re:20 MB in 160 GB ?! by Random2 · · Score: 1

      What type of text files do you write that take up 20 MB?

      --
      "Our goal each year should be to increase the number of goals we set for ourselves!"
    5. Re:20 MB in 160 GB ?! by lomedhi · · Score: 1

      Yes, I suppose you're right; there are definitely use cases in that range. And most hard drives are a lot bigger than that these days anyway.

      --
      Did you say "insightful" or "inciteful"?
    6. Re:20 MB in 160 GB ?! by lomedhi · · Score: 4, Informative

      Of course; valid point taken. Knee-jerk reaction on my part.

      --
      Did you say "insightful" or "inciteful"?
    7. Re:20 MB in 160 GB ?! by Abstrackt · · Score: 1

      What type of text files do you write that take up 20 MB?

      Directory listing of his porn stash.

      --
      They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance. - Terry Pratchett
    8. Re:20 MB in 160 GB ?! by BuckaBooBob · · Score: 1

      There are a million ways to do this... You can hide data in photo's.. Videos... MP3's... just about any innocent file can have a hidden payload in it if you know what to look for.. The big key is that you just can't have a hunt/find/decrypt executable on that pc..

      --
      Who needs WiFi when we can have Packet Over Sheep! http://datacomm.org/PoS-InternetDraft.txt
    9. Re:20 MB in 160 GB ?! by Dunbal · · Score: 1, Funny

      I think "Hello World" in Microsoft Word should do it, no?

      --
      Seven puppies were harmed during the making of this post.
    10. Re:20 MB in 160 GB ?! by Dishevel · · Score: 4, Funny

      Wow.
      You took criticism constructively and then admitted you were wrong and moved on with your life?
      You do not belong here. Move along. :)

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    11. Re:20 MB in 160 GB ?! by lomedhi · · Score: 1

      Those MetaFilter people must be starting to rub off on me ....

      --
      Did you say "insightful" or "inciteful"?
    12. Re:20 MB in 160 GB ?! by Anonymous Coward · · Score: 0

      http://iq.org/~proff/rubberhose.org/

      Written by Julian Assange, [...]

      Is that the Julian Assange?

    13. Re:20 MB in 160 GB ?! by MasterPatricko · · Score: 3, Informative

      Yes. He did actually have a productive life as a white-hat hacker (he was one of the first famous Australian hackers; he was arrested and given a slap on the wrist at age 20 for breaking into telecommunications networks) and FOSS developer before becoming a media celebrity.

      Assange has actually contributed many small interesting projects; IIRC he wrote nntpcache & surfraw, as well as rubberhose ...

      --
      I'd tell a UDP joke, but you may not get it. I'd tell a TCP joke, but I'd have to keep repeating it until you got it.
    14. Re:20 MB in 160 GB ?! by Electricity+Likes+Me · · Score: 1

      This is probably key really - at the end of the day it can't "look" like you've hidden something, so you'd be just as well off using a hidden partition with something like Truecrypt, since you'll have to keep the decoding program on a portable key of some kind.

    15. Re:20 MB in 160 GB ?! by MichaelSmith · · Score: 1

      It could be the software and key to turn a different block of random data into actual data.

    16. Re:20 MB in 160 GB ?! by lomedhi · · Score: 1

      Another good point.

      --
      Did you say "insightful" or "inciteful"?
    17. Re:20 MB in 160 GB ?! by RockDoctor · · Score: 1

      Wow, isn't that useful.

      As you've later agreed ... 20MB is actually reasonably useful. The problem with this techniques is that you're going to need in the order of 160GB of non-infringing data to hide the 20MB in. And if you're wanting to do this routinely, you're going to need a lot more, otherwise it's going to start to look suspicious. Lots of Jason Bourne lookalikes crossing your borders, all carrying laptops with the same collection of movies on them ... peculiar. Attention-attracting.

      Actually ... a ripped collection of movies ... as long as they were definitely legal (so you'd probably need to be using in-house training videos of mind-exploding tedium ; Hollywood movies could get annoying questions asked, and you don't want to attract attention.

      Hmmm. There is a problem there, but thinking a bit more about it, you could probably generate convincing data fairly easily to do your steganography with. And it wouldn't be too difficult to come up with a scenario where the hard drive has multiple partitions for data management, again without attracting attention.

      I suppose I'd better go and RTFA now.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
  6. Re:Steganography? by Jeremiah+Cornelius · · Score: 1

    US and Pakistan.

    Together. CIA and ISI?

    Here's your backdoor Trojan from hell.

    --
    "Flyin' in just a sweet place,
    Never been known to fail..."
  7. Re:Steganography? by Anonymous Coward · · Score: 0

    Congratulations, you've failed to read the first two sentences of the article summary! :P

  8. bollocks by Hazel+Bergeron · · Score: 2

    Just because you're encoding the information in the fragmentation patterns of the underlying filesystem it doesn't mean you're not engaging in encryption. The encryption is the key input to the algorithm to identify how to turn that apparently random pattern back into plaintext - otherwise we'd be able to say, "OK, let's check he's not using this method," without any secrets.

    tl;dr Steganography is useless without encryption.

    1. Re:bollocks by X0563511 · · Score: 2

      The point of Steganography is not to make it hard to find the information. It's point is to avoid even being looked for. That's what the whole "hide in plain sight" bit means, you know.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    2. Re:bollocks by Hazel+Bergeron · · Score: 2

      That reasoning has always been specious. It's trivial to compile a list of published steganographic methods and engineer some check for them. The method must involve some form of key and encryption to make the check unlikely to succeed.

    3. Re:bollocks by vlm · · Score: 1

      That reasoning has always been specious. It's trivial to compile a list of published steganographic methods and engineer some check for them. The method must involve some form of key and encryption to make the check unlikely to succeed.

      The way the check might fail is by finding random weirdness. Right off the top of my head, a graph of file length vs frags is probably going to be distorted by this storage mechanism... Also a graph of filesystem age or filesystem size vs frag level is probably going to show this mechanism as an outlier.

      Since fragmentation is not random, hiding anything using it is going to be very tricky... Plenty of room for honest error and/or snake oil and/or back doors.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    4. Re:bollocks by Anonymous Coward · · Score: 0

      Sorta how you just called that guy an a**hole without using the word. Classic example.

    5. Re:bollocks by Anonymous Coward · · Score: 0

      Anything is useless without encryption, using that argument.

      Everything is encoded somehow, keyword, encoded, because that is what this is.
      A file format doesn't need to be deliberately encrypted, just encoded in such a way that it optimizes space usage.
      If that means it is unreadable to human eyes, then so be it. But that just makes it compression rather than encryption.

      A QR code isn't encryption. It is compression designed to take advantage of a wide range of cameras as efficiently as possible.
      It means it is unreadable to humans. (unless they have memorised the QR algo.)
      There are also versions that use color ranges rather than B/W to enable significantly higher storage.
      But these are simply compression methods.

      Although, in saying all that, the act of hiding information in chunks all over a hard drive is deliberately trying to hide stuff, which is a form of encryption.

      I think we need to come up with a word that describes the middle-ground of encryption and compression. Encression? Compryction?
      Disregard, I'm in a bit of a weird mood due to pain killers.

    6. Re:bollocks by mlts · · Score: 1

      Encryption is done beforehand for three reasons:

      1: The hidden data is essentially static, with no discernible patterns.

      2: If the stegoed data is located, it cannot be used as plain text.

      3: Plausible deniability. If a stego detector finds random numbers, that is one thing, versus plaintext as another.

      Don't forget -- a lot of encrypted files have a pattern to them, such as PGP, ZIP, etc. One will need to find a utility that does to files what TrueCrypt does to partitions and has a complete unreadable structure. This is harder than it sounds, because almost all file encryption programs have some type of header in their encrypted output.

    7. Re:bollocks by kesuki · · Score: 1

      i think the real life analogue of this software is a pair of paper scissors and hiding fragments in unmarked folders. even if you know what the computer is about to do, finding all the 'misplaced' folders is something likely to take several hours per incident. if this technique was used to protect a whole lot of folders it might not be reversible at any level.

    8. Re:bollocks by Anonymous Coward · · Score: 0

      *Compressed* files like zip often have a pattern; they tend to have some kind of standard header containing the info needed to decompress the rest. Identifying them isn't any more difficult than identifying file formats in general.

      Encrypted files look like noise; they don't have extra readable structured information attached, because the person/program decoding them are expected to know the key and other relevant info on their own. That's kind of the point of encryption, after all. Some implementations may have additional identifiers attached for convenience, but that's generally just going to be a "[format] cryptotext starts here" kind of thing that can be stripped out.

    9. Re:bollocks by Anonymous Coward · · Score: 0

      That's why we use the unpublished methods, uh-duhhh!

  9. illegal by Anonymous Coward · · Score: 0

    Steganography will probably become illegal exactly when encryption becomes illegal.

  10. Re:Defrag and die by ColdWetDog · · Score: 2

    Yeah that was my thought too. Although you could consider defrag to be a secure destruct mechanism... ;)

    That's the beauty of this sort of thing. Not for storing your routine Porn^HDocuments, but for really sensitive stuff that can be destroyed quickly and 'innocently'.

    "Well, sir, the computer was running a bit slow, so I defragged it yesterday. Is that a problem?"

    --
    Faster! Faster! Faster would be better!
  11. hide it in spam, e-books, etc.... by Anonymous Coward · · Score: 0

    It may be best to hid the steganography-generated content in a bunch of SPAM emails, in the SPAM folder of whatever email program you use...

    Kind of like:
    http://www.spammimic.com/explain.shtml

    It's the first thing most law-enforcement people would delete, or ignore...

  12. Security through obscurity by Anonymous Coward · · Score: 0

    Hiding things in plain sight is extremely useful until you know where it is. Then the game is up. Funny thing is, now that the method is out there for everyone to see, one could hardly argue that such data was hidden at all.

  13. Re:Steganography? by alostpacket · · Score: 1

    But how many words per minute can it type?

    --
    PocketPermissions Android Permission Guide
  14. Re:Defrag and die by Random2 · · Score: 1

    Yes, but it would require the user to know to actually defrag the hard drive.

    Also, that's even better than you might think, makes obliterating the data even easier if you suspect it'll be found, or as a way to ensure it's destroyed. As long as you're not writing to the volatile part of the HD, you'll be fine for normal operation.

    --
    "Our goal each year should be to increase the number of goals we set for ourselves!"
  15. All sorts of uses by Hallmarc · · Score: 2

    If it can work in the filesystem, it can work theoretically at the network packet level...

    1. Re:All sorts of uses by MacTenchi · · Score: 2

      Except that any router passing your packets might choose to re-fragment or recombine your packets, destroying your message.

    2. Re:All sorts of uses by sgt+scrub · · Score: 1

      in addition to MacTenchi's comment.. out of order fragments will get dropped by any good router or ips so you can't go that way and duplicate fragments are discarded by every decent firewall. now udp packets echo'd from client to random client until they need to be re-assembled is another story. the greater the ratio of client to packets you have the greater the difficulty for someone to re assemble it.

      --
      Having to work for a living is the root of all evil.
  16. Re:Defrag and die by Anonymous Coward · · Score: 0

    Or require a FS that fragments

  17. Purely academic by gweihir · · Score: 3, Interesting

    You get very little data to store, but this looks like it will be secure and, for a change, really hard or impossible to detect.

    Of course a dead giveaway is the access software needed, so this works only for hiding data that the holder cannot access. That and the low data volume (20MB in 160GB are given as example) limits the usefulness to a nice but very academic idea.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Purely academic by Anonymous Coward · · Score: 0

      Of course a dead giveaway is the access software needed, so this works only for hiding data that the holder cannot access.

      If you're afraid to store it on an SD card, you can launch Java-based apps with nothing more than a command an a URL. It might take some care to write the software to remove all traces of itself, but it's certainly possible.

    2. Re:Purely academic by gweihir · · Score: 1

      If accessing that java app is not suspicious, then store your data in it. Otherwise you are handing probable cause right to the other side. Also, what makes you think the app, if not under your control, is trustworthy? Amateur.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    3. Re:Purely academic by jmorris42 · · Score: 1

      > Of course a dead giveaway is the access software needed, so this works
      > only for hiding data that the holder cannot access.

      Lots of use cases for that. You encode a hard drive at your embassy and send it back with an unsuspecting minion. When they get home your people there do a 'routine check' on the laptop and extract the too hot for ordinary channels memo, again with the user totally unsuspecting that he was a courier.

      Human rights group in hellhole country wants to get a release out? Find some tourist willing to be the carrier, inject the data onto their laptop and tell them to quietly contact the group's main office back in the first world when they get home.

      --
      Democrat delenda est
    4. Re:Purely academic by gweihir · · Score: 1

      Completely bogus.

      Embassies have diplomatic couriers that are explicitly allowed to carry encrypted data and make regular travels. Embassies also typically have very secure encrypted communications.

      "Human rights group.": The tourist will likely be an informer or watched and needs to be extremely careful not to be entrapped. This scenario is completely unrealistic. Also, if the "Human rights group" has the software or even the paper, then they already have channels that actually work. If the tourist's laptop is searched before and after the message is placed, the change in fragmentation pattern will be glaringly obvious.

      Any more artificial examples?

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    5. Re:Purely academic by jonadab · · Score: 1

      Actually, the real problem is that normal usage of the drive would typically change where some files are stored and how they are fragmented. If you used it on your main system drive (i.e., the filesystem whereupon the OS is installed), merely booting up your operating system would very likely make some of your hidden data irretrievable.

      (There's also the small matter of FAT32 no longer being terribly useful on hard drives, but in principle the method would be applicable to other filesystems, though the implementation details would be significantly different.)

      Besides that, the scheme is unnecessarily complicated. There are easier ways to hide encrypted data in plain sight and plausibly deny its significance. I mean, seriously, have you never heard of a log file or a browser cache? Heck, use the seconds fields in the timestamps in the Received: headers in a big fat folder full of old email. It ain't that hard.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    6. Re:Purely academic by Em+Adespoton · · Score: 2

      You get very little data to store, but this looks like it will be secure and, for a change, really hard or impossible to detect.

      Of course a dead giveaway is the access software needed, so this works only for hiding data that the holder cannot access. That and the low data volume (20MB in 160GB are given as example) limits the usefulness to a nice but very academic idea.

      I agree... and this made me think: a good method I saw for steganography uses forums and blogs to embed the data in public site inside other documents.

      However, why not do something like store the data in a Fake Antivirus program, or even web cookies forged for various sites? Both give you true plausible deniability, as you can deny you ever wanted the data on your machine in the first place... and with the second, you can make the data expire, and even have a remote website that'll automatically reconstitute the data for you given the appropriate key. The data is hidden this way based on the general uselessness of the data as it normally exists, and in its fragmentation (since that data is usually written to disk by a bunch of third parties). Even if someone knew about this method, it would be hard to detect, as the data is hiding in amongst a bunch of constantly changing noise.

    7. Re:Purely academic by Em+Adespoton · · Score: 1

      2nd thought: you can even hide the data on OTHER people's computers using this method, assuming you have access to a few domain names and web servers. You could also initiate a remote expiry/rewrite of key cookies, so the data can be remotely revoked, assuming the person visits somewhere that'll reset the cookie.

      You could even overwrite common cookies (store the data in ad cookies, and then usually run ad blocking software). To erase, you disable your ad blocking software, and the ads wipe the data for you :)

    8. Re:Purely academic by Jane+Q.+Public · · Score: 1

      You beat me to it. It seems to me that since slack space is not protected by either the FS or the OS, it would be vulnerable to everyday use of the drive.

    9. Re:Purely academic by moonbender · · Score: 1

      How would the change in the fragmentation pattern be glaringly obvious? I don't think they're going to create a complete image of every hard driver entering or leaving the country. Or the carrier might just bring a drive bought inside the country, etc etc.

      I agree that it's largely artificial, though; with capacities in the sub-gigabyte range, transmitting the data via the internet or a cellular link is going to be much easier than physically carrying around drives. Most places that have tourists going in also have internet access that, while it might be censored, is easily "free enough" to anonymously get dozens of megabytes outside the country. There are notable exceptions, though; North Korea has no public internet access, and only a handful of tourists who get their cell phones confiscated upon entry. Some people did manage to get a digital camera into (and back out of) the country, though. Hiding stuff on a suitably large SD card in plain sight among a couple thousand jpegs could be useful, mostly because that means you probably will get easily out of the country even if you're caught (sans camera+sd card).

      --
      Switch back to Slashdot's D1 system.
    10. Re:Purely academic by gweihir · · Score: 1

      The change is of course only obvious if they are looking for it. But they do not need the whole disk, just the FAT and that is far, far smaller and there such a change is glaringly obvious.

      Anyways, I doubt anybody is really worried about preventing a few megabytes from being smuggled. There are a lot of ways to do that and the threat represented by this is rather small.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  18. Plausible deniability by aylons · · Score: 5, Insightful

    Doesn't TrueCrypt's plausible deniability get the same effect without depending on a loose file system hack?

    --
    This comment may contain speech figures. Reader discretion is advised.
    1. Re:Plausible deniability by gnapster · · Score: 2

      That might be part of it. However, the main aspect of plausible deniability for TrueCrypt is that the blob of encrypted data may hold two volumes, each accessed by a different passphrase. Then, I can have the software installed on my computer, and it is easy to see that I am probably using the software for hiding data. But it is impossible to tell whether I am only using one encrypted volume, or two. I can deny that I have created a passphrase for the second one, and there is no way to tell how much of the blob is storing information.

      With this strategy, the presence of the software will probably remove any hope you had for plausible deniability. Not so with TrueCrypt.

    2. Re:Plausible deniability by Anonymous Coward · · Score: 0

      Let's not forget you have to prove there is actually a Truecrypt volume on the drive. Is that ~abacad234.tmp file really a temporary file or truecrypt volume ? I don't know about you, but my Truecrypt volumes aren't labeled Truecrypt.tc on my harddrive.

    3. Re:Plausible deniability by Chemisor · · Score: 1

      Deniability gets less and less plausible every time you get hit with a $5 wrench.

    4. Re:Plausible deniability by Anonymous Coward · · Score: 0

      But it is impossible to tell whether I am only using one encrypted volume, or two. I can deny that I have created a passphrase for the second one, and there is no way to tell how much of the blob is storing information..

      Yes, you can deny having created a passphrase for a second one, but somehow I see a $5 wrench whenever someone promotes plausible deniability. If someone is that insistent on finding data hidden with steganography that plausible deniability comes into consideration, I'm not really sure it is possible to convince them that you don't have another partition...

    5. Re:Plausible deniability by Anonymous Coward · · Score: 0

      You've conflated plausible deniability with flat refusal. The whole point of PLAUSIBLE deniability is that people will most likely BELIEVE you when you say you have nothing to hide. In other words, you're hoping they won't see a reason to use the wrench.

    6. Re:Plausible deniability by fatphil · · Score: 1

      The guys who are using two will probably give up the information they were trying to keep secret, and if so possibly survive.

      The guys who are only using one will not survive.

      So there's no incentive for the latter set to use it at all.

      *Everything* about using TrueCrypt says "keep beating me with the rubber hose".

      --
      Also FatPhil on SoylentNews, id 863
    7. Re:Plausible deniability by Anonymous Coward · · Score: 0

      Unfortunately, most governments will just lock you up until you fess up the second passphrase. If you don't have one, you're fucked.

    8. Re:Plausible deniability by dkf · · Score: 1

      You've conflated plausible deniability with flat refusal. The whole point of PLAUSIBLE deniability is that people will most likely BELIEVE you when you say you have nothing to hide. In other words, you're hoping they won't see a reason to use the wrench.

      But if the questioners think you've got a truecrypt volume, they'll just keep on destroying parts of you body until either you give them multiple passwords that work and give them the data they're looking for, or you're dead (and buried in an unmarked grave). Using truecrypt is itself suspicious, and anyone dumb enough to think that a technical solution will get you out of this is totally missing what would happen in reality. Or are you one of these idiots that thinks their data is more important than their life and health?

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    9. Re:Plausible deniability by Urkki · · Score: 1

      Deniability gets less and less plausible every time you get hit with a $5 wrench.

      No, the deniability gets more and more plausible every time you get hit with the wrench and still just keep begging for mercy. It's just that it gets harder and harder too with every impact. But I'm sure that's what you actually meant, so this is just nitpicking.

      Then the question becomes: Will they keep hitting you with the wrench until you die just in case, even if they start to believe you're telling the truth?

      And then: If you're still alive when they're through with using the wrench, are they going to bury the evidence (that means you), move to more effective and probably even less pleasant information extraction methods, or (yeah, right) just let you go?

    10. Re:Plausible deniability by Bucky24 · · Score: 1

      Your point is valid and correct but I think they were more talking about the software for decrypting, rather than the data itself.

      --
      All the world's a CPU, and all the men and women merely AI agents
    11. Re:Plausible deniability by Anonymous Coward · · Score: 0

      Deniability gets less and less plausible every time you get hit with a $5 wrench.

      The opposite is true. The Problem is determining the upper bound of the number of hits.

  19. Thar be dragons! by vlm · · Score: 2

    Moreover, the channel provides two-fold plausible deniability so that an investigator without the key cannot prove the presence of hidden information,"

    So what encryption scheme are they using before storing the data? I didn't find it in the article. Hopefully not something as dumb as XOR using the "key" or using the key as a step size when encoding or something like that.

    Unless they encrypt the data before encoding the fragmentation,a glance at the frag pattern will show a distinct and obvious pattern based on the stored data. If the data is UTF-8 text using non-ascii glyphs, its gonna be pretty obvious when every other byte is a UTF-8 shift header thingy. If its plain ole ascii text its going to be pretty obvious the 8th bit is almost always 0. If the data is semi-packetized like video frames, its gonna be pretty obvious. If the data is stored emails with semi-known plaintext headers, its gonna be pretty obvious. Theres only so many ways to encode 1 and 0 into the frag pattern so playing games like encoding it backwards isn't going to help.

    I'm guessing its not going to be plausibly deniable at all... The other part of the deniability problem is how to deny the presence of the decryption tools in the filesystem, or in unused blocks of the FS. Hmm. You could delete the tools, and then defrag the hard drive to sorta-wipe it. Oh wait...

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  20. Re:Defrag and die by PPH · · Score: 1

    Correct me if I'm wrong (I often am about Windows) but aren't there several types of sectors reserved for system uses and not touched by defrag? I know I've seen the defrag graphic when fixing some friends borked up PC and seen something like this.

    All that would have to be done is to mark the hidden data as system sectors not to be messed with by defrag. Of course, knowing this, it would make a search for said data much easier.

    --
    Have gnu, will travel.
  21. Re:Defrag and die by mikejuk · · Score: 1

    And Windows 7 does a defrag automatically! See : http://www.i-programmer.info/news/149-security/2352-hiding-data-in-disk-fragmentation.html for some of the problems.

  22. Great... by Anonymous Coward · · Score: 0

    And I just deleted my porn folder...

  23. How? by gmuslera · · Score: 1

    I the wonder how password they could do is this in plain swordfish sight

    1. Re:How? by werewolf1031 · · Score: 1

      My kingdom for a mod point...

  24. Re:Steganography? by Abstrackt · · Score: 1

    Based on TFA, and even TFS, it would be more accurate to say they've found a novel way to use the wheel.

    --
    They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance. - Terry Pratchett
  25. Re:Steganography? by Anonymous Coward · · Score: 0

    None. Counting typing speed is haram.

  26. I doubt it will work by PPH · · Score: 3, Funny

    "A group of researchers I has developed a new think application that can hide this sensitive data is on a hard drive a without encrypting it bunch or leaving any of obvious signs that the data is crap present."

    --
    Have gnu, will travel.
    1. Re:I doubt it will work by I'm+not+really+here · · Score: 1

      come on... Maybe Everyone is Exceptionally stupid, Truly... At least Try to Make it less Obvious. Each Secret system has it's own way of passing data... I can think of 8 off the top of my head, but none are that ridiculously easy to spot. Perhaps More effort is needed to create a good example? even this one is pathetic, but it's more realistic than what you are showing, and more accurately to the point (somewhat).

      --
      Before commenting on the Bible, please read it first
    2. Re:I doubt it will work by Anonymous Coward · · Score: 0

      Why not Eat At Joe's?

    3. Re:I doubt it will work by Anonymous Coward · · Score: 0

      No, no, no...

      Take Stenography using an image file as an example. You encode the data you want to hide in the low order bits of the picture information. Working with 32-bits, no one will notice some seemingly randomness in these bits. So someone is looking for your information will only see a picture of a beautiful lake.

      If you know where to look you may decide there is something there, but unless you know the coding you can't figure out what it is.

  27. working implementation: by circletimessquare · · Score: 1

    the data isn't even written to sectors marked empty, the data is written to empty air!

    http://blog.jitbit.com/2011/04/chinese-magic-drive.html

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  28. Slowpokes by Anonymous Coward · · Score: 0

    DOS sez:

    copy file1+file2 file3

    NOW I HID FILE2 IN FILE1! THIS IS SUPER BED TIME READING!

  29. Re:Steganography? by pclminion · · Score: 4, Insightful

    What sort of thought process leads to a stupid comment like this? Somebody creates a new plastic: "Congratulations, you've reinvented polymerization!" Somebody makes a better and faster computer chip: "Congratulations, you've reinvented computing!"

    Everything is built on something else. For most of us, that's obvious. I guess not for some. For you, new ideas must leap fully formed from a different universe accompanied by a huge explosion in order to be interesting, I guess.

  30. Ephemeral but effective by NicknamesAreStupid · · Score: 1

    There are a lot of things that someone might want to hide for a short while. It could work well on networks, too, using a predictive coding scheme like Trellis. The message would be almost impossible to detect. On the other hand, the sender and receiver need to be intimately involved, and in there lies the rub.

  31. Re:Defrag and die by pclminion · · Score: 3, Informative

    They hide data by splitting it into small pieces, writing it to disk in random order and marking that sector empty. Sounds like a disaster to me, all you need to do is to use the disk, just defrag it and your hidden data is gone.

    This is called fragility, and depending on context, is a desired feature.

  32. Re:Defrag and don't read the article by b4dc0d3r · · Score: 3, Informative

    Know how I know you did not read the article? This method is rearranging existing data so the FAT itself holds the data. This is not including the data at the end of a cluster, or putting it in empty clusters.

    If you want to encode a 0, put the first block at an even numbered sector. If you want to encode a 1, put it at an odd numbered sector. There are other ways to do it, but that's just one example.

    There is no data on the drive itself to analyze, it's all in the fragmentation of the FAT.

  33. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  34. Only 20MB by Arlet · · Score: 1

    It's easier to put your sensitive data on a micro SD card, and hide that somewhere.

    1. Re:Only 20MB by Anonymous Coward · · Score: 0

      Flash cards aren't secure unless encrypted (in software), and your "unfindable" hiding place is likely to be about #3 on a list of "places people hide stuff from us".

    2. Re:Only 20MB by Neil+Boekend · · Score: 1

      I hide all my sensitive data in a burning furnace. They'll never find it there!

      --
      Well, I might have a way, but it only works on a semi spherical planet in a vacuum.
    3. Re:Only 20MB by peawormsworth · · Score: 1

      It's easier to put your sensitive data on a micro SD card, and hide that somewhere.

      I once setup a computer on an SD card, but also setup a partition to be used as memory for my digital camera. In this way I could put the memory into my SD camera and the camera would operate in all normal ways if searched. But I could also remove the memory from my camera and put it into a computer. Furthermore, I didn't just put data on the SD card. I put the entire operating system on it. So I could essentially travel anywhere with only my camera in hand and when I arrive at my destination, I could put the SD card in any computer and log into my the computer just like it was my own.

      So my "hiding" was not really hiding the content, but rather hiding the media in plain site by exploiting the SD memory card for 2 uses. By making one usage active, easy to test and verify the secondary usage is unlikely to be noticed. Especially when I wouldn't even need to carry a computer with me.

      To further protect the operating system during transit and protect information when the media is inevitably lost or not needed, I encrypted the computer partition using Luks as well.

      Now this doesn't provide true security against the discovery of an encrypted partition completely if the camera data stick is removed and searched separately by a computer. But it is just one layer of protection against unwanted detect of the existence of encrypted data (or even whole operating system) in the first place.

      As mentioned, the traveler using this technique wouldn't even have to carry a computer with them. Just keep the SD in the camera and that is all you travel with. Then insert it into a computer you buy, rent or borrow at the destination. I took the SD card into a Best Buy and booted it up on about 80% of their current models without issue. The main issue with the remaining 20% was the inability to boot off SD memory sticks. But for the most part you should expect newer computers to totally support this.

      However, don't try any of this with Windows operating systems or any others that attempt to tie the operating system to the motherboard. IMO: An immoral and possibly illegal contract request. But anyhow, windows specifically prohibits booting your operating system on multiple computers and I'm unsure of their current stance on SD installations. I'm also quiet certain you would have to pay extra in order to have the entire operating system encrypted... if windows does even offer this ability at all... I don't know... I don't use windows because it is an antiquated operating system tied up in legal EULA issues that attempts to protect profit at the expense of stifled innovation. Anyhow... point is, use Linux for this and similar experiments. I used Ubuntu and it was easy to setup exactly what I described.

  35. Would it make more sense to hide the Hard Drive? by DanielRavenNest · · Score: 1

    For example, place the hard drive in the shell of a real but non functional printer. If it doesn't need to be connected, alternately hollow out a book and hide it in there, etc.

  36. Re:Defrag and die by Anonymous Coward · · Score: 0

    You are wrong.

    The system sectors are actual files. Files are marked as DO NOT MOVE because of various things that happens with these files. Empty space cannot be marked as unmoveable.

  37. Re:Steganography? by Anonymous Coward · · Score: 0

    ... wtf, all they did was reverse the process of defragmentation. THAT'S BEEN DONE ALREADY, FOR ONE THING. calling it steganography is stupid... the file system will have to take all these scattered clusters into account in order to avoid over writing them. this is only 'hiding' the data if you have a drive plate with no file system intact and have to scrub it for the data. nobody is ever in that situation. your drive at home will have the file system intact, and there will be headers linking all these 'scattered' segments together. puh fucking LEASE. it was worse than reinventing the wheel, it doesn't even sound good. 'wheel' sounds good!

  38. Re:Steganography? by Anonymous Coward · · Score: 0

    Because there is no "invention" here. Chopping up data into pieces and scattering them around a drive has been a known technique for nearly 30 years. There is no invention involved for "finding other cracks for the pieces to fit into".

    In addition, steganography and similar technologies are very poor choice for hiding data, because detecting the hidden data can be easily automated.

  39. Re:Intimately Involved by TaoPhoenix · · Score: 1

    Steganographically encode info in trolls!

    Did you exactly document the shades of red in Goatse? How do you know those aren't orange-shifted to encode data?

    Talk about in plain sight! Yikes!

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  40. Re:Defrag and die by Morgaine · · Score: 5, Informative

    They hide data by splitting it into small pieces, writing it to disk in random order and marking that sector empty.

    No they do not. You just totally invented that.

    I know this is Slashdot and not reading TFA is a rite of passage, but at least don't try to "inform" when you have no idea about something.

    None of the secret data is written to disk at all. As the researchers explain clearly (they're quoted in TFA), the data is encoded in the pattern of cluster allocations used for storing the non-hidden files already present on the drive. They even describe the RLE-based algorithm used for cluster-chain encoding. The size of existing files remains the same, the amount of disk space used and unused in the filestore remains the same, and the contents of all the files remain the same after this process.

    So your explanation couldn't be more wrong. And the moderators who gave you a +5 Informative failed to understand the method as well.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
  41. Re:Defrag and die by ThatMegathronDude · · Score: 1

    Just write to /dev/null and save yourself the trouble.

  42. Re:Steganography? by EdIII · · Score: 1

    I can certainly see how his comment could come off as sarcastic and acerbic.

    However, he does have a point. There is nothing new about the approach. They even claim new, but from reading the article, this is not new.

    I see no reason to make a comparison between new and old stenographic methods. At most splitting the chunks against multiple files is a different implementation of the exact same idea. Nothing Earth shattering, and I can see a couple of issues already.

    If it is split across multiple files and not encrypted, then technically the safety of your data is only as safe as how limited the ability of an attacker is to perform analysis and reconstruction. There are companies out there that make tens of thousands of dollars doing just that.

    If my file is split across 349 files what happens when file# 235 is modified or deleted? Do they have a system wide monitoring process? Redundant processes similar to RAID to accept small degradations like that? Just how inefficient is the process then? Like RAID 5 do you need to lose an additional 20% of total storage space on a 4 drive implementation?

    I can kind of see the "Congratulations" statement here. It is stenographic, just not radically different than other methods, and ostensibly with some serious caveats.

    I think I will stick with TrueCrypt for now which actually encrypts my data is reliant upon a simple and hard to defeat denial mechanism. That being, "But I gave you the password. You can see the files".

  43. Security 101 by SuperTechnoNerd · · Score: 1

    Security through obscurity never works, nor should it be tried.

    1. Re:Security 101 by knappe+duivel · · Score: 1

      Security through obscurity can work, but you (or I) won't know about it when it does.

  44. Re:Steganography? by Anonymous Coward · · Score: 0

    Not very many, but it's amazing to watch it using that spiky tail at all...

  45. yeah but no but by Anonymous Coward · · Score: 0

    Just worth pointing out that this will be blindingly obvious to anybody that wants to look for hidden data. Plus most operating systems screw around with this all the time... won't work.. stupid idea... go back to truecrypt

  46. Re:Steganography? by Anonymous Coward · · Score: 0

    stenography is the word you are looking for?

  47. Re:Steganography? by geminidomino · · Score: 1

    Except this doesn't seem "better" since it's just one fsck away from obliterating everything.

  48. Simon & Garfunkel fans sing with me: by Tablizer · · Score: 1

    "His bowtie is really a camera..."

    1. Re:Simon & Garfunkel fans sing with me: by wideBlueSkies · · Score: 1

      Have you heard the Yes version? Great rendition. :)

      --
      Huh?
  49. Re:Steganography? by digitig · · Score: 2

    fuck religious people in general

    Can I start with the cute ones, please?

    --
    Quidnam Latine loqui modo coepi?
  50. They're hiding in the block-lists, not empty space by davecb · · Score: 1

    They reorder full blocks to encode data in the orderings within the list of blocks for a given file. That's why they "do not require storage of any additional information on the filesystem" and why "a capacity of up to 24 bits/cluster can be achieved on a half-empty disk".
    If they wrote to additional blocks they (1) would be adding additional data to the filesystem, (2) would have no limit to the data that could be hidden and (3) would lose it as soon as one started writing additional information to the disk and used the empty blocks.

    See instead the abstract from Science Direct:
    http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6V8G-51BBKRS-1&_user=10&_coverDate=01%2F31%2F2011&_rdoc=1&_fmt=high&_orig=gateway&_origin=gateway&_sort=d&_docanchor=&view=c&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=ee913861b3d05b46b905bd4d52ca9380&searchtype=a

    --
    davecb@spamcop.net
  51. Re:Steganography? by creat3d · · Score: 0

    My thoughts exactly... both are abominations by themselves, but have them "cooperate" on a project and the result can be quite disastrous. I'm sure the biggest terrorist attack of our century rings a bell...

    --
    Grammar nazis are to this community what excrements are to gold.
  52. Re:Defrag and die by FrootLoops · · Score: 1

    It seems like TFA's author might have made the same mistake, or their wording is extremely poor. They say

    The software does this by breaking a file to be hidden into a number of fragments and placing the individual pieces in clusters scattered around the hard drive. [...] The method that Khan and his colleagues developed avoids this problem by hiding small pieces of a sensitive file various random places on a hard drive. [...] as the sensitive files are not actually hidden but rather dispersed in pieces.

    The file is broken into bits and placed in the arrangement of clusters--these bits are not literally written to the hard drive.

  53. Re:Defrag and die by Anonymous Coward · · Score: 0

    Defrag? What is defrag? Oh, I know. You use one of those "archeological relic from the past" operating systems that don't have self-cleaning file systems. The patent expired on this stuff more than 20 years ago. IBM developed and implemented it in 1968. It was hot stuff back then. Defrag, oh, and vote for Hubert Humphrey, don't vote for that Nixon! I see political scandal in his future! Perhaps next time you could describe problems with file systems whos' design is newer than 40 years old? Is your 160kB 5 1/4" floppy disk ok? Have you ever gotten a punched card misplaced in your card deck? You sure find out in less than an hour when you get the printout from the teletypewriter! Oh, and defrag!

  54. Re:Steganography? by CharlyFoxtrot · · Score: 1

    Start with the girls of the IDF and work your way through the middle east from there.

    --
    If all else fails, immortality can always be assured by spectacular error.
  55. Re:Would it make more sense to hide the Hard Drive by I'm+not+really+here · · Score: 1

    Or, place it inside a fully functional printer, directly wired to the USB line, hiding in the back of an unused paper tray slot of a multi-slot computer... then, with the printer connected, the Hard Drive can also be connected (or easily disconnected). Add a switch internally if you're paranoid, or set the power such that turning off the printer turns on the hard drive and vice versa.

    --
    Before commenting on the Bible, please read it first
  56. Re:Defrag and die by Anonymous Coward · · Score: 0

    I have an SSD, you insensitive clod!

  57. Re:Steganography? by houghi · · Score: 2

    Look at copyright and patenting lawsuits and you will realize that he is not alone. We used to stand on the shoulders of giants. Nowadays these giants ask so much rent you can't stand on their shoulders.
    Even if standing on their shoulders would mean you could drag them out of the pit, they rather get money then be saved.

    --
    Don't fight for your country, if your country does not fight for you.
  58. Re:As long as the Mossad is not involved by Jeremiah+Cornelius · · Score: 1

    Do you think there is an "intelligence" organisation in the world, that is no co-opted and part of the secret government operations?

    --
    "Flyin' in just a sweet place,
    Never been known to fail..."
  59. Security through Obfuscation by Calsar · · Score: 0

    This is basically security through obfuscation and we all know how well that works in the long run.

  60. Re:Would it make more sense to hide the Hard Drive by jonadab · · Score: 1

    If you're going to assume that they won't do a thorough physical search, you might as well just put a second hard drive in the computer but disconnect the data cable. Any search too cursory to find it in a hollow book won't find it in the spare internal drive bay either.

    This approach fails badly, though: if they do any kind of serious physical search, the gig is up.

    --
    Cut that out, or I will ship you to Norilsk in a box.
  61. Re:Steganography? by Anonymous Coward · · Score: 0

    I am really surprised Garfinkel, who is on the editorial board for the journal, let it be published. They should have read through the BlackHat and DefCon archives before publishing. They are not just trying to stand on the shoulders of giants, but failing to credit those giants.

    At Blackhat Federal 2006 The Grudd and I were discussing various places to hide data. He brought up this exact method but we dismissed it because file systems were starting to do automatic file defragmentation. These researchers get credit for coming up with it separately and getting it published. However, they had to use FAT because it is one of the few file system in use today where the method will still reliably work.

    Today NTFS is the primary file system on over 90% of home computers, making research based on the archaic FAT file system nearly meaningless. USB drives and XBoxs still use FAT so legitimate forsenic of anti-forsenic research papers often include sections on FAT, but no serious paper only covers FAT.

  62. Re:Would it make more sense to hide the Hard Drive by DanielRavenNest · · Score: 1

    I think we can rely on the police to be lazy in general, and likely the search warrant would be for computer equipment. If you keep your naughty data in a spare small PC in a dusty box in the attic which you access wirelessly, and don't give them any special reason to think you have one up there, they could easily miss it.

    If you have an old style rear projection TV you can easily fit an entire PC inside it, and transmit data via the coax cable.

    At last a use for the cloud: register under a fake account name, say, that of your local prosecutor, and store your naughty files encrypted on there.

    [Note: by "naughty" I don't mean sexual necessarily, I mean anything the powerful don't want you to have]

  63. Re:Would it make more sense to hide the Hard Drive by PhrstBrn · · Score: 1

    I think we can rely on the police to be lazy in general, and likely the search warrant would be for computer equipment. If you keep your naughty data in a spare small PC in a dusty box in the attic which you access wirelessly, and don't give them any special reason to think you have one up there, they could easily miss it.

    If they seized your computer and did forensics on it, they would see you accessing some wifi box "dirtydatamachine". They walk up to your premise with a wifi scanner, and wonder why there there is an AP without and SSID being broadcast, that happens to respond with "dirtydatamachine".

    The only thing that will really work with this is to encrypt the drive with truecrypt and only give up the decoy password, at which point there is no reason to bother with the WiFi box.

  64. Doesn't look undetectable by davitf · · Score: 1
    From the article:

    a cluster is chained with a consecutive cluster if the bit encountered in the message is similar to the previous bit and a cluster is chained with a non-consecutive cluster if the message bit is different from the previous message bit.

    Then, even if the data is encrypted with an unknown key, we can expect almost exactly half the clusters to be chained to consecutive ones, and they are distributed a random fashion. By counting the length of consecutive cluster blocks, we should see that 1/2 of them have 1 cluster, 1/4 have 2 clusters, 1/8 have 3 clusters and so on, and they are evenly distributed along the drive.

    It's very unlikely that such a distribution would appear spontaneously on a disk by just using it normally, so someone who knows that this scheme exists can check whether it is present on the disk, even if they're not able to decode the data.

    (Disclaimer: I haven't read the actual paper, they may have addressed this. Or the claim in the article may be incorrect.)

  65. Re:Would it make more sense to hide the Hard Drive by Anonymous Coward · · Score: 0

    A hollowed out battery casing in a common form-factor (think C, D, or 9V) containing an SD card or USB stick would even be easier. Besides, something like that can easily be put in with the batteries on a travel radio or battery operated toy and (if done correctly) all you're going to see on an X-ray is the same metal casing as on the other batteries. Not to mention that when considering the inconvenience and difficulty in carrying it out, it's unlikely customs or baggage checks is going to confiscate batteries out of everything that passes their way.

    Why people go for a hard drive to hold such a small amount of encrypted data when easier methods are available appears a little silly.

    It seems like a method that's probably more useful to log and hide data about the computer it's on with a low probability of detection. Like something for a hard to detect trojan or key-logger with low network usage that piggy-backs its activity with other more legit network activity. Whether or not it's applied that way is another question.

  66. Re:bollocks: Not even hidden! by Terje+Mathisen · · Score: 1

    Bollocks indeed:

    a) Even with small amounts of hidden data (20 MB in 160 GB was quoted), you will still end up with an _extremely_ fragmented file system:

    Each hidden bit requires either a sequential or fragmented block placement, which means that 20 MB needs 160 Mbit or 160 million frag/nofrag chaining decisions.

    This works out to one such block per kB of disk space, but since the FAT32 filesystem normally uses 4 KB (or larger) clusters, you would have to decrease the block size to either 1 KB or 512 bytes (the sector size, so the minimum possible).

    Since the (presumably compressed and encrypted) data to be hidden will have 50% 0 and 1 bits, the allocation run lengths in the file system will average just two clusters, this would be extremely obvious on any low-level scan of the file system.

    I.e. you could make this system work, but only in order to hide a few KB of data, not MB!

    Terje

    --
    "almost all programming can be viewed as an exercise in caching"
  67. Re:Would it make more sense to hide the Hard Drive by Anonymous Coward · · Score: 0

    For example, place the hard drive in the shell of a real but non functional printer. If it doesn't need to be connected, alternately hollow out a book and hide it in there, etc.

    lol, spot on.

  68. Scanners... by Anonymous Coward · · Score: 0

    And when they x-ray your book and find a hard drive inside?

  69. Re:Would it make more sense to hide the Hard Drive by Anonymous Coward · · Score: 0

    1. It would work through your regular AP (no mysterious unidentified APs)

    2. By the time they've carted off your main computer and done forensics on it, you've had time to dispose of the machine containing your illicit data.

    3. In the UK you can be locked up for failing to disclose your encryption keys when asked, I don't fancy trying to convince them I haven't got any hidden Truecrypt volumes. You could deny having them, but the question is: can they lock you up anyway if they think you have one? I don't think that question has been tested yet. So keeping your illicit data on a box they won't find in the first raid may be safer whether it is encrypted on the hidden box or not.