nullexceptiontsb / psteg Goto Github PK

s/e

engine errors are not handled correctly in psteg-stegano an cause unhandled exceptions
this error has been previously fixed in chaffblob

SOS section is skipped using the length parameter
this is incorrect behavior, it must be partially parsed (read until an unescaped 0xFF byte is found)

broh

self explanitory, make the code not horrible

currently chaffs are more likely to be inserted at the end of a file, as opposed to the start. same applies with larger files as opposed to smaller ones. this could be remedied by giving each file a weight proportional to their total size instead of each file being equally likely to be selected. this would greatly improved theoretical security of the Chaffblob implementation

Raw data file handle is leaked

To repro:
open "Steganographic Method" combobox
open start menu using windows key

Program will throw unhandled exception and select an invalid method

se

add a hash settings dialog to configure hashing for cryptographic passwords

this has already been fixed upstream

tested on: james.png
payload: astely.txt
last bit changed: 1 => 0

for fourier transform-basted steganography methods

implement ACL steganography

implement ads steganography

the current code is monolythic, messy and very ugly. rewrite it to be less Bad.

the engine is written but the glue code isn't (forgor). this causes the lsb-dct engine to be unusable.

depends: #11 #7