-
Notifications
You must be signed in to change notification settings - Fork 24
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
Only the last message fragment is sent #21
Comments
This has been observed by some people in the last days indeed. Thanks for this. This is obviously a big priority. |
This seems like an libotr upstream problem. I'm waiting for a patch to be accepted. http://lists.cypherpunks.ca/pipermail/otr-dev/2013-January/001549.html |
Still waiting for the patch to be upstream so I'll add it here since it's pretty trivial. http://ev0ke.net/0001-Fix-pass-opdata-when-sending-message-fragment.patch |
Shouldn't this be closed, considering it's a bug in libotr? |
I don't think so because this package does not work properly with upstream libotr and keeping this opened acknowledge the issue and even provide a fix. Until we see the fix in upstream libotr, I really think this should be kept open because other distros (like Arch or even Ubuntu) are not providing a fix for libotr. |
Ok so this is upstream in libotr right now. We are putting pressure on them to release a new version with that fix so packages stop applying this custom patch. Once a release is done, we'll close this one! |
thanks! any timeline on that? or reference for the upstream issue, for that matter? |
Ian needs to create a new libOTR release, it's upstream in the git repository. |
well, that's what i meant: do we know when they will do a new release or where their bugtracker is? |
-----BEGIN PGP SIGNED MESSAGE----- There isn't really a bugtracker, there is a mailinglist however[1] [1] http://lists.cypherpunks.ca/mailman/listinfo/otr-de iQEcBAEBAgAGBQJSRtofAAoJELc5KWfqgB0C3aAH/jF4ErUbkSs7wp3Z/1O0byV2 |
I hope it doesn't make libotr insecure, but the trivial patch comes from this irssi-otr thread: cryptodotis/irssi-otr#21
When sending encrypted messages that need to be fragmented, only the last fragment is actually sent to the IRC server. I can reproduce this by connecting two irssi clients to the same IRC server, initiating an OTR session between them and sending an 80 character line from one client to the other. "/rawlog save" only shows the fragment that starts with "?OTR|...|...,00002,00002,".
I've tested this with irssi 0.8.15-5 and ibotr5 4.0.0-2 on Debian wheezy amd64 with irssi-otr v1.0.0-alpha1-5-g5f685aa from git.
The text was updated successfully, but these errors were encountered: