Ticket #544 (closed enhancement: fixed)

Opened 5 years ago

Last modified 2 years ago

ESessions JEP (unjargoned encryption)

Reported by: stellaris@… Owned by: bct
Priority: normal Milestone: 0.12
Component: None Version:
Severity: major Keywords: encryption
Cc: steve-e Blocked By:
OS: All Blocking:

Description (last modified by nk) (diff)

 http://www.jabber.org/jeps/jep-0116.html

Attachments

Change History

  Changed 5 years ago by nk

  • owner changed from asterix to nk
  • priority changed from normal to lowest
  • severity changed from major to minor

yes we plan to do that. we need a python wrapper to libotr (C). an alpha is here  http://continuity.notcows.com/~retrev/PyOTR/ if you wanna play :)

  Changed 5 years ago by stellaris@…

yay!

follow-up: ↓ 11   Changed 5 years ago by gajim@…

I would strongly suggest you check on what is being done on the standards front in the Jabber community here. There is a dedicated mailinglist for security aspects in XMPP. On of the subscribers suggested to write an OTR JEP, but came back from this because of what Peter Saint-Andre is working on in  ESessions (JEP-0116). His work incorporates the best things in OTR.

You can read the archives of the xmppsec mailinglist here:  http://mail.jabber.org/pipermail/xmppsec/, and discuss JEP-0116 on the standards-jig mailinglist.

-- Ralph Meijer

  Changed 5 years ago by nk

hello Ralph and thanks for your comments.

I'm aware of psa trying to merge all the goods in esessions.

This ticket is not high prio atm, so we can wait and see what happens

  Changed 5 years ago by nk

  • description modified (diff)
  • summary changed from Off The Record encryption to ESessions JEP (unjargoned encryption)

  Changed 4 years ago by nk

  • owner changed from nk to asterix

  Changed 4 years ago by jim++

  • type changed from defect to enhancement

  Changed 4 years ago by gromobir

Replying to stellaris@h3c.de:

>  http://www.jabber.org/jeps/jep-0116.html

Hello, I just wanted to ask if you are working to implement this JEP or not? It really would be great to see OTR working with gajim. It would be fantastic if the gajim OTR implemantation would be compatible with other Clients (such as Miranda OTR plugin or gaim OTR plugin). Keep on the good work. :-)

  Changed 4 years ago by asterix

nothing is done nor planned about that. But this will come one day ...

  Changed 4 years ago by jim++

  • type changed from defect to enhancement

in reply to: ↑ 3   Changed 4 years ago by anonymous

While the standards work on JEP is encouraging, I think that there is value in looking at OTR itself since it plays nicely with other networks. I understand that Gajim is Jabber only, but being able to support end to end encryption even through transports is an important part of IM security.

Replying to gajim@ralphm.ik.nu:

I would strongly suggest you check on what is being done on the standards front in the Jabber community here.

  Changed 4 years ago by anonymous

  • milestone set to 0.12

  Changed 3 years ago by Brendan Taylor

  • os set to All

I will be working on this as part of GSoC 2007.

  Changed 3 years ago by steve-e

  • cc steve-e added

  Changed 3 years ago by steve-e

Do you have got a weblog or how can we keep up with your work?

  Changed 3 years ago by anonymous

  • priority changed from lowest to normal
  • owner changed from asterix to bct
  • severity changed from minor to major

  Changed 3 years ago by asterix

  • status changed from new to closed
  • resolution set to fixed

(In [20fa0908829cd0fe01f23960ed7d1c4eb4b38f18]) [Brendan Taylor] Gsoc 2007 work : end to end encryptions. Fixes #544

  Changed 2 years ago by misery

FYI: Added a feature request to pidgin for ESession-Support.  http://developer.pidgin.im/ticket/5225

  Changed 2 years ago by misery

Meta-Tracking:  https://bugs.launchpad.net/ubuntu/+bug/202557

Add/Change #544 (ESessions JEP (unjargoned encryption))

Author


E-mail address and user name can be saved in the Preferences.


Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Next status will be 'needinfo'
 
Note: See TracTickets for help on using tickets.