shtrom / lurch4adium Goto Github PK

OMEMO Xtra for Adium (packaging the lurch and carbons libpurple plugins)

License: GNU General Public License v3.0

Objective-C 35.46% Makefile 64.54%

omemo encryption adium plugin xtra lurch carbons xep-0280 xmpp jabber

lurch4adium's Introduction

Lurch4Adium

An Xtra for Adium to support OMEMO. This is just a packaging effort. All credit goes to Richard Bayerle gkdr for writing the actual functionality.

This project packages gkdr's lurch and carbons plugins for Pidgin/libpurple as an Adium Xtra, so we can finaly have low-friction multi-device federated conversations.

Installation

You can either build the Xtra yourself (see below), or download a pre-built version it from the l4a-releases, and extract it. Once done, you can open the Xtra, which will be sent to Adium for installation.

open build/Release/Lurch4Adium.AdiumLibpurplePlugin

(The path shown assumes you built the Xtra.)

You then need to restart Adium, and make sure this new Plugin is enabled in the Xtras manager.

Usage

You should be able to enable carbons for a Jabber account by entering

/carbons on

in any chat window to enable carbons for this account.

You should similarly be able to interact with lurch and enable OMEMO through the lurch command. See

/lurch help

for more details.

On Using Libpurple Plugins in Adium

The plugin boilerplate comes from the Adium Tutorial adium-plugin-tutorial, which still seems to be relevant as of Sierra (10.12.4)/Xcode 8.3.2.

One notable difference, is, however, that libpurple plugins need to use the AdiumLibpurplePlugin wrapper extension, so the installLibpurplePlugin and loadLibpurplePlugin methods of the AILibpurplePlugin class are called.

Building

Build Requirements

The XCode GUI tools are needed. You can get them from the AppStore xcode-appstore after having sold your soul and given banking details. Apart from that, it's free-as-in-beer.

You then need to agree to lease out your first born as a receptacle for Steve Jobs' soul. This is done as follows.

sudo xcodebuild -license

Building

make

Will fetch the necessary third-party sources, and build them.

lurch4adium's People

Contributors

Stargazers

Watchers

Forkers

arahlin

lurch4adium's Issues

Plugin silently doesn't load on some machines

On some machines, Adium appears to not load the Lurch4Adium plugin, with no errors reported. Running /carbons on or /lurch help just results in that message being sent to the other party.

When running in Debug mode, searching for "lurch" in the Debug Window returns no lines.

Previously in 0.0.1, I had at least two friends who were unable to load the plugin. That was resolved for one of them in 0.0.3, but the second person is still unable to load the plugin.

Me (working): Adium 10.5.10.4, OS X 10.12.6.
Other 1 (not working with 0.0.1, works with 0.0.3): Adium 10.5.10.4, OS X 10.13.4.
Other 2 (not working with 0.0.1 or 0.0.3): Adium 10.5.10.4, OS X 10.10.5.

Could the issue be related to one mentioned in this comment?
#10 (comment)

Please let me know if I can provide more useful info.

Thanks for your help!

A correct support of OMEMO: 12 byte for initilization vector (IV)

@shtrom: There is a problem in the code of libomemo used by lurch:

xsf/xeps#894

I have done a patch here:

gkdr/libomemo#27

Can you find the solution to have a "good" OMEMO in macOS?

Linked to:

XEP-0384: OMEMO Encryption 0.4.0+

Can you update the XEP-0384: OMEMO Encryption support to 0.4.0+?

https://xmpp.org/extensions/xep-0384.html

And XEP-0454: OMEMO Media sharing:

https://xmpp.org/extensions/xep-0454.html

Diff Tool:

PS: Not sure that 0.3.0 was complete before:

https://xmpp.org/extensions/attic/xep-0384-0.3.0.html

Linked to:

gkdr/lurch#143

Unable to chat with unencrypted clients

I am unable to chat with xmpp clientes that do not support OMEMO.
If the opposite does not support OMEMO, that chat should be not be encrypted, otherwise the messages will not be readable or received.

Preferences -> Advanced -> Default Client => Adium Crash

First of all thanks for bringing carbons and omemo to adium, wich is a huge step forward for the sadly kind of dead adium. 🙂👍

I immediately installed the plugin to test it and stumbled over a crash in the preferences after installing the plugin: When accessing the "Default Client" page in the preferences Adium instantly crashes.
Preferences -> Advanced -> Default Client => Adium Crash

EDIT: I'm sorry,... I used Adium Version 1.5.10.3b1 and the issue got fixed in 1.5.10.4. (Looks like the updater is/was broken, as it didn't report the new Version,.. maybe because several of the Adium Websites are broken.)

Nothing seems to be working

I installed the plugin, restarted Adium (v1.5.11b3). No output from either /carbons on or /lurch help. Those actually end up being transmitted to the recipient in the clear. Neither carbons functionality nor omemo encryption is functionally working.

Adium mercurial server is dead...thus no builds

So I wanted to try out your nice contribution only to find that Adium's Mercurial servers which are used in your build script are dead (503).

Are there any other Adium source locations you could try to integrate there?
Maybe that would also allow to put in a Travis Script and enable you to provide compiled builds?

/lurch enable

in texting window output:

Valid arguments for 'lurch' in IMs are 'show', 'remove', 'blacklist', 'uninstall', and 'help'.

I am texting with an android user of Conversations - very OMEMO capable. I can view fp conv and own id and fp own

v 1.5.10.4

Carbons4Adium?

Is it possible to make a version of this plugin that includes just carbons? I have a use case in which I would like the functionality of carbons without requiring lurch, and I don't see a way to disable OMEMO by default (while still enabling carbons) with this plugin as written.

Carbons message from my other client open in a separate chat window with myself

As discussed in #10, I am seeing this issue with 0.0.3-pre.1 [0], but I appear to be the only one.

Please chime in on this issue if this impacts you, too.

[0] #10 (comment)

OMEMO indication

With the build from June 7th, I don't get the (OMEMO) in the window title like my conversation partner does with Pidgin when we're in an OMEMO-encrypted conversation.
Is that possible with Adium at all?

Building on macOS Monterey M1/ARM

Good evening,

I just cloned the latest and tried to build on my M1 MacBook Pro. Got a BUILD FAILED:

`/Users/snow/src/Lurch4Adium/Frameworks/adium/Adium.xcodeproj: warning: AddressBook is deprecated. Consider migrating to Contacts instead. (in target 'Adium' from project 'Adium')
/Users/snow/src/Lurch4Adium/Frameworks/adium/Adium.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.7, but the range of supported deployment target versions is 10.9 to 12.3.99. (in target 'AdiumLibpurple' from project 'Adium')
/Users/snow/src/Lurch4Adium/Frameworks/adium/Adium.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.7, but the range of supported deployment target versions is 10.9 to 12.3.99. (in target 'Setup Build Directory' from project 'Adium')
/Users/snow/src/Lurch4Adium/Frameworks/adium/Adium.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.7, but the range of supported deployment target versions is 10.9 to 12.3.99. (in target 'Plist Macros' from project 'Adium')
/Users/snow/src/Lurch4Adium/Frameworks/adium/Adium.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.7, but the range of supported deployment target versions is 10.9 to 12.3.99. (in target 'AIUtilities.framework' from project 'Adium')
/Users/snow/src/Lurch4Adium/Frameworks/adium/Adium.xcodeproj: warning: AddressBook is deprecated. Consider migrating to Contacts instead. (in target 'AIUtilities.framework' from project 'Adium')
** BUILD FAILED **

make[1]: *** [adium] Error 65
make: *** [/Users/snow/src/Lurch4Adium/Frameworks/adium/.built] Error 2`

Any ideas? No worky on M1?

Thank you!

Updated build?

Any chance of getting an updated release build of Lurch4Adium? There's been updates to both carbons and lurch, the former of which fixes bugs that break carbons with the Conversations client, and the latter of which has received security updates.

I tried building it myself but it looks like I'll have to do an OS upgrade before Apple will let me have xcode.

Hard to follow documentation

Hello - cool work on the plugin!

I and my friend installed the plugin, typed '/carbons on'. I got a 'success' message. I have no idea the plugin is actually doing anything though. Is there any visual indication that what we're saying is encrypted? (or that something's not encrypted).

Some info as to what to expect of a successfully encrypted/unsuccessfully encrypted conversation would be useful for me.