Skip to content
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

Decipher crack_cmd() #3

Open
assarbad opened this issue Oct 26, 2023 · 1 comment
Open

Decipher crack_cmd() #3

assarbad opened this issue Oct 26, 2023 · 1 comment
Assignees

Comments

@assarbad
Copy link
Owner

For c1 and c1xx we got the following types, apparently:

  • 1: bool getting set to true
  • 5: bool but setting value to false (inverted)
  • 10: char* callback(currswitch, currword)
  • 0x22: char*
  • 0x24: decimal number (validated) stored as 32-bit int/uint
  • 0x26: list of strings (some cumulative value)
  • 0x28: hexadecimal number (validated) stored as 32-bit int/uint
  • 0x29: same callback type as 10 (what's the difference, though?) ... maybe not the same type after all but something like char* vs. wchar_t*?

Special characters in the canonical string form are:

  • #
  • $
  • %
  • *
  • - (equivalent to or exchangeable for /?)
@assarbad
Copy link
Owner Author

assarbad commented Oct 27, 2023

For c2 the second field after the offset of the receiving variable seems to correspond to the above, also stored as byte. First field in that case is unclear. The third field -- a uint -- appears to somewhat correspond to the first field in c1/c1xx.

@assarbad assarbad self-assigned this Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant