"it doesn't work" is too vague plus Bugzilla is not a support forum for
general software development question. There are many pages out there
which explain how to compile software... Thanks for your understanding.
--
You received this bug notification because you are a member of Desktop
@Xavier: Can't you provide us, at very least, a small tutorial showing
how to compile this with the latest empathy build? Because it doesn't
work.
If not - I donated years ago for this to be implemented, so I'll want my
money back. :P
--
You received this bug notification because you are a
** Changed in: libtelepathy
Importance: Wishlist => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR encryption
Status in
No idea - I've long migrated to software which cares enough about
security not to have critical bugs opened for 5 years.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
Anyone still working on getting this into released empathy ?
Thanks,
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR encryption
Status in
In regards to my previous comment. I discovered enable-otr is in
/src/connection.c, once you get the right branch...
git clone git://people.freedesktop.org/~smcv/telepathy-gabble
git checkout untested-otr
I also tried setting the default FALSE option to TRUE. Still OTR
doesn't work for me,
(In reply to Xavier Claessens from comment #99)
You probably want python2. Build just fine on ubuntu 15.04, it just has a
warning for a deprecated gnutls function, but you can ignore that with
--disable-Werror (or make a fix).
sudo apt-get build-dep telepathy-gabble
./autogen.sh
You probably want python2. Build just fine on ubuntu 15.04, it just has
a warning for a deprecated gnutls function, but you can ignore that with
--disable-Werror (or make a fix).
sudo apt-get build-dep telepathy-gabble
./autogen.sh --disable-Werror
make
make install
--
You received this bug
(In reply to JKAbrams from comment #93)
What is the status of this project? Is it dead?
More like (deliberately?) ignored. When most all the work is done, and
working patches exist you have to wonder...
--
You received this bug notification because you are a member of Desktop
Packages, which
Xavier, I'm happy to pay you now. PayPal to email?
Sam
On 2 Jun 2015 21:01, Xavier Claessens xclae...@gmail.com wrote:
There are patches, there are review comments, and 55 subscribers to this
bug. If only one of you could just work on it instead of complaining...
--
You received this bug
See comment #81 for the few items missing. As far as I'm concerned it
can be merged if someone just fix those, and it's close to trivial to do
IIRC.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
In the year 2015, this should have priority highest not medium (and
certainly not ignore).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR
There are patches, there are review comments, and 55 subscribers to this
bug. If only one of you could just work on it instead of complaining...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
(In reply to Xavier Claessens from comment #97)
See comment #81 for the few items missing. As far as I'm concerned it can be
merged if someone just fix those, and it's close to trivial to do IIRC.
Seeing as the compile process isn't well documented, it's very confusing
for newcomers. If you'll
How will this be marked as complete on freedomsponsors? How do we pay
Xavier?
Sam
On Tue, Jun 2, 2015 at 2:32 PM, G4JC 296...@bugs.launchpad.net wrote:
Just so everyone knows, this has been completed quite some time ago via
a bounty developer on FreedomSponsors.
However, upstream is
Just so everyone knows, this has been completed quite some time ago via
a bounty developer on FreedomSponsors.
However, upstream is furiously continuing to ignore the patch and keep their
users insecure.
Source of upstream stupidity:
https://bugs.freedesktop.org/show_bug.cgi?id=16891#c46
Read
Ick! If telepathy makes doing OTR securely impossible, that's very bad
news.
We should lobby to remove Empathy and telepathy from Debian stable and
Ubuntu then. OTR is critical post Snowden.
--
You received this bug notification because you are a member of Desktop
Packages, which is
As good as dead if you care about security. Luckily there are plethora
of alternatives out there with OTR support. See http://otr.im for
details.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
What is the status of this project? Is it dead?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR encryption
Status in Chat app, and
(In reply to comment #91)
Realization of the first three points would require adding a new interface
to gabble. I imagine it as an extension of connection interface providing
settings individually for every account. Would using gdbus codegen just
like in case of the currently implemented otr
Hi
I am currently working on OTR support for KDE Telepathy. There are some
features we would like to have:
- otr policy settings
- a way to generate a new private key for account
- possibility to manage known fingerprints (trust/distrust)
- two additional ways of peer authentication (shared
As far as I understood it can used with gnome-chat or whatever client
using telepathy library - once it's upstreamed of course.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
(In reply to comment #88)
As far as I understood it can used with gnome-chat or whatever client using
telepathy library - once it's upstreamed of course.
Ah, that's great! Also, why was it necessary to make it protocol-
specific? OTR is supposed to be useful for any sychronous messaging
--
(In reply to comment #87)
Why is the patch protocol-specific?
Telepathy does not have any central point where OTR can be done for all
protocols and all UIs simultaneously. We can either do it once per
protocol backend, or once per UI. Once per UI would break the ability to
log OTR messages or
Why is the patch protocol-specific?
Would it be possible to use the same code for the new gnome-chat
application which will likely replace Empathy?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
(In reply to comment #83)
I did manage to start a session using Xavier's branch but noticed the
following bug:
- Start an OTR session between Empathy and Pidgin
- In Pidgin using the OTR menu pick End private conversation
- Try sending a message from Empathy. The message doesn't reach Pidgin
(In reply to comment #83)
I did not manage to start an OTR session with this branch.
The '/otr start' command was displaying OTR:$blob in empathy-chat.
You need to set enable-otr=true in your CM parameters, otherwise OTR
is disabled in Simon's branch. There is magic mc-tool command for that,
(In reply to comment #76)
1) handle html, I'm not sure to understand what you mean or why it is that
important... Maybe you can make the changes that you want?
Looking into it. The more important direction (don't send plain text
where HTML is expected, so that parts of messages that happen to
(In reply to comment #58)
+ type=(say) access=read
Are these literally the hex and binary versions of the same digest, or do
they have different information content? (Or is the string version some
OTR-specific thing that is easier to transcribe than hex?)
I'm not particularly happy about
Security issue: it isn't at all clear to me what trust means here. In
something like GPG or SSL, the trusted assertion is the key whose
fingerprint is ...63c7cc90 is controlled by 'Simon McVittie
simon.mcvit...@collabora.co.uk' or the key whose fingerprint is ...
is controlled by the
(In reply to comment #78)
In particular, we don't seem to
be binding a fingerprint to a JID.
On closer inspection of libotr, it seems we are indeed binding a (remote
username, local account name, protocol) tuple to a fingerprint; the API
just doesn't make that obvious.
--
You received this
I've made most of the changes I wanted but haven't had time to test them
yet. Use at own risk:
http://cgit.freedesktop.org/~smcv/telepathy-gabble/log/?h=untested-otr
Still to do:
* testing (in particular, send lt; and a message that resembles HTML
in both directions between Empathy and
fp_data = g_variant_get_data (fp_variant);
fp = otrl_context_find_fingerprint (context, (guchar *) fp_data, 0, NULL);
I'm still considering use string fingerprints with error-checking to
be a merge blocker, because I don't think this code is OK for the case
where fp_data has length != 20
(In reply to comment #81)
I've made most of the changes I wanted but haven't had time to test them
yet. Use at own risk:
http://cgit.freedesktop.org/~smcv/telepathy-gabble/log/?h=untested-otr
I did not manage to start an OTR session with this branch.
The '/otr start' command was displaying
(In reply to comment #83)
I did manage to start a session using Xavier's branch but noticed the
following bug:
- Start an OTR session between Empathy and Pidgin
- In Pidgin using the OTR menu pick End private conversation
- Try sending a message from Empathy. The message doesn't reach Pidgin
(In reply to comment #54)
trust_level_to_str(): I'd mention encrypt using OTR to be clearer and
avoid confusion my server encryption.
Fixed.
return _(The conversation is currently unencrypted.);
I'd say unencrypted with OTR to stay coherent and crystal clear.
Your branch looks good to
From a (very) quick look on the Gabble branch, it seems that all the
channel messages are now sent through OTR (if built with it), even when
it has not been activated. Is that really what we want?
Also, shouldn't we use it only for contact channels?
--
You received this bug notification because
(In reply to comment #56)
From a (very) quick look on the Gabble branch, it seems that all the channel
messages are now sent through OTR (if built with it), even when it has not
been activated. Is that really what we want?
Yes, that's what pidgin-otr does as well. That's because all received
Just doing the spec right now:
The extra DBus channel interface is implemented using GDBus
so it needs to be exported on a different bus name.
Ugh. Can we not do strange hacks like this, please? Either use the
extensions mechanism, or save it for 1.0.
+ interface
(In reply to comment #50)
Could we also get a config option that turns this whole feature on/off? I
ask because some industries (like the one where I work) require that all
electronic communications related to the business get recorded and reviewed
by compliance officers and made available to
Implementation in Gabble:
+ /* FIXME: There should be no sender for a notification, but setting handle to
+ * 0 makes empathy crash atm. */
+ tp_message_mixin_take_received (G_OBJECT (self),
+ tp_cm_message_new_text (base_conn,
+ tp_base_channel_get_target_handle (base_chan),
+
I would really like im-channel to implement o.fd.Telepathy.Securable -
as a starting point we can have the two booleans not be requestable, and
just have them set by the OTR code calling a new
gabble_im_channel_indicate_security
(GABBLE_SECURABLE_ENCRYPTED|GABBLE_SECURABLE_VERIFIED) (or only one
Corner cases:
What happens when we try to send a message and the channel is already
TRUST_FINISHED? I think we should refuse, for the rest of the lifetime
of that channel (until Close()), to avoid the security flaw where we
send messages to a channel that just closed.
What happens when we close
(In reply to comment #59)
Ideally, that distinctive message header should be a machine-readable
version of the message, so OTR-literate UIs (Empathy) can discard the
untranslated version from Gabble and display something translated. We've
always had a policy of putting UI strings and their
(In reply to comment #58)
Just doing the spec right now:
The extra DBus channel interface is implemented using GDBus
so it needs to be exported on a different bus name.
Ugh. Can we not do strange hacks like this, please? Either use the
extensions mechanism, or save it for 1.0.
I don't
+static void
+otr_handle_smp_event (void *opdata,
+ OtrlSMPEvent smp_event,
+ ConnContext *context,
+ unsigned short progress_percent,
+ gchar *question)
+{
+ DEBUG (UNIMPLEMENTED\n);
+}
Is this OK/allowed? Should we at least tell libotr no, I don't
implement SMP?
--
You received this bug
en_GB speaker review of strings:
+ notify (self, _(An error occurred when encrypting your message and
+ not sent.));
This sentence no verb.
Maybe ... and it was not sent?
+ notify (self, _(Your message was not sent because %s closed their
+ connection. Either close your private connection,
After fixing the obvious things, it would also be good to get someone
who understands the OTR protocol and/or libotr to review this
(particularly the things I raised in Comment #59 and Comment #62). I
don't think there's any such person among the main Telepathy developers,
but perhaps one of the
A brief glance at Empathy:
+ return _(The conversation is currently encrypted with
+ OTR but the remote contact has not been
+ authentified);
There is no such word. I think you mean authenticated and/or
identified.
--
You received this bug notification because you are a member of Desktop
(In reply to comment #60)
(In reply to comment #50)
Could we also get a config option that turns this whole feature on/off? I
ask because some industries (like the one where I work) require that all
electronic communications related to the business get recorded and reviewed
by compliance
(In reply to comment #61)
I would really like im-channel to implement o.fd.Telepathy.Securable - as a
starting point we can have the two booleans not be requestable, and just
have them set by the OTR code calling a new
gabble_im_channel_indicate_security
** Bug watch added: GNOME Bug Tracker #729762
https://bugzilla.gnome.org/show_bug.cgi?id=729762
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to
(In reply to comment #68)
It doesn't matter, if the message is in the form ?OTR:base64 then it
puts new_content to whatever the original message was (html or not). OTR
doesn't change anything if user wants to send html message as plaintext,
empathy will escape when displaying them.
Are you
(In reply to comment #68)
I can change the iface name but it doesn't matter much. I would like to
avoid extensions/ nightmare though, I don't want to write code using that in
master and port it again in next.
OK. I still would prefer to use o.fd.T for the 0.x version though.
This deserves a
(In reply to comment #69)
It can be done later. ATM the policy is MANUAL and it's the right thing
until we have an explicit option. I would consider this non-blocker future
enhancement.
That's OK, but only if MANUAL specifically means do not initiate *or
accept* OTR sessions without user
(In reply to comment #62)
Corner cases:
What happens when we try to send a message and the channel is already
TRUST_FINISHED? I think we should refuse, for the rest of the lifetime of
that channel (until Close()), to avoid the security flaw where we send
messages to a channel that just
(In reply to comment #71)
It currently
cannot go back to NOT_PRIVATE because I don't support ending the otr
session, but could add a /otr end for that. pidgin can do that.
Please don't. In Pidgin, maybe that feature is OK, because typically only
one UI handles a window (Pidgin's D-Bus
Voilà, added commits to fix most of your comments. What's missing:
1) handle html, I'm not sure to understand what you mean or why it is
that important... Maybe you can make the changes that you want?
2) Find a solution if we don't want the other end to be able to initiate
an OTR session without
(In reply to comment #46)
Empathy: http://cgit.collabora.com/git/user/xclaesse/empathy.git/log/?h=otr
Ok for the first commit.
Second commit:
+ tuple = empathy_gdbus_channel_interface_otr1_get_remote_fingerprint (
+ priv-otr_proxy);
I have no idea how these new generated
(In reply to comment #53)
(In reply to comment #46)
Empathy: http://cgit.collabora.com/git/user/xclaesse/empathy.git/log/?h=otr
Ok for the first commit.
Second commit:
+ tuple = empathy_gdbus_channel_interface_otr1_get_remote_fingerprint (
+ priv-otr_proxy);
I have no
(In reply to comment #51)
The conversation won't be encrypted until you type /otr start or if the
other side request a private conversation. So you should be fine AFAIK.
Actually I was wrong, when both sides are OTR-aware, it initialize
itself without an explicit user request. I changed the
I just logged in to say thank you! I am so happy to see this eventually
finished. Thank you so much. :)
Hope to see this soon merged into mainline. Thanks again :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
Could we also get a config option that turns this whole feature on/off?
I ask because some industries (like the one where I work) require that
all electronic communications related to the business get recorded and
reviewed by compliance officers and made available to regulatory
agencies upon
The conversation won't be encrypted until you type /otr start or if
the other side request a private conversation. So you should be fine
AFAIK.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
Just because the conversation is encrypted end to end doesnt mean you
cant log locally. Dont know how empathy does this, but in pidgin it can
be set up easily. There is even an option to omiss the conversations
that are encrypted.
I dont really like that distinction, because it implies all
Here it is! It is limited to XMPP, and empathy has only rudimentary UI.
To start an OTR session, in empathy chat window, type /otr start. Type
/help otr to see other supported otr actions. There is no graphical UI
atm.
Notably, to authenticate the other end, you need to verify its
fingerprint by
Big thanks Xavier.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR encryption
Status in Chat app, and Telepathy user interface:
Confirmed
Commits relevant for telepathy-gabble:
http://cgit.collabora.com/git/user/xclaesse/telepathy-
gabble.git/commit/?h=otrid=4addae9f4173eb3ed19581c1201fecc43a405fc6
Commits relevant for empathy:
This is fantastic news Xavier. Thank you for your hard work - this
proves that crowd funding great ideas works! Now GNOME project will be
able to celebrate Reset The Net on June 5th. Someone should nominate!
https://www.resetthenet.org/
--
You received this bug notification because you are a
Complaints show fear, anger ungratefulness while calm feature requests
show peace, gratefulness understanding of a problem.
Community giving of FOSS shows kindness compassion, while taking
complaining shows an unsatisfied desire for control.
True control lies in harmonising with the
Disturbingly that applies as much to Monsanto as it does to Ubuntu or FOSS.
On 30 Apr 2014 07:15, James Cuzella trinitr...@gmail.com wrote:
Complaints show fear, anger ungratefulness while calm feature requests
show peace, gratefulness understanding of a problem.
Community giving of FOSS
After all that NSA, PRISM, etc, scandal, I don't want to imagine the silly face
Telepathy's developers who stated so arrogantly that security wasn't very
important must have every morning. They thought that critic users who were
demanding security were little less than intellectually retarded
I think most people take it for granted that telepathy devs are on the dark
side - even the name of the project gives it away!
Telepathy is for other people to read your thoughts.
But it's bad manners to bring it up on the bug report list.
On 28 Apr 2014 17:51, Bugzi 296...@bugs.launchpad.net
I'm fed up of people complaining about developers. It's *free software*,
and if you get anything more than you paid for then you should be
grateful (I certainly am).
This is doubly so considering all the criticism that has gone the way of
the OpenSSL people in the wake of Heartbleed. When someone
Well, my issue isn't how the devs choose to spend their time, but the
extremely hostile and dismissive attitude they took towards security and
privacy when they have addressed this bug/feature request/feature.
I haven't paid them, they are not obligated to me, I am disturbed that
Ubuntu would
I'm feed up of people complaining about people complaining about wilful bad
security.
This is doubly so considering all the criticism that has gone the way of
the OpenSSL people in the wake of Heartbleed.
A little more discussion there might have helped, but here it obviously
hasn't!
When
I'm not complaining about people who spend time auditing security
software and finding these bugs making their discoveries known - even if
they are less than polite while doing so. (I myself am taking maximum
advantage of the opportunity to poke fun at ridiculous or borderline
fraudulent
I think people are trying provoke a post-Snowden comment from the devs or
Ubuntu.
This uncomfortable discussion has an important social role in establishing
or restoring or writing off credibility.
Pre-Snowden the official position seemed incredible, but potentially
honestly held.
It may even
Please bump the priority for this. If you can't add OTR support then
please give instructions how to add a plugin. I've been waiting
patiently for several years for this support. I was thrilled to see an
IM client get audio and video support on Linux. Now it's time to get
encryption. We have the
I also feel that Canonical should be funding this or providing
developers since they made it the default for Ubuntu and exposed all
their users to sending cleartext personal info over the internet.
--
You received this bug notification because you are a member of Desktop
Packages, which is
From comments when this first arose, the empathy developers were not
interested in something that was interoperable with OTR, but might,
someday, be interested in their own unique snowflake of an encryption
system.
I'm not a coder, but OTR is out there, works, and plays well with others.
They
Now it's time to get encryption
I also feel that Canonical should be funding
They really ought to make it work in empathy
Because open source is all about freedom. The freedom to demand that other
people should do free work for you.
Sorry, these comments are not helpful.
--
You received
Updated URL for JPRvita's Spec: https://gitorious.org/jprvita-repos
/telepathy-gabble/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR
Sorry I had tested that previously, but I guess i had missed some of the URL on
paste. Basicly JPRvita's spec was much farther along then mine and is a more
complete spec.
https://gitorious.org/jprvita-repos/telepathy-gabble/source/master:
https://gitorious.org/jprvita-repos/telepathy-gabble/
@Jordan F, why did you remove a working link and replace it with a
broken one?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR encryption
Sad to see that wolfrage stop his work on this bug.
No reply from Telepathy's developers. Security is no one of our goal ??
https://bugs.launchpad.net/ubuntu/+source/libtelepathy/+bug/296867/comments/170
--
You received this bug notification because you are a member of Desktop
Packages, which
I think they are waiting for a clean well specified standard maybe
with nsa approved security ;-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to
(In reply to comment #40)
(In reply to comment #39)
No reply from Telepathy's developers. Security is no one of our goal ??
Ah, it's our goal (good ol' royal we), but it's Telepathy's developers
who should work on it. Have you considered to continue working on the patch
if this goal is so
(In reply to comment #39)
No reply from Telepathy's developers. Security is no one of our goal ??
Ah, it's our goal (good ol' royal we), but it's Telepathy's
developers who should work on it. Have you considered to continue
working on the patch if this goal is so important to you?
--
You
I am sorry if you feel that I have disappeared. I did not intend it that
way. I did what I could to help. The developers of empathy stated that
they could not implement OTR unless they had a spec first. They also
forced the issue that my spec had to include XTLS. I am only a novice
programer and
https://freedomsponsors.org/core/issue/333/telepathy-should-support-otr-
encryption
$942
Maybe someone is willing to spend some time on this. I tried at a point
to gather some support, but well the core developers of empathy believe
OTR is a bad idea, and well jprvita is not willing to continue
Note that freedomsponsors somehow changed their urls, old link is 404
now, new link is http://freedomsponsors.org/core/issue/333/telepathy-
should-support-otr-encryption (currently at US$ 575)
--
You received this bug notification because you are a member of Desktop
Packages, which is
(In reply to comment #36)
For the record, here is a thread summarising the design issues regarding
end-to-end security in Telepathy:
http://lists.freedesktop.org/archives/telepathy/2012-June/006122.html
Also, don't forget about the ZRTP option, as discussed in the Bug
#29904.
--
You received
** Tags removed: 12.10
** Tags added: 14.04
** Tags added: im
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/296867
Title:
empathy needs to support OTR encryption
Status in Chat
For the record, here is a thread summarising the design issues regarding
end-to-end security in Telepathy:
http://lists.freedesktop.org/archives/telepathy/2012-June/006122.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in
Thi bug depend of thi one:
https://bugs.freedesktop.org/show_bug.cgi?id=16891
There are crownd funding project with one or two student who work on. The find
are to 450 $
http://freedomsponsors.org/core/issue/333/telepathy-should-support-otr-encryption
--
You received this bug notification
Bounty is now at 400 USD. Make that 4000 USD and someone with the
required skills can spend a month between two jobs collecting it. Sadly,
FreedomSponsors seems quite unpopular, so that people in the right
position might not see the tender offer. Are there perhaps other
platforms one could
Bounty is now up to $225 USD. Everybody who wants this feature but
doesn't have the skills to code an implementation and submit a patch,
please contribute to the bounty instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in
Individual offers of $50 on a bug report are great, but we talked of
having a Kickstarter. I bet in the current climate we could raise
thousands.
Who is capable of taking a quarter million dollars, or 120k, or 50k,
or 10k, and doing this?
It happens for other crap. Why not for this awesome?
Hi everyone.
This issue is a big deal for me, so I'm willing to pay USD 50.00 for it.
This offer is registered on FreedomSponsors
(http://freedomsponsors.org/core/issue/333/telepathy-should-support-otr-encryption).
If you solve it (according to the acceptance criteria described there), please
1 - 100 of 146 matches
Mail list logo
