On Montag, 9. Oktober 2017 15:46:16 CEST Paul Schaub wrote: > Hi! > > I'm currently thinking about errors that might occur when initializing > an encrypted Jingle session. Most prominent when the decryption of the > Transport Key fails for some reason (eg. corrupted OMEMO session, > missing trust decision, wrong PGP key etc.). > > Jingle (XEP-0166) defines a security-error (Table 3), which is an "[...] > action is related to a violation of local security policies.". > > Do you think it makes sense to handle decryption errors by sending a > session-terminate with a reason containing a security-error (and an > additional descriptive error text)? I'm not sure, whether Jingle > (XEP-0166) allows for finer error handling.
I think you can add your own custom error conditions in the JET context. The involved parties already know that they support JET, so extending Jingle with JET-specific errors should be fine. kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
