-
Notifications
You must be signed in to change notification settings - Fork 1
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
Implement parsing #1
Comments
This issue includes to make public some fuctions of libotr |
@annacruz and me had a quick conversation and we have decided to implement the non-interactive messages later. We'll keep this issue close until we implement them. |
ok @deniscostadsc Quick question: why only the parsing of the data message takes a pointer and why there are no testing of the other messages? |
I also see a lot of potential memory leaks on the implemented functionality, so it will be nice to add tests to check these kind of things. |
Parsing is using a bunch of printfs that are not global, as it depends on the os: Parsing should not do that. |
Almost all parsing functions are memory leaking, see:
|
I'll try to fix the mem leaks :) |
So, it is only missing the prekey message. But for this, we need the whole |
Description:
OTR_parse should provide a program (command) the shows in a easier-to-read way the OTRv4 messages. Also need to provide functions that will be used by the other functions of toolkit.
Parser should be able to parse:
Reference:
https://bugs.otr.im/lib/libotr/blob/master/README (TOOLKIT section)
https://bugs.otr.im/lib/libotr/tree/master/toolkit
https://github.com/otrv4/otrv4/blob/master/otrv4.md#forging-transcripts
The text was updated successfully, but these errors were encountered: