Check if we need other OTR Error messages

otrv4 / libotr-ng

A new implementation of OTR with support for version 4. This is a mirror of https://bugs.otr.im/otrv4/libotr-ng

Other

43 stars 9 forks source link

Check if we need other OTR Error messages #104

Closed claucece closed 6 years ago

claucece commented 6 years ago

Why

As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of using OTR errors.

Reference

Please, refer to the OTR Error Messages section of the OTRv4 spec.

Tasks

Open questions

Should we include more error types?

olabini commented 6 years ago

Yes, I definitely think so.

claucece commented 6 years ago

Ok, so libotr3 has:

- OTRL_ERRCODE_ENCRYPTION_ERROR: occured while encrypting a message
- OTRL_ERRCODE_MSG_NOT_IN_PRIVATE: sent encrypted message to somebody who is not in a
 mutual OTR session
- OTRL_ERRCODE_MSG_UNREADABLE: sent an unreadable encrypted message
- OTRL_ERRCODE_MSG_MALFORMED: message sent is malformed

I think we can use the same..

claucece commented 6 years ago

Only a test and to update the spec is missing on this.