[OTR-dev] Reccomended version of libgcrypt? Libotr status messages.

[Ian Goldberg]

On Wed, Jul 22, 2009 at 04:07:14PM +0200, Jonathan Schleifer wrote:
> Ian Goldberg <ian at cypherpunks.ca> wrote:
> 
> > Both of these issues relate to constant strings in libotr.  Those have
> > been removed in the development version of the library (for exactly
> > the reasons you identify), currently checked into CVS at
> > sourceforge.  If you want to use the last release, editing the
> > strings is probably the best you can do, or you can see if you can
> > use the CVS version of the API.
> 
> Good to hear that - we might implement OTR again in Gajim if this is
> really a clean design now.

I'd actually love to get your feedback on whether what's in CVS now
would work for you.

> One question though: Would it be possible to encrypt whole stanzas
> maybe in a way that is still compatible with transports? For example
> you encrypt the body in a way that is backwards-compatible and then you
> encrypt additional tags that can be attached to a message (like
> XHTML-IM) separately, which are then only handled if the client on the
> other side is a Jabber client.

Sorry, I'm not following.  Can you give an example?

Thanks,

   - Ian