hakimrie/f5-steganography

Automatically exported from code.google.com/p/f5-steganography

f5-steganography's Issues

Embedded file content are getting lost when its embedded with default quality i.e. 80

What steps will reproduce the problem?
1. embed file with -q 80.
2. extract the file from the jpg
3. some of the contents at the end of file is lost.

What is the expected output? What do you see instead?
Full file supposed to be extracted with default quality.

What version of the product are you using? On what operating system?
Windows. Version is not marked in f5.jar.

Please provide any additional information below.
Embed the file test.txt in out1.jpg through command
java -jar f5.jar e -e test.txt -q 80 use.jpg out1.jpg

Extract the embed file using command
java -jar f5.jar x -e test.txt out1.jpg

Message received after running the jar file:
Huffman decoding starts
Permutation starts
2545920 indices shuffled
Extraction starts
Length of embedded file: 22601 bytes
Default code used
Incomplete file: only 22058 of 22601 bytes extracted

Original issue reported on code.google.com by [email protected] on 22 May 2013 at 11:04

OME for large JPG

What steps will reproduce the problem?
1. Operating upon a 6MB jpg crashed the app with OutOfMemoryException
2.
3.

What is the expected output? What do you see instead?
Did not expect an OME


What version of the product are you using? On what operating system?
jdk1.7 on win7


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 17 Dec 2013 at 5:46

Process is very slow in permutation class

What steps will reproduce the problem?
1. Debug the code with a IDE for Java.
2. Put a breakpoint in Permutation Class
3. See that delay 4-5 segs to run the permutation process.

What is the expected output? What do you see instead?
The delay must be 1-2 seg to run the permutation process.

What version of the product are you using? On what operating system?
ALL

Please provide any additional information below.
N/A

Original issue reported on code.google.com by [email protected] on 14 Jul 2013 at 6:10