From a.sporto+bee at gmail.com  Sat Feb 21 16:56:05 2009
From: a.sporto+bee at gmail.com (Uli M)
Date: Sat, 21 Feb 2009 22:56:05 +0100
Subject: [OTR-users] irssi-otr and xchat-otr 0.3 released / weechat-otr
	available in git
Message-ID: <20090221215604.GA12207@gmail.com>

Hiho,

irssi-otr[1] v0.3 is released. It has some interesting new features(see the
ChangeLog) and some bugs have been removed. The most important new feature is
probably that you can specify a list of <nick>@<server> patterns along with an
OTR policy for each one. That way you can, for instance, easily set a different
policy for IRC networks than you have for bitlbee (IM-to-IRC gateway) servers.

irssi-otr is available in many distributions and some have already picked up
v0.3. xchat-otr is quite new but already available in some distributions. In the
git repo you can also find weechat-otr which only works with the current
development version(0.2.7) of weechat. The whole project is now called "irc-otr"
and you can expect modules for other clients.

Thanks,

Uli

[1] http://irssi-otr.tuxfamily.org


From russg at rnstech.com  Sat Feb 21 17:48:55 2009
From: russg at rnstech.com (Russ Gibson)
Date: Sat, 21 Feb 2009 14:48:55 -0800
Subject: [OTR-users] IRC
In-Reply-To: <20090221215604.GA12207@gmail.com>
References: <20090221215604.GA12207@gmail.com>
Message-ID: <49A084D7.9040006@rnstech.com>

Is there a way to use otr in a session with multiple people on
irc.freenode.net?

If there is documentation somewhere, just point me to it, as I was
unable to find it.

Thanks.



From ian at cypherpunks.ca  Sat Feb 21 17:59:23 2009
From: ian at cypherpunks.ca (Ian Goldberg)
Date: Sat, 21 Feb 2009 17:59:23 -0500
Subject: [OTR-users] IRC
In-Reply-To: <49A084D7.9040006@rnstech.com>
References: <20090221215604.GA12207@gmail.com> <49A084D7.9040006@rnstech.com>
Message-ID: <20090221225923.GH11065@yoink.cs.uwaterloo.ca>

On Sat, Feb 21, 2009 at 02:48:55PM -0800, Russ Gibson wrote:
> Is there a way to use otr in a session with multiple people on
> irc.freenode.net?
> 
> If there is documentation somewhere, just point me to it, as I was
> unable to find it.

OTR does not (currently) support group chat rooms, only one-to-one
communication.

   - Ian


From ian at cypherpunks.ca  Sat Feb 21 18:01:56 2009
From: ian at cypherpunks.ca (Ian Goldberg)
Date: Sat, 21 Feb 2009 18:01:56 -0500
Subject: [OTR-users] irssi-otr and xchat-otr 0.3 released /
	weechat-otr	available in git
In-Reply-To: <20090221215604.GA12207@gmail.com>
References: <20090221215604.GA12207@gmail.com>
Message-ID: <20090221230156.GI11065@yoink.cs.uwaterloo.ca>

On Sat, Feb 21, 2009 at 10:56:05PM +0100, Uli M wrote:
> Hiho,
> 
> irssi-otr[1] v0.3 is released. It has some interesting new features(see the
> ChangeLog) and some bugs have been removed. The most important new feature is
> probably that you can specify a list of <nick>@<server> patterns along with an
> OTR policy for each one. That way you can, for instance, easily set a different
> policy for IRC networks than you have for bitlbee (IM-to-IRC gateway) servers.
> 
> irssi-otr is available in many distributions and some have already picked up
> v0.3. xchat-otr is quite new but already available in some distributions. In the
> git repo you can also find weechat-otr which only works with the current
> development version(0.2.7) of weechat. The whole project is now called "irc-otr"
> and you can expect modules for other clients.

Thanks!  I've updated the software page on the website.

   - Ian


From a.sporto+bee at gmail.com  Mon Feb 23 05:18:59 2009
From: a.sporto+bee at gmail.com (Uli M)
Date: Mon, 23 Feb 2009 11:18:59 +0100
Subject: [OTR-users] irssi-otr and xchat-otr 0.3 released /
	weechat-otr	available in git
In-Reply-To: <20090221230156.GI11065@yoink.cs.uwaterloo.ca>
References: <20090221215604.GA12207@gmail.com>
	<20090221230156.GI11065@yoink.cs.uwaterloo.ca>
Message-ID: <20090223101858.GA11667@gmail.com>

On Sat 21.02.09 18:01, Ian Goldberg wrote:
> On Sat, Feb 21, 2009 at 10:56:05PM +0100, Uli M wrote:
> > Hiho,
> > 
> > irssi-otr[1] v0.3 is released. It has some interesting new features(see the
> > ChangeLog) and some bugs have been removed. The most important new feature is
> > probably that you can specify a list of <nick>@<server> patterns along with an
> > OTR policy for each one. That way you can, for instance, easily set a different
> > policy for IRC networks than you have for bitlbee (IM-to-IRC gateway) servers.
> > 
> > irssi-otr is available in many distributions and some have already picked up
> > v0.3. xchat-otr is quite new but already available in some distributions. In the
> > git repo you can also find weechat-otr which only works with the current
> > development version(0.2.7) of weechat. The whole project is now called "irc-otr"
> > and you can expect modules for other clients.
> 
> Thanks!  I've updated the software page on the website.

Great! Thank you!

Uli


From rainercg at yahoo.de  Mon Feb 23 05:42:56 2009
From: rainercg at yahoo.de (Rainer)
Date: Mon, 23 Feb 2009 11:42:56 +0100
Subject: [OTR-users] Communication with Pidgin to Miranda (or others) has
 encoding problemes
Message-ID: <49A27DB0.5030901@yahoo.de>

Hello!

I've experienced a problem during OTR encrypted communication between Pidgin
and Miranda (or other clients). In short: several characters are encoded as
HTML entities and so transmitted. E.g. an ampersand is sent as &amp; or a
newline is not the \n character (0x0A) but <br> instead. On the other way
round, messages from Miranda to Pidgin are displayed correctly, but written
HTML entities or tags like <br> will be extra parsed (so a newline is
displayed instead of "<br>").

The communication without OTR is fine, it's plain text transmitted (checked
the packages with Wireshark).

The whole problem is described on Pidgin's bugtracker. The answer was that
is has to be the problem of the third party plugin, namely Pidgin OTR.
Here it is, a longer description of the problem:

http://developer.pidgin.im/ticket/8453

OTR encrypted communication from Pidgin to other libpurple-based messengers
like Pidgin or Adium is fine.
I tested with an independent ICQ messenger (cliMM) with built-in OTR support
and received the same problems as with Miranda as the contact's client. I
also tested XMPP between Pidgin and Miranda: same thing.

The mystery is, Adium is like Pidgin based on libpurple, but has built-in
OTR support. No problems occur in communication to Miranda or cliMM. So I
isolated to problem to the combination Pidgin / OTR plugin.

Please try to help me or to identify the reason of this strange behaviour.


I'm using Pidgin 2.5.4 for Windows, but the same problem goes for the Linux
version. Pidgin OTR is in version 3.2.0.


Thanks for reading,
Rainer




From konrad at tylerc.org  Mon Feb 23 06:08:31 2009
From: konrad at tylerc.org (Conrad Meyer)
Date: Mon, 23 Feb 2009 03:08:31 -0800
Subject: [OTR-users] Communication with Pidgin to Miranda (or others)
	has encoding problemes
In-Reply-To: <49A27DB0.5030901@yahoo.de>
References: <49A27DB0.5030901@yahoo.de>
Message-ID: <200902230308.31627.konrad@tylerc.org>

On Monday 23 February 2009 02:42:56 am Rainer wrote:
> Hello!
>
> I've experienced a problem during OTR encrypted communication between
> Pidgin and Miranda (or other clients). In short: several characters are
> encoded as HTML entities and so transmitted. E.g. an ampersand is sent as
> &amp; or a newline is not the \n character (0x0A) but <br> instead. On the
> other way round, messages from Miranda to Pidgin are displayed correctly,
> but written HTML entities or tags like <br> will be extra parsed (so a
> newline is displayed instead of "<br>").
>
> Thanks for reading,
> Rainer

This is a well known pidgin bug, unrelated to OTR.

Regards,
-- 
Conrad Meyer <konrad at tylerc.org>



From js-otrim at webkeks.org  Mon Feb 23 07:09:47 2009
From: js-otrim at webkeks.org (Jonathan Schleifer)
Date: Mon, 23 Feb 2009 13:09:47 +0100
Subject: [OTR-users] Communication with Pidgin to Miranda (or others)
	has encoding problemes
In-Reply-To: <200902230308.31627.konrad@tylerc.org>
References: <49A27DB0.5030901@yahoo.de> <200902230308.31627.konrad@tylerc.org>
Message-ID: <4AD51613-C190-447F-9A3A-35A05858EEBA@webkeks.org>

Am 23.02.2009 um 12:08 schrieb Conrad Meyer:

> This is a well known pidgin bug, unrelated to OTR.

It is more or less a OTR bug as it doesn't specify whether the  
formatted text should be encrypted or the plaintext. This is  
especially a problem with Jabber, as some clients use HTML there and  
put it in the body - where it's not supposed to go. There's XHTML-IM  
for Jabber which uses a <body> in the XHTML namespace for it.

--
Jonathan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 801 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20090223/7a392264/attachment.pgp>

From paul at aurich.com  Mon Feb 23 14:57:36 2009
From: paul at aurich.com (Paul Aurich)
Date: Mon, 23 Feb 2009 11:57:36 -0800
Subject: [OTR-users] Communication with Pidgin to Miranda (or others)
 has encoding problemes
In-Reply-To: <49A27DB0.5030901@yahoo.de>
References: <49A27DB0.5030901@yahoo.de>
Message-ID: <49A2FFB0.6080704@aurich.com>

And Rainer spake on 02/23/2009 02:42 AM, saying:
> I've experienced a problem during OTR encrypted communication between Pidgin
> and Miranda (or other clients). In short: several characters are encoded as
> HTML entities and so transmitted. E.g. an ampersand is sent as &amp; or a
> newline is not the \n character (0x0A) but <br> instead. On the other way
> round, messages from Miranda to Pidgin are displayed correctly, but written
> HTML entities or tags like <br> will be extra parsed (so a newline is
> displayed instead of "<br>").

Your assumption that libpurple is entity-encoding the HTML entities and
transmitting them as such is fallacious.  They are *displayed* that way in
Miranda, but that is not evidence that they are transmitted as such.

>From gdb:
Breakpoint 1, process_sending_im (account=0x2c240a0, who=0x2cd1b70
"<redacted>",
    message=0x7ffffbf57e10, m=0x0) at otr-plugin.c:325
325	{
(gdb) p *message
$1 = 0x2cb4c60 "foobarzle<br><br>foobarzle"

As you can see, the message that OTR encrypts contains markup, not
entity-encoded stuff.

Now, as Jonathan pointed out, from a client writer's perspective, this is
entirely not the correct thing to do in many situations, since the receiver
is required to grok the arbitrary markup the sender's message contains.

> The communication without OTR is fine, it's plain text transmitted (checked
> the packages with Wireshark).

Yes, Miranda's XMPP plugin (mentioned further along in your message) does
not support XHTML-IM (based on a brief grep'ing of their code) and
libpurple strips all formatting from ICQ<>ICQ messages, so this is what you
would expect.

The real problem, as I see it, is that the libpurple sending-im signal is
triggered from libpurple's core and is sent before the protocols have
gotten a chance to munge the message into the format they want (plaintext
for ICQ, plaintext (+ optionally XHTML-IM) for XMPP, whole-buffer
formatting for MSN, etc). This means that the message contains markup when
the other side may not really want it.

Evan Schoenberg suggested one mechanism for fixing this (well, he was after
fixing AIM Direct Connect messages, but it could fix this, too) by having
the protocol plugins handle the signals [1], though I don't believe
anything was decided in that discussion. In addition (caveat: I'm not very
familiar with the crypto of OTR), I suspect a proper fix for XMPP to send
encrypted markup and encrypted plaintext in their appropriate elements
would require modifications to OTR, since only one of the two messages
would be handled by the receiver and I believe OTR doesn't handle dropped
messages well (someone correct me on this?).

In any event, the OTR specification apparently says the decrypted text can
contain HTML markup [2], so, even though I tend to agree with Jonathan on
this topic, the specification points toward this being a problem with
Miranda's implementation.

I'm unsure what Miranda should be doing for sending messages with markup,
though if the user literally types <br> in a message, my feeling is that
Miranda should be escaping that and sending &lt;br&gt;

~Paul

[1] http://pidgin.im/pipermail/devel/2008-December/007208.html
[2] http://lists.cypherpunks.ca/pipermail/otr-dev/2008-February/000744.html


From l-otr.0705+23jv-l at ruediger-kuhlmann.de  Mon Feb 23 15:26:59 2009
From: l-otr.0705+23jv-l at ruediger-kuhlmann.de (=?iso-8859-1?Q?R=FCdiger?= Kuhlmann)
Date: Mon, 23 Feb 2009 21:26:59 +0100
Subject: [OTR-users] [otr-users] Communication with Pidgin to Miranda
	(or others)	has encoding problemes
In-Reply-To: <49A2FFB0.6080704@aurich.com>
References: <49A27DB0.5030901@yahoo.de> <49A2FFB0.6080704@aurich.com>
Message-ID: <20090223202659.GB7754@msgids.ruediger-kuhlmann.de>

>--[Paul Aurich]--<paul at aurich.com>
> In any event, the OTR specification apparently says the decrypted text can
> contain HTML markup [2],

That may be true, but the README[1] specifically says that the text to be
encrypted is what ever format the protocol specified (there is no "convert
to XMPP-IM format" or anything like that), and since XMPP quite clearly
specifies that the body part contains plain text in UTF-8 (and not any HTML
markup), the text (that is then encrypted) put into the body tag may not
contain markup.

The comment from [2] is misleading, as of couse for protocols that define
the text to contain markup, the decrypted text can contain markup. It's
just that XMPP isn't one of them.

As such, the libpurple implementation is wrong, while Miranda and climm
are correct.

I remember that it was considered to change the lib to provide functions
to encode markup and non-markup in the next release, but I have no idea
what happened to it.

[1] http://www.cypherpunks.ca/otr/README-libotr-3.2.0.txt

-- 
"See, free nations are peaceful nations. Free nations don't attack
 each other. Free nations don't develop weapons of mass destruction."
      - George W. Bush, Milwaukee, Wis., Oct. 3, 2003


From paul at aurich.com  Mon Feb 23 16:57:19 2009
From: paul at aurich.com (Paul Aurich)
Date: Mon, 23 Feb 2009 13:57:19 -0800
Subject: [OTR-users] [otr-users] Communication with Pidgin to Miranda
 (or others)	has encoding problemes
In-Reply-To: <20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
References: <49A27DB0.5030901@yahoo.de> <49A2FFB0.6080704@aurich.com>
	<20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
Message-ID: <49A31BBF.9000002@aurich.com>

And R?diger Kuhlmann spake on 02/23/2009 12:26 PM, saying:
> That may be true, but the README[1] specifically says that the text to be
> encrypted is what ever format the protocol specified (there is no "convert
> to XMPP-IM format" or anything like that),

Could you point out where the README says that? I can't seem to find it.

> and since XMPP quite clearly
> specifies that the body part contains plain text in UTF-8 (and not any HTML
> markup), the text (that is then encrypted) put into the body tag may not
> contain markup.
> 
> The comment from [2] is misleading, as of couse for protocols that define
> the text to contain markup, the decrypted text can contain markup. It's
> just that XMPP isn't one of them.

The OTR specification to me, seems to be effectively protocol-agnostic
(except with regard to maximum message size and fragmentation), which is
unfortunate in this case, because it does not really address this (at
least, from my quick once-over) and states that the unencrypted text
(without qualification for "only some protocols") is "encoded in UTF-8,
optionally with HTML markup."

> As such, the libpurple implementation is wrong, while Miranda and climm
> are correct.

Then shouldn't Miranda and cliMM either be complaining vociferously that
they received an invalid XMPP stanza or displaying the markup (i.e., the
message from gdb in my previous message would appear as
"foobarzle<br><br>foobarzle" in Miranda/cliMM, not
"foobarzle&lt;br&gt;&lt;br&gt;foobarzle")?

> I remember that it was considered to change the lib to provide functions
> to encode markup and non-markup in the next release, but I have no idea
> what happened to it.

That sounds good. Will it allow for a single IM to contain two encrypted
payloads (one XHTML-IM, one plaintext)? I like the ability to send
marked-up text over OTR over XMPP.

Also, I'll repeat again: I'm of the opinion the libpurple OTR plugin's
current behavior is *wrong* from a "how should this protocol work in an
ideal world" perspective and unfairly relies on the receiver's client to
grok the markup and/or strip it, but to the best of my knowledge, that
isn't actually wrong according to the (underspecified, perhaps) OTR
specification, which says nothing about the unencrypted message needing to
conform to the rules of the protocol.

~Paul



From mail at scottellis.com.au  Mon Feb 23 17:49:01 2009
From: mail at scottellis.com.au (Scott Ellis)
Date: Tue, 24 Feb 2009 09:49:01 +1100
Subject: [OTR-users] [otr-users] Communication with Pidgin to Miranda
	(or others) has encoding problemes
In-Reply-To: <49A31BBF.9000002@aurich.com>
References: <49A27DB0.5030901@yahoo.de> <49A2FFB0.6080704@aurich.com>
	<20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
	<49A31BBF.9000002@aurich.com>
Message-ID: <96e269140902231449u3978e4cdvf270d830b8dd26b2@mail.gmail.com>

I've spoken about this at length a long while back.
At present there is another plugin for miranda called 'NoHtml' to help with
the problem.

2009/2/24 Paul Aurich <paul at aurich.com>

> And R?diger Kuhlmann spake on 02/23/2009 12:26 PM, saying:
> > That may be true, but the README[1] specifically says that the text to be
> > encrypted is what ever format the protocol specified (there is no
> "convert
> > to XMPP-IM format" or anything like that),
>
> Could you point out where the README says that? I can't seem to find it.
>
> > and since XMPP quite clearly
> > specifies that the body part contains plain text in UTF-8 (and not any
> HTML
> > markup), the text (that is then encrypted) put into the body tag may not
> > contain markup.
> >
> > The comment from [2] is misleading, as of couse for protocols that define
> > the text to contain markup, the decrypted text can contain markup. It's
> > just that XMPP isn't one of them.
>
> The OTR specification to me, seems to be effectively protocol-agnostic
> (except with regard to maximum message size and fragmentation), which is
> unfortunate in this case, because it does not really address this (at
> least, from my quick once-over) and states that the unencrypted text
> (without qualification for "only some protocols") is "encoded in UTF-8,
> optionally with HTML markup."
>
> > As such, the libpurple implementation is wrong, while Miranda and climm
> > are correct.
>
> Then shouldn't Miranda and cliMM either be complaining vociferously that
> they received an invalid XMPP stanza or displaying the markup (i.e., the
> message from gdb in my previous message would appear as
> "foobarzle<br><br>foobarzle" in Miranda/cliMM, not
> "foobarzle&lt;br&gt;&lt;br&gt;foobarzle")?
>
> > I remember that it was considered to change the lib to provide functions
> > to encode markup and non-markup in the next release, but I have no idea
> > what happened to it.
>
> That sounds good. Will it allow for a single IM to contain two encrypted
> payloads (one XHTML-IM, one plaintext)? I like the ability to send
> marked-up text over OTR over XMPP.
>
> Also, I'll repeat again: I'm of the opinion the libpurple OTR plugin's
> current behavior is *wrong* from a "how should this protocol work in an
> ideal world" perspective and unfairly relies on the receiver's client to
> grok the markup and/or strip it, but to the best of my knowledge, that
> isn't actually wrong according to the (underspecified, perhaps) OTR
> specification, which says nothing about the unencrypted message needing to
> conform to the rules of the protocol.
>
> ~Paul
>
> _______________________________________________
> OTR-users mailing list
> OTR-users at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20090224/3dcdfa92/attachment.html>

From rainercg at yahoo.de  Mon Feb 23 19:48:36 2009
From: rainercg at yahoo.de (Rainer)
Date: Tue, 24 Feb 2009 01:48:36 +0100
Subject: [OTR-users] [otr-users] Communication with Pidgin to Miranda
 (or others) has encoding problemes
In-Reply-To: <49A31BBF.9000002@aurich.com>
References: <49A27DB0.5030901@yahoo.de>
	<49A2FFB0.6080704@aurich.com>	<20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
	<49A31BBF.9000002@aurich.com>
Message-ID: <49A343E4.9070605@yahoo.de>

Paul Aurich wrote:
> The real problem, as I see it, is that the libpurple sending-im signal is
> triggered from libpurple's core and is sent before the protocols have
> gotten a chance to munge the message into the format they want (plaintext
> for ICQ, plaintext (+ optionally XHTML-IM) for XMPP, whole-buffer
> formatting for MSN, etc). This means that the message contains markup when
> the other side may not really want it.

I see... that's not how it should work, is it? I'm sending plain text
messages over ICQ with all possible combinations of sender/receiver clients,
there are no problems without OTR encryption. But there are some when
encrypting a message that SHOULD be without markup.

So is there a possibility to change the order of

1) encrypt written text
2) strip message to plain text

to 2) first, then 1)?
Seems to be either a Pidgin problem or a problem in the plugins's
implementation. If it's the latter, why are the developers deedless in spite
of a well known error?


>> As such, the libpurple implementation is wrong, while Miranda and climm
>> are correct.
> 
> Then shouldn't Miranda and cliMM either be complaining vociferously that
> they received an invalid XMPP stanza or displaying the markup (i.e., the
> message from gdb in my previous message would appear as
> "foobarzle<br><br>foobarzle" in Miranda/cliMM, not
> "foobarzle&lt;br&gt;&lt;br&gt;foobarzle")?

I could also ask why Pidgin is parsing such a message like
"foobar<br>newline" into a real new line, while there is no parsing when
sending a plain text message. Seems that Miranda/cliMM can handle messages
with markups but don't parse them. :(


Scott Ellis wrote:
> I've spoken about this at length a long while back.
> 
> At present there is another plugin for miranda called 'NoHtml' to help with the problem.

I'm sorry, but "NoHtml" does not help for this problem. At least not for me.
It is unparsing HTML tags like "<a href="this/is/a/url">Click</a>" into a
plain text or a BBcoded link. But it is not unparsing HTML entities like
&lt; or &quot;.


Bye,
Rainer Grabbe



From js-otrim at webkeks.org  Mon Feb 23 20:30:43 2009
From: js-otrim at webkeks.org (Jonathan Schleifer)
Date: Tue, 24 Feb 2009 02:30:43 +0100
Subject: [OTR-users] [otr-users] Communication with Pidgin to Miranda
	(or others)	has encoding problemes
In-Reply-To: <20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
References: <49A27DB0.5030901@yahoo.de> <49A2FFB0.6080704@aurich.com>
	<20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
Message-ID: <A5039D68-B20C-41C2-9522-80B48A2E94D4@webkeks.org>

Am 23.02.2009 um 21:26 schrieb R?diger Kuhlmann:

> That may be true, but the README[1] specifically says that the text  
> to be
> encrypted is what ever format the protocol specified (there is no  
> "convert
> to XMPP-IM format" or anything like that), and since XMPP quite  
> clearly
> specifies that the body part contains plain text in UTF-8 (and not  
> any HTML
> markup), the text (that is then encrypted) put into the body tag may  
> not
> contain markup.

Then you still got the problem that you get error strings from libotr  
containing markups. libotr's error handling is really the worst I can  
imagine. Basically, the client does not really know anything about the  
errors and just gets an HTML message telling the user what went wrong.  
Horrible!

--
Jonathan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 801 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20090224/980e5a03/attachment.pgp>

From rainercg at yahoo.de  Tue Feb 24 07:03:46 2009
From: rainercg at yahoo.de (Rainer)
Date: Tue, 24 Feb 2009 13:03:46 +0100
Subject: [OTR-users] [otr-users] Communication with Pidgin to Miranda
 (or others) has encoding problemes
In-Reply-To: <A5039D68-B20C-41C2-9522-80B48A2E94D4@webkeks.org>
References: <49A27DB0.5030901@yahoo.de>
	<49A2FFB0.6080704@aurich.com>	<20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
	<A5039D68-B20C-41C2-9522-80B48A2E94D4@webkeks.org>
Message-ID: <49A3E222.20408@yahoo.de>

Hello!

I found a solution in otr-dev mailing list:
http://lists.cypherpunks.ca/pipermail/otr-dev/2009-January/000985.html

The patch applied to otr-plugin.c leads to correct order, first striping
HTML to plain text, then encrypting it. At least this is what it seems to me
because Miranda displays the correct content. No more HTML entities, no <br>
instead of a new line. :)

My only "problem" is that my improved pidgin-otr.dll is about 2500KB in
size, whereas the original one is 413KB. But that's another story... (if
someone knows a solution, please e-mail me directly)

Thanks for helping and maybe there's a pidgin-otr 3.2.1 in the future. ;)


Bye,
Rainer Grabbe




From js-otrim at webkeks.org  Tue Feb 24 10:10:59 2009
From: js-otrim at webkeks.org (Jonathan Schleifer)
Date: Tue, 24 Feb 2009 16:10:59 +0100
Subject: [OTR-users] [otr-users] Communication with Pidgin to Miranda
	(or others) has encoding problemes
In-Reply-To: <49A3E222.20408@yahoo.de>
References: <49A27DB0.5030901@yahoo.de>
	<49A2FFB0.6080704@aurich.com>	<20090223202659.GB7754@msgids.ruediger-kuhlmann.de>
	<A5039D68-B20C-41C2-9522-80B48A2E94D4@webkeks.org>
	<49A3E222.20408@yahoo.de>
Message-ID: <E547B72E-D664-42E9-991D-4F8B6587FF68@webkeks.org>

Am 24.02.2009 um 13:03 schrieb Rainer:

> My only "problem" is that my improved pidgin-otr.dll is about 2500KB  
> in
> size, whereas the original one is 413KB. But that's another story...  
> (if
> someone knows a solution, please e-mail me directly)

mingw32-strip pidgin-otr.dll

--
Jonathan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 801 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20090224/3600fa16/attachment.pgp>

From ananda.samaddar at vfemail.net  Wed Feb 25 06:01:10 2009
From: ananda.samaddar at vfemail.net (Ananda Samaddar)
Date: Wed, 25 Feb 2009 11:01:10 +0000
Subject: [OTR-users] Pidgin and OTR install guide
Message-ID: <20090225110110.33fc25e0@ananda-desktop>

I'm working on a Pidgin and OTR user guide.  This is being written in
LyX and has screenshots.  I'm hoping that this can become an 'official'
guide as the docs on the OTR site are inadequate and out of date in my
opinion.

I will let you know when it's finished and hopefully you can modify it
and upload it to the OTR site.  Because I'm using LyX it can easily be
converted to LaTeX or html.

I believe Richard Stallman when he says that free software is useless
without good free documentation.  Also since I live in one of the most
surveillance happy country in the world - the UK - I'd like to see
widespread use of privacy technologies. I'll probably put my efforts in
to the public domain so it can be used for any purpose.

I'd like to hear the OTR maintainers' thoughts on these issues.

thanks,

Ananda Samaddar


From otrs at exby.com  Thu Feb 26 08:36:00 2009
From: otrs at exby.com (Dave E)
Date: Thu, 26 Feb 2009 08:36:00 -0500
Subject: [OTR-users] I can't read my own encrypted Pidgin messages
Message-ID: <1956e3fd0902260536u70791f8eq4311dab06ddd6f1d@mail.gmail.com>

I've been having a problem recently. Here is my system info:

OS: Fedora release 10 (Cambridge),  2.6.27.15-170.2.24.fc10.i686 #1 SMP
Pidgin: 2.5.4-1.fc10
OTRS: 3.2.0

When communicating with individuals who have verified me and I them - I
cannot read my own messages in the message window after I send to them. The
message looks like if you try to read an encrypted message without OTRS.

I can read my buddies IMs just fine, and they can see mine, but as for me
seeing my own - doesn't work. I had this same issue on another machine with
very similar specs to the ones above. This machine is a brand new
installation and it actually *worked* when I first installed pidgin, and
otrs. Then after a reboot, I believe, is where I started having this
problem.

Any direction/suggestions would be much appreciated...this is a pretty
sizable pain. Thanks.

DE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20090226/c2573cc6/attachment.html>

From andrei at srr.ro  Fri Feb 27 03:22:01 2009
From: andrei at srr.ro (Andrei Boros)
Date: Fri, 27 Feb 2009 10:22:01 +0200
Subject: [OTR-users] I can't read my own encrypted Pidgin messages
In-Reply-To: <1956e3fd0902260536u70791f8eq4311dab06ddd6f1d@mail.gmail.com>
References: <1956e3fd0902260536u70791f8eq4311dab06ddd6f1d@mail.gmail.com>
Message-ID: <49A7A2A9.5060503@srr.ro>

See if you disable some of the plugins.

I had the same problem because of the "message splitter" plugin which
splits outgoing message so that it does not exceed a certain limit per
message.

Dave E wrote:
> I've been having a problem recently. Here is my system info:
>
> OS: Fedora release 10 (Cambridge),  2.6.27.15-170.2.24.fc10.i686 #1 SMP
> Pidgin: 2.5.4-1.fc10
> OTRS: 3.2.0
>
> When communicating with individuals who have verified me and I them -
> I cannot read my own messages in the message window after I send to
> them. The message looks like if you try to read an encrypted message
> without OTRS.
>
> I can read my buddies IMs just fine, and they can see mine, but as for
> me seeing my own - doesn't work. I had this same issue on another
> machine with very similar specs to the ones above. This machine is a
> brand new installation and it actually *worked* when I first installed
> pidgin, and otrs. Then after a reboot, I believe, is where I started
> having this problem.
>
> Any direction/suggestions would be much appreciated...this is a pretty
> sizable pain. Thanks.
>
> DE
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> OTR-users mailing list
> OTR-users at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-users
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20090227/41ec9bb8/attachment.html>

From otrs at exby.com  Fri Feb 27 08:47:56 2009
From: otrs at exby.com (Dave E)
Date: Fri, 27 Feb 2009 08:47:56 -0500
Subject: [OTR-users] I can't read my own encrypted Pidgin messages
In-Reply-To: <49A7A2A9.5060503@srr.ro>
References: <1956e3fd0902260536u70791f8eq4311dab06ddd6f1d@mail.gmail.com>
	<49A7A2A9.5060503@srr.ro>
Message-ID: <1956e3fd0902270547w782f4685k117529c5a0d097bd@mail.gmail.com>

That was it. The message splitter plugin was causing the problem on every
message, not just the ones that needed to be split. Thanks!

On Fri, Feb 27, 2009 at 3:22 AM, Andrei Boros <andrei at srr.ro> wrote:

>  See if you disable some of the plugins.
>
> I had the same problem because of the "message splitter" plugin which
> splits outgoing message so that it does not exceed a certain limit per
> message.
>
> Dave E wrote:
>
> I've been having a problem recently. Here is my system info:
>
> OS: Fedora release 10 (Cambridge),  2.6.27.15-170.2.24.fc10.i686 #1 SMP
> Pidgin: 2.5.4-1.fc10
> OTRS: 3.2.0
>
> When communicating with individuals who have verified me and I them - I
> cannot read my own messages in the message window after I send to them. The
> message looks like if you try to read an encrypted message without OTRS.
>
> I can read my buddies IMs just fine, and they can see mine, but as for me
> seeing my own - doesn't work. I had this same issue on another machine with
> very similar specs to the ones above. This machine is a brand new
> installation and it actually *worked* when I first installed pidgin, and
> otrs. Then after a reboot, I believe, is where I started having this
> problem.
>
> Any direction/suggestions would be much appreciated...this is a pretty
> sizable pain. Thanks.
>
> DE
>
> ------------------------------
>
> _______________________________________________
> OTR-users mailing listOTR-users at lists.cypherpunks.cahttp://lists.cypherpunks.ca/mailman/listinfo/otr-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20090227/fae694c2/attachment.html>

From gmaxwell at gmail.com  Fri Feb 27 09:14:12 2009
From: gmaxwell at gmail.com (Gregory Maxwell)
Date: Fri, 27 Feb 2009 09:14:12 -0500
Subject: [OTR-users] I can't read my own encrypted Pidgin messages
In-Reply-To: <1956e3fd0902270547w782f4685k117529c5a0d097bd@mail.gmail.com>
References: <1956e3fd0902260536u70791f8eq4311dab06ddd6f1d@mail.gmail.com>
	<49A7A2A9.5060503@srr.ro>
	<1956e3fd0902270547w782f4685k117529c5a0d097bd@mail.gmail.com>
Message-ID: <e692861c0902270614n55df95dq59636ff22bff2e5d@mail.gmail.com>

On Fri, Feb 27, 2009 at 8:47 AM, Dave E <otrs at exby.com> wrote:
> That was it. The message splitter plugin was causing the problem on every
> message, not just the ones that needed to be split. Thanks!

OTR does its own fragmentation, so I don't think you need that plugin
if you convince all your contacts to install OTR. :)