Bug: core dumped after entering cotp password - cotp v1.2.2 about cotp HOT 8 CLOSED

Thank you for reporting, can you send me the full backtrace by running RUST_BACKTRACE=1 cotp?

I assume this is a secret decoding error, but the full backtrace will help me find out where the real problem is.

from cotp.

No additional information is provided after running RUST_BACKTRACE=1 cotp
This is the result when doing a RUST_BACKTRACE=full cotp
Password:
thread 'main' panicked at 'called Result::unwrap() on an Err value: "DecodeError { position: 26, kind: Symbol }"', src/interface/table.rs:73:36
stack backtrace:
0: 0x5655334eb2e0 -
1: 0x56553344e0fe -
2: 0x5655334c2274 -
3: 0x5655334ec82f -
4: 0x5655334ec42f -
5: 0x5655334ed4a2 -
6: 0x5655334ecf84 -
7: 0x5655334eceec -
8: 0x5655334ecec1 -
9: 0x5655333ce5e2 -
10: 0x5655333cea12 -
11: 0x565533405cc6 -
12: 0x56553340c533 -
13: 0x565533409265 -
14: 0x5655333d83fd -
15: 0x56553341034e -
16: 0x7f85d12da790 -
17: 0x7f85d12da84a - __libc_start_main
18: 0x5655333d4b8e -
19: 0x0 -
Aborted (core dumped)

from cotp.

Ok thank, you i forgot that the debug info is striped out from the release binary.

When i get some time i will release a fix for this.

Probably you have an OTP secret that is not encoded correctly (or not handled correctly by the software), so i will prevent the UI to crash and highlight OTP codes with possible problems.

Thank you again for reporting.

from cotp.

@Libre4IT could you try this branch, UI should not crash anymore but highlight errors: #192

from cotp.

@replydev when cloning the repo and do a git branch I only see the master. Would you be able to assist?

from cotp.

@Libre4IT of course, please do:

• git fetch -a to fetch all the repository metadata.
• git checkout -b fix/crash_on_decode origin/fix/crash_on_decode to checkout the branch.
• cargo run to run the software.

To replicate the test case you could export your database using cotp export and then import in the development project using cargo run -- import -c -p <path_of_exported_file.json>.

from cotp.

@replydev It's fixed now. Great work!

from cotp.

Closing the issue as the problem is solved, feel free to open another issue if you think that the highlighted code (the one that gave the error) is right.

from cotp.