[jitsi-users] Possible Bug: OTR chat needs refreshing after period of inactivity


#1

Hello Everyone,

Something I've noticed that's happened over a few Jitsi version is
that OTR conversations need to be refreshed after a period of
inactivity. For example, if I'm chatting OTR with someone and we go
away for a little while then come back, the session will still show as
OTR encrypted but typing messages gives the message

"You've sent me an unreadable encrypted message".

Refreshing the conversation seems to fix it.

Show I report this as a bug or is this expected behavior?

Thanks!
Anthony

- -- geg
Anthony Papillion
Phone: 1.918.533.9699
SIP: 17772098750@in.callcentric.com
XMPP: cypherpunk@patts.us

www.cajuntechie.org


#2

On XP pro, I have the latest nightly installed - I have it set to play back on plantronic USB headphones, if I hit the test button to play audio in the headphones,fails - but the phone actually works. The mic input shows sound levels.

···

--------------------------------------------------------------------------------
Karl Schmidt EMail Karl@xtronics.com
Transtronics, Inc. WEB http://secure.transtronics.com
3209 West 9th Street Ph (785) 841-3089
Lawrence, KS 66049 FAX (785) 841-0434

Ethical axioms are found and tested not very differently from the axioms of science.
Truth is what stands the test of experience.
Albert Einstein - an objectivist.
--------------------------------------------------------------------------------


#3

I can confirm this behavior.

- --
John Perry

···

On 8/4/2013 6:12 PM, Anthony Papillion wrote:

Hello Everyone,

Something I've noticed that's happened over a few Jitsi version is
that OTR conversations need to be refreshed after a period of
inactivity. For example, if I'm chatting OTR with someone and we
go away for a little while then come back, the session will still
show as OTR encrypted but typing messages gives the message

"You've sent me an unreadable encrypted message".

Refreshing the conversation seems to fix it.

Show I report this as a bug or is this expected behavior?

Thanks! Anthony


#4

Anthony Papillion:

Hello Everyone,

Something I've noticed that's happened over a few Jitsi version is
that OTR conversations need to be refreshed after a period of
inactivity. For example, if I'm chatting OTR with someone and we go
away for a little while then come back, the session will still show as
OTR encrypted but typing messages gives the message

"You've sent me an unreadable encrypted message".

Refreshing the conversation seems to fix it.

Show I report this as a bug or is this expected behavior?

I'm not 100% sure, please correct me. I think it's kind of expected
behaviour unfortunately. I would guess it's part of otr4j (or libotr)
because it's the same with all clients using OTR.
   So when your active chat session expires or is quit by one
participent, the OTR session has to be reestablished. It has nothing to
do with jitsi in particular. What _can_ be done is the notification
about recieving a message that cannot be read: I'd notify just like an
incoming message plus suggesting to reestablish the otr session with one
click if not doing it automatically.
   Especially important on mobile, where it shouldn't happen that
someone sends messages to me and my client knows about it, but doesn't
even notify me, just because the otr session has expired previously.

···

Thanks!
Anthony

-- geg
Anthony Papillion
Phone: 1.918.533.9699
SIP: 17772098750@in.callcentric.com
XMPP: cypherpunk@patts.us

www.cajuntechie.org

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

This happens sometimes on other clients, however, not routinely. If using jitsi you find that you can reproduce this always by going away for a while, then I'd say that is a possible bug, but it could perhaps have something to do with some setting keeping a conversation connection live?

···

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello Everyone,

Something I've noticed that's happened over a few Jitsi version is
that OTR conversations need to be refreshed after a period of
inactivity. For example, if I'm chatting OTR with someone and we go
away for a little while then come back, the session will still show as
OTR encrypted but typing messages gives the message

"You've sent me an unreadable encrypted message".

Refreshing the conversation seems to fix it.

Show I report this as a bug or is this expected behavior?

Thanks!
Anthony

- -- geg
Anthony Papillion
Phone: 1.918.533.9699
SIP: 17772098750@in.callcentric.com
XMPP: cypherpunk@patts.us

www.cajuntechie.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJR/t+1AAoJEKCKfnPhYIFFhrkQAMAts/oxmYz1XfY+YB+5XrvU
QTaqTnoCEyPm5chiAotxzb7wBAeDBNHDdeH9kd40ad/93+HBTVPtBtH+/PQKJb63
11OxCullUcEp/GjIlOfkmOEv3nqltwbGeuYx6WIQViMPw3RIRvRarEqiNQdzwVj3
u+ymCT+whLngauoV3zgzQ+yyzo1JLJBgJXdKE7N2lCVekeftVs9h6zzu0XabMgN0
euO977jgFGFWfLOLiVJPMHXtJspdEjEh09QGKP2j+euE0VNNQ2LvP55pl3IlIdNL
GmCUZtE7oTrDS/3JWpMREJU28CQdMFnn0jE8hRGOZDQeTH4CiGcxCxGIKSOIlikI
Uzgle+7bmk7cTmME1kbhqQogGuCd8P58rzsl7Oaf1I32kCsG0bDATJmJmr0SuHUy
0PLRNg/2NeMuZrV7kVo4bTz08N24Hd8lTEObGjkbISiQh9rgvoplS7EmC1NRrVvB
Y5hzXO1dbH79lcIdTH7EzupF2crvvEj9oNyifDCowCSjbGwLj4UshpD8lAWY5o7c
PNMhHK2l1kTLL6OnbZ/D766Y1n5Bck685i5rd95Dg20yEj76wG1xazD0ge1DNSox
klctZ+cQtDmMpHDsMpqUAUJH/eAhJPygMZ8ZAYDDeRsWn3RNrQf9rJbGZtK7yPO3
3gP6aUyV0yHsmOgckPT8
=/1GB
-----END PGP SIGNATURE-----

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#6

Yes, I agree. In fact, I believe ice seen a similar thing happen in Pidgin once before. But it's definately something that I'm able to reproduce fairly reliably. So I think I'll make a bug report just in case.

Thanks!
Anthony

···

--
Sent from my mobile device

On Aug 4, 2013, at 11:16 PM, BitMessage <BM-2DBVT9yeUEFhLR8Qg9vhqB7ZQE9Sf3gAgS@bitmessage.ch > wrote:

This happens sometimes on other clients, however, not routinely. If using jitsi you find that you can reproduce this always by going away for a while, then I'd say that is a possible bug, but it could perhaps have something to do with some setting keeping a conversation connection live?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello Everyone,

Something I've noticed that's happened over a few Jitsi version is
that OTR conversations need to be refreshed after a period of
inactivity. For example, if I'm chatting OTR with someone and we go
away for a little while then come back, the session will still show as
OTR encrypted but typing messages gives the message

"You've sent me an unreadable encrypted message".

Refreshing the conversation seems to fix it.

Show I report this as a bug or is this expected behavior?

Thanks!
Anthony

- -- geg
Anthony Papillion
Phone: 1.918.533.9699
SIP: 17772098750@in.callcentric.com
XMPP: cypherpunk@patts.us

www.cajuntechie.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJR/t+1AAoJEKCKfnPhYIFFhrkQAMAts/oxmYz1XfY+YB+5XrvU
QTaqTnoCEyPm5chiAotxzb7wBAeDBNHDdeH9kd40ad/93+HBTVPtBtH+/PQKJb63
11OxCullUcEp/GjIlOfkmOEv3nqltwbGeuYx6WIQViMPw3RIRvRarEqiNQdzwVj3
u+ymCT+whLngauoV3zgzQ+yyzo1JLJBgJXdKE7N2lCVekeftVs9h6zzu0XabMgN0
euO977jgFGFWfLOLiVJPMHXtJspdEjEh09QGKP2j+euE0VNNQ2LvP55pl3IlIdNL
GmCUZtE7oTrDS/3JWpMREJU28CQdMFnn0jE8hRGOZDQeTH4CiGcxCxGIKSOIlikI
Uzgle+7bmk7cTmME1kbhqQogGuCd8P58rzsl7Oaf1I32kCsG0bDATJmJmr0SuHUy
0PLRNg/2NeMuZrV7kVo4bTz08N24Hd8lTEObGjkbISiQh9rgvoplS7EmC1NRrVvB
Y5hzXO1dbH79lcIdTH7EzupF2crvvEj9oNyifDCowCSjbGwLj4UshpD8lAWY5o7c
PNMhHK2l1kTLL6OnbZ/D766Y1n5Bck685i5rd95Dg20yEj76wG1xazD0ge1DNSox
klctZ+cQtDmMpHDsMpqUAUJH/eAhJPygMZ8ZAYDDeRsWn3RNrQf9rJbGZtK7yPO3
3gP6aUyV0yHsmOgckPT8
=/1GB
-----END PGP SIGNATURE-----

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#7

Anthony Papillion:

Hello Everyone,

Something I've noticed that's happened over a few Jitsi version
is that OTR conversations need to be refreshed after a period of
inactivity. For example, if I'm chatting OTR with someone and we
go away for a little while then come back, the session will still
show as OTR encrypted but typing messages gives the message

"You've sent me an unreadable encrypted message".

Refreshing the conversation seems to fix it.

Show I report this as a bug or is this expected behavior?

I'm not 100% sure, please correct me. I think it's kind of
expected behaviour unfortunately. I would guess it's part of otr4j
(or libotr) because it's the same with all clients using OTR.

That may explain why it happens in multiple clients like another
poster suggested. I think both Jitsi and Pidgin (as well as others)
use libotr or some variant of it. Makes sense.

So when your active chat session expires or is quit by one
participent, the OTR session has to be reestablished. It has
nothing to do with jitsi in particular. What _can_ be done is the
notification about recieving a message that cannot be read: I'd
notify just like an incoming message plus suggesting to reestablish
the otr session with one click if not doing it automatically.

In fact, I believe that this is the behavior that happens with Jitsi.
When you type a message and the session has expired, it is (usually)
automatically reestablished. But not always. Sometimes, you have to
manually re-establish the connection. Not a big deal in and of itself
but one of those 'nice to haves'.

Especially important on mobile, where it shouldn't happen that
someone sends messages to me and my client knows about it, but
doesn't even notify me, just because the otr session has expired
previously.

Agreed.

Best Regards,
Anthony

- --
Anthony Papillion
Phone: 1.918.533.9699
SIP: 17772098750@in.callcentric.com
XMPP: cypherpunk@patts.us

www.cajuntechie.org

···

On 08/05/2013 07:04 AM, Martin Kepplinger wrote:


#8

I'm not 100% sure, please correct me. I think it's kind of
expected behaviour unfortunately. I would guess it's part of otr4j
(or libotr) because it's the same with all clients using OTR.

That may explain why it happens in multiple clients like another
poster suggested. I think both Jitsi and Pidgin (as well as others)
use libotr or some variant of it. Makes sense.

Jitsi uses otr4j. The only similarity that comes to mind would be that
George Politis (the author of otr4j) was inspired by libotr.

A general remark to OTR: We know that we have a lot of issues with it. I
hope to work on this sometimes this year, but I can't promise anything.
If you have a _reproducible_ scenario that doesn't work, please describe it
in a comment to ticket 758 [1] or 1075 [2] with as much details as possible.

Ingo

[1] https://trac.jitsi.org/ticket/758
[2] https://trac.jitsi.org/ticket/1075