Skip to content

/ Ciphey

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deciphering base64-encoded files yield no results when run with -i #215

Open
TheAlcanian opened this issue Jul 29, 2020 · 8 comments
Open

Deciphering base64-encoded files yield no results when run with -i #215

TheAlcanian opened this issue Jul 29, 2020 · 8 comments
Assignees
@bee-san
Labels
bug good first issue

Comments

@TheAlcanian
Copy link

@TheAlcanian TheAlcanian commented Jul 29, 2020

Describe the bug
When running Ciphey on a base64-encoded file using the - command-line parameter, Ciphey picks up and decodes the base64-encoded file's contents, and prints the decoded content like normal. When running Ciphey on a base64-encoded file using the -i command-line parameter, Ciphey finds no results.

To Reproduce
Steps to reproduce the behavior:

  1. What input did you use?
    A sample file named test_base64 with the contents dGVzdCBiYXNlNjQgb3V0cHV0Cg==
  2. What flags / arguments did you use?
    Command run was ciphey -i test_base64.

Expected behavior
Ciphey decodes the base64, outputs the decoded text and exits normally.

Versions:

  • OS/Distro: Gentoo Linux
  • Python version: Python 3.7.8
  • Ciphey versions: CipheyCore v0.2.4, CipheyDists v0.3.11, Ciphey v5.0.0rc10
@TheAlcanian TheAlcanian added the bug label Jul 29, 2020
@issue-label-bot
Copy link

@issue-label-bot issue-label-bot bot commented Jul 29, 2020

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.
@TheAlcanian TheAlcanian changed the title Deciphering base64-encoded files yield no results when run with `-i` Deciphering base64-encoded files yield no results when run with -i Jul 29, 2020
@TheAlcanian
Copy link
Author

@TheAlcanian TheAlcanian commented Jul 29, 2020

Edited title because I remembered markdown doesn't work in titles
@bee-san
Copy link
Member

@bee-san bee-san commented Jul 29, 2020

@all-contributors please add @TheAlcanian for bugs
@allcontributors allcontributors bot mentioned this issue Jul 29, 2020
Merged
@allcontributors
Copy link
Contributor

@allcontributors allcontributors bot commented Jul 29, 2020

@brandonskerritt

I've put up a pull request to add @TheAlcanian! 🎉
@Cyclic3
Copy link
Member

@Cyclic3 Cyclic3 commented Jul 31, 2020

Can you run this with -vv (to give trace logging)?
@TheAlcanian
Copy link
Author

@TheAlcanian TheAlcanian commented Aug 1, 2020

decoded_but_not_output.txt
Decoded, but not output?
@Cyclic3
Copy link
Member

@Cyclic3 Cyclic3 commented Aug 2, 2020

Ciphey seems to be loading the filename itself as the ciphertext, rather than as the input. The -i parameter actually doesn't really do anything atm, so I would omit it.

We are having difficulty reading in files with ciphey (hopefully fixed soon), so the best bet is to use cat <file> | ciphey <flags...> (or type <file> | ciphey <flags...> on windows`) until we get that fixed
@TheAlcanian
Copy link
Author

@TheAlcanian TheAlcanian commented Aug 3, 2020

Sounds good.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bee-san bee-san

Labels
bug good first issue
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@bee-san @Cyclic3 @TheAlcanian
You can’t perform that action at this time.