#18 · closed · 3 comments
 hello! great tool. i have this error, i checked rockyou on sha256, its correct. why this error happening? Or maybe it should work like that, idunno?
Heya 👋 That message just means that it added the file name as a potential password candidate to try. I've seen a few times that a challenge author used the name of the stego file as a password, so stegseek tries that as well. Same for empty password for example. Nothing to worry about. Do you know for sure this file contains a stego payload, and do you know what password stegseek should be finding here? Without it there isn't much for me to debug. PS: I also notice you're trying to specify two wordlists here (rockyou.txt and a.txt). That is not supported syntax, so the `a.txt` argument is just discarded in this case.
i think yes, flag.jpg should contain smthng. i tried stegcracker, should i wait it? also appreciate your answer. cool story about that challenge author used name for passwd
If you don't know if the image contains steghide content and you don't know the password then I can't help you. This tool very specifically attacks steghide, it is not a general magic bullet stego tool. You can use `stegseek --seed <filename>` to test if it contains steghide content. If it comes back with "no seeds found" that means it doesn't contain steghide content and this tool will not be of use to you. Closing the issue here, since you seem to be asking for general stego advice rather than a bug report. If you find a case where stegseek fails to find a _known_ password or `--seed` reports no seed while you know a file contains steghide content then that'd be a bug in stegseek and you can open an issue for that.