Steganography Freeware Available Now
in [Cryptography]
|
Prev: now, you need to encrypt a test .pdf file, what better than the original RSA paper?
Next: cracking an old zip password
From: jmorton123 on 2 Jun 2010 23:15 I think I wrote in one too-big paragraph. Here it is step by step and why as I go along: 1.) place your source files into a folder and zip that folder. 2.) XOR this zipped folder with a random binary number file generated using the BulletProof software. That random binary number file will have a name such as, FA000001. Name this XORed zipped folder, FA000001 so by just looking at the zipped folder name you will know what random binary number file was used to XOR the folder. 3.) Place FA000001 into another folder and zip it. It is not important what you call this last zipped folder. What is important is that you know that it is a zipped folder. 4.) Use Stega_BP_v3.exe and embed this last zipped folder into a bitmap image using Digits.txt. Like it says in the Stega instructions, if you want to be sure the maximum file size of 110KB is successfully embedded into a bitmap image, make the bitmap image file at least 1760KB and the Digits.txt file at least 10,000,000 random digits long. This should be guaranteed successful. And any source file smaller will also be successfully embedded, guaranteed. 5.) So here you are with a bitmap image file with your double-zipped and XORed source embedded into it. If you like you can now post this bitmap image on your website. Then go to your website and right-click on the bitmap image and save it to your hard drive. Or email the bitmap image to yourself then open your email and save the bitmap image to your hard drive. Now start Stega_BP_v3.exe and select extract. Input this bitmap image as the source bitmap image file. Again, use your Digits.txt random digits file for you next input and save the extracted file as any name you like but put a .zip extension on it. This source bitmap image file you are extracting from is the exact same one you used originally to embed with except of course the LSBs of the randomly chosen bytes within it have been set to your source's bits. When you run Stega to extract, it will use the Digits.txt to generate the exact same random numbers to access the exact same random bytes from this bitmap image. It knows to extract the LSBs from these random bytes and to recombine them to extract the embedded file which is your last zip file. So now you have extracted the file you saved with the added .zip extension. You added the .zip extension because you already know that the file is a zipped file. Now unzip this file and you will get your FA000001 zipped file from within this unzipped folder. See, if you did not zip up the FA000001 zipped file into this last zip file, you could not have transmitted the name of the FA000001 random binary number file used to XOR the folder containing your source files. You would have had to find another way to let yourself know what random binary number file to use to re-XOR the zip file to get your original source files back. When you XORed the folder with your source files in it, every byte got XORed. And if you used a "useable" random binary number file generated with BulletProof, there is no way anyone can determine what the contents of the XORed file is by just trying to crack the random binary numbers used. So this is my highly recommended protocol. You are embedding only one file: the last zipped file that has in it the XORed zip file named, FA000001 that when re-XORed gives you the folder that has in it your original source files. I think this is correct. I appreciate your interest. Ten years ago if anyone would have told me the country and the world would be where it is today, I'd say they were crazy. Well, here we are. I think that if someone today came up to me and rightly told me how things would be in another ten years from now, I'd probably say they were crazy. I would not let BulletProof, XOR, and Bitmap Steganography pass me by. Who knows, this software might not be available tomorrow. Things change. JM On Jun 2, 6:30 am, mike clark <m...(a)netadv.net> wrote: > On Jun 1, 11:54 pm, jmorton123 <jmorton...(a)rock.com> wrote: > > > On May 30, 10:52 pm, Mok-Kong Shen <mok-kong.s...(a)t-online.de> wrote: > > > I also suggested a protocol in my original post that was not quite > > right. Here is what I wanted to say: place your source files into a > > folder. Zip this folder. Use the XOR Utility Program availabe at > > KingKonglomerate.com to XOR this folder using random binary numbers > > generated with BulletProof Random Binary Number Generator, also > > available at KingKonglomerate.com. These random binary number files > > will have file names such as FA000001. Next, place the FA000001 file > > into another folder and zip it. The reason for this is that you need > > to preserve the file name in order to know what file was used to XOR > > it. Now you use the Stega_BP_v3.exe software to randomly embed this > > into a bitmap image. > > Embed what? The zipped random file or the zipped source files? I'm > guessing both. > > > When you extract the file from the bitmap image, > > you already know it is a zip file. Just add the .zip extension and > > unzip it. In the unzipped folder you will find FA000001. You then > > use FA000001 to XOR to get the folder with your original source files > > in it. > > So basically you are encrypting our plaintext with a random file. Then > storing that random file and the ciphertext in (basically) the clear. > If the attacker knows your algorithm he can also extract the zipped > key file, add the .zip extension, unzip it and use the resulting > random file to decrypt the ciphertext.
From: Mok-Kong Shen on 3 Jun 2010 09:50 jmorton123 wrote: > Currently, the stega utility program embeds into the LSB of a ranomly > chosen byte in the bitmap image. This random byte is chosen based > solely on the random digit string in the Digits.txt file. > > The following could easily be implemented: select a particular byte > in the bitmap image and do anything you want with any particular bit > in that byte. > > Each pixel consists of three bytes: red, green, blue. All the bytes > in a bitmap image are in this order: blue, green, red. > > So it would be straight forward to do what you describe. > > The BulletProof source code is available on a non-exclusive basis but > requires, along with a non-disclosure agreement, a rather large sum of > money. > > This is also the case for the Stega program. But the title of the thread says it's freeware, isn't it? M. K. Shen
From: jmorton123 on 3 Jun 2010 23:45 The freeware is free. Not the source code. JM On Jun 3, 6:50 am, Mok-Kong Shen <mok-kong.s...(a)t-online.de> wrote: > jmorton123 wrote: > > Currently, the stega utility program embeds into the LSB of a ranomly > > chosen byte in the bitmap image. This random byte is chosen based > > solely on the random digit string in the Digits.txt file. > > > The following could easily be implemented: select a particular byte > > in the bitmap image and do anything you want with any particular bit > > in that byte. > > > Each pixel consists of three bytes: red, green, blue. All the bytes > > in a bitmap image are in this order: blue, green, red. > > > So it would be straight forward to do what you describe. > > > The BulletProof source code is available on a non-exclusive basis but > > requires, along with a non-disclosure agreement, a rather large sum of > > money. > > > This is also the case for the Stega program. > > But the title of the thread says it's freeware, isn't it? > > M. K. Shen- Hide quoted text - > > - Show quoted text -
From: Mok-Kong Shen on 4 Jun 2010 04:30 jmorton123 wrote: > The freeware is free. > > Not the source code. I maintain: If you could do a bit generalization as I mentioned, your software would get a wider acceptance. M. K. Shen
From: jmorton123 on 5 Jun 2010 08:26
So you want to be able to input which bytes to access and which bits within each byte to manipulate, right? Give me an example of the precise input you want to be able to make to get the desired output and describe the output precisely. Don't just describe it: give me the input you would expect to make - the complete input, not generalities, and how do you want to enter the input? JM On Jun 4, 1:30 am, Mok-Kong Shen <mok-kong.s...(a)t-online.de> wrote: > jmorton123 wrote: > > The freeware is free. > > > Not the source code. > > I maintain: If you could do a bit generalization as I mentioned, your > software would get a wider acceptance. > > M. K. Shen |