Pidgin omemo plugin настроить
A core plug-in enabling 1:1 OMEMO encryption for the libpurple framework in XMPP
Latest commit
Git stats
Files
Failed to load latest commit information.
README.md
This is a prototype plug-in for Jabber/XMPP accounts to support 1:1 end-to-end encryption with OMEMO (XEP-0384) in Pidgin and other compatible clients using libpurple. It doesn’t have graphical trust management yet. See Usage on how to activate and configure it «by hand».
It allows Pidgin to be OMEMO-compatible with Conversations (Android), ChatSecure (iOS), Gajim (desktop — with OMEMO plug-in) and riba’s Pidgin OMEMO plug-in.
DISCLAIMER: This plug-in is in experimental state and in constant development. It is not intended to be used on production environments. Do not rely on this plug-in to protect sensitive information. If you use it you are on your own and I take no resposibility for any damage, harm or loss you, your system, your data or your cat might suffer.
This plug-in was the result of academic research. You can find a couple of thoughts about it as well as OMEMO itself here (in German).
Tested with the following versions:
- libpurple 2.10.12 (Ubuntu: libpurple0)
- libgcrypt 1.6.5 (Ubuntu: libgcrypt20)
- libsqlite 3.11.0 (Ubuntu: libsqlite3-0)
- libsignal-protocol-c git@e0e778d (see below)
libpurple development headers (Ubuntu: libpurple-dev)
libgcrypt development headers (Ubuntu: libgcrypt20-dev)
libsqlite3 development headers (Ubuntu: libsqlite3-dev)
libxml2 development headers (Ubuntu: libxml2-dev)
(This will install the shared library as well as the development headers)
Will copy omemo.so to the user’s plugin directory ($HOME/.purple/plugins). After that you should see the plugin appear in Tools->Plugins. Restart Pidgin after activation.
After building the plugin:
The following assumes that the plug-in is installed and activated, Pidgin restarted and the Jabber account was online at least once.
Before using the plug-in you have to enable encryption for the contacts you want to communicate with, then you have to define trust for every device of each contact.
Step one: Locate the OMEMO DB file
If you have only one Jabber account just open the SQLite DB found under $HOME/.purple/omemo/ (or wherever you purple home is). If you have multiple accounts go to $HOME/.purple/accounts.xml and look for omemo-db-id under the settings section of the account you want to configure and edit the corresponding file under $HOME/.purple/omemo/.
Step two: Enable encryption
Encryption is disabled by default. To enable it set the value of encryption in the table contacts to 1. If the table has no entries try restarting Pidgin.
Step three: Trust devices (or not)
Now you are able to receive encrypted messages. However, in order to send you need to define for every device of your contact whether you trust it or not. Go to the table devices and set trust to 1 (trusted) or 0 (not trusted) accordingly. Do the same for your own devices.
You won’t get any feedback from the plug-in in the chat window. If something doesn’t work as expected open the Pidgin debug console (Help->Debug window) and filter after core-mancho-omemo.
- On sending the first message to a contact the Signal sessions are built asynchronously. Depending on how fast the servers are it could be that the first message or messages are discarded, so don’t wonder if they are not delivered to your counterpart. Wait a second and try again.
- A very large etc.
- Notifications in chat window
- Configuration GUI (activation and trust management)
- Group chat support
- New build system
About
A core plug-in enabling 1:1 OMEMO encryption for the libpurple framework in XMPP
Источник
Pidgin omemo plugin настроить
/lʊʁç/. In German, an Axolotl is a type of Lurch, which simply means ‘amphibian’. This plugin brings Axolotl, by now renamed to double ratchet, to libpurple applications such as Pidgin by implementing the XEP-0384: OMEMO Encryption. For a higher-level overview, see the official OMEMO homepage.
(Plus I thought the word sounds funny.)
This section is now the changelog.
Table of Contents
1. Install the (submodules’) dependencies
Below you can find the command to install the dependencies for popular distribution families. Make sure that you use at least version 2.7 of mxml, and 2.10.10 of libpurple.
Debian, Ubuntu
ArchLinux, Parabola
Fedora
2A. EITHER: Build and install from source
If you just pull a newer version ( git pull ), remember to also update the submodules as they might have changed!
The last command compiles the whole thing and copies the plugin into your local libpurple plugin directory.
The next time you start Pidgin, or another libpurple client, you should be able to activate it in the «Plugins» window.
2B. OR: Install from a community repo
Thanks to EionRobb, Windows users can use the dlls he compiled and provides here: https://eion.robbmob.com/lurch/
- Download the plugin (lurch.dll) and put it in the Program Files (x86)\Pidgin\plugins directory.
- Download libgcrypt-20.dll and libgpg-error-0.dll and put them in the Program Files (x86)\Pidgin directory.
These instructions can also be found at the provided link.
Homebrew should have all dependencies:
This should work on newer versions of MacOS, but if you run into problems check out #8 for some hints. Complete instructions on how to get this running with Pidgin appreciated!
Alternatively, if you use Adium, you should definitely check out shtrom’s Lurch4Adium!
The current version of libpurple‘s XMPP protocol plugin does not support many XEPs by itself. For more features and compatibility with other clients such as Conversations you can install the pulgins below.
If you have multiple devices and want messages sent and received by one device show up on all others, XEP-0280: Message Carbons is what you are looking for.
You can find my plugin for it here: https://github.com/gkdr/carbons
In order to support the checkmarks for delivered messages, you could install this plugin implementing XEP-0184: Message Delivery Receipts:
The first thing you can do to check if this plugin works is enter the /lurch help command in any conversation window. You will receive a list of the other commands you can use. I know this is a bit clunky, but using the command interface for interactions makes the plugin usable in clients that do not have a GUI.
After you have made sure it was installed correctly, you do not have to activate it specifically for each conversation partner you want to use it with, unlike with e.g. OTR. If it detects that the other side is using OMEMO (by the existence of an OMEMO devicelist), the conversation will be encrypted automatically. If you do not want this, you can blacklist the user by typing /lurch blacklist add in the conversation window.
This plugin will set the window title to notify the user if encryption is enabled or not. If it is, it will generally not send plaintext messages. If a plaintext message is received in a chat that is supposed to be encrypted, the user will be warned.
Group chats (via XEP-0045: Multi-User Chat aka MUCs) are not part of the OMEMO specification, but can work under specific circumstances as outlined on the Conversations README. These are:
- The MUC has to be non-anonymous so the real JID of each participant is visible. The channel owner has to set this property. In Pidgin you can get there by typing /config .
- Every participant has to be in every other participant’s contact list! This is why this really only makes sense for member-only MUCs.
Once you have confirmed these conditions are met, every member has to activate OMEMO him- or herself. Using this plugin it works by typing /lurch enable . Warning messages are displayed if it does not work for every user in the conference, hopefully helping to fix the issue.
It is recommended you confirm the fingerprints look the same on each device, including among your own. To do this, you can e.g. display all fingerprints participating in a conversation using /lurch show fp conv .
In order to uninstall this plugin, you should call the /lurch uninstall command. It will remove this client from the OMEMO device list, notifying other OMEMO clients that they do not need to encrypt messages for it any longer.
Afterwards, you can just deactivate the plugin in the Tools > Plugins window.
In order to completely remove all data related to this plugin, e.g. for a fresh installation, you will need to delete the following files from your .purple directory:
- your@xmpp.account_omemo_db.sqlite to delete the device list cache
- your@xmpp.account_axc_db.sqlite to delete your keypair and all sessions with other devices
- and finally, lurch.[so|dll] found in the plugins directory
If something does not work as expected, don’t hesitate to open an issue. You can also reach me on the Pidgin IRC channel (#pidgin on freenode) as riba , or send me an email.
It will usually be helpful (i.e. I will probably ask for it anyway) if you provide me with some information from the debug log, which you can find at Help > Debug Window in Pidgin. There, you will see a scary error from the XML parser every time you receive a message, which you can safely ignore. It is due to the nonstandard namespace used by OMEMO and looks something like this: jabber: XML parser error for JabberStream 0x5631ed678670: Domain 3, code 100, level 1: xmlns: URI eu.siacs.conversations.axolotl is not absolute .
In addition to just reading logs, you can get a bit more active, as again I will probably ask for this anyway. Pidgin comes with an XMPP console, but you have to activate the plugin first (Tools > Plugins). Afterwards you can find it at Tools > XMPP Console and send queries to the server.
If you are having trouble sending or receiving messages, you should look up if you can find the device in the device list. You can do so by pasting the following into the XMPP console, replacing the to attribute with the device’s owner’s JID:
Sometimes, a device might be on the list, but it did not publish a bundle, which is necessary to establish a session. In this case, you can query this bundle by pasting the following, replacing the to attribute as well as the DEVICE_ID suffix of the bundles node:
Finally, in case it is more serious and Pidgin crashes, I will have to ask you for a backtrace. You can obtain it in the following way:
- Open Pidgin in gdb: gdb pidgin
- Run it: run
- Do whatever you were doing to make it crash
- When it does crash, type bt (or backtrace )
- Copy the whole thing
Can it talk to other OMEMO clients?
Yes, it was (briefly) tested with:
See https://omemo.top/ for additional clients.
Does it work with Finch?
It should, but I only tried it briefly.
OMEMO is not ‘whatever Conversations can do’, but a very specific XEP.
For instance, if you don’t install the additional plugin mentioned above, this is probably not the right thing to use if you have multiple clients running at the same time, as there is no message carbons support in libpurple as of now.
At the moment, there is no XEP-0313: Message Archive Management aka MAM support in libpurple, so there are no ‘offline messages’.
Finally, I can’t stress this enough: This plugin is highly experimental, so you should not trust your life on it.
Источник
XMPP+OMEMO — множественные отпечатки при одном устройстве.
Месяца 3-4 пытался использоват Convesations на Android и Gajim/Pidgin+OMEMO на Linux/Win7. В результате ушел с OMEMO. (Наверное на OTR/PGP). Основная проблема в клиенте под андроид (Conversations.im) — он постоянно генерит новые fingerprints на имеющееся устройство. Достаточно просто загрузиться в TWRP recovery и сделать бекап(даже не откатить его. ) — естественно при отключенном аккоунте в Convesations.
Такая же и история с Gajim/
По всеё видимости автор Conversations знает об этом баге(в самом OMEMO. ), ибо по умолчанию в Conversations.im стоит доверять всем fingerprints слепо!
Вопрос: может я не умею настраивать OMEMO?
Не баг а фича
Чтобы не генерить ключи в консерве, просто бэкапь консерву титаниумом
Re: Не баг а фича
А на писюке как быть. Да и чем титаниум лучше TWRP?
УМВР. Ключи лежат в хомяке, новых не генерируется. Думаю, где-то с консервой косяк.
Комп получает ip под dhcp по wifi от роутера и пару перезагрузок имеем 6 fingerpring от одного устройства.
Это точно происходит по вине роутера?
Это точно происходит по вине роутера?
Не факт, просто описываю ситуацию — IP может/должен меняться (клиентов мало — иногда ip один и тотже).
Я использовал и Legacy и текущие релизы регулярно (3-4 месяца) [может слушать пытаются — иногда fingerprints совсем левые (-;]
У меня такое не наблюдается ни с Conversations, ни с Gajim. Вы что-то делаете не так.
похоже эта проблема на стороне Conversations.
Аккуратно связал два устройства(mobile/Conversations) с одним аккоунтом с двумя устройствами с другим аккоунтом(PC/Gajim) — кроме 2+2fingerprints вылезло ещё два (один точно от другой сессии от Conversations, а другой не помню откуда — может быть левый).
Очень неудобно чистить OMEMO отпечатки на Conversations — удалить все кроме активного — на Gajim гораздо удобнее.
Если бы чистилка OMEMO отпечатков на Conversations была как на Gajim — я бы этот вопрос может быть и не задавал бы.
похоже эта проблема на стороне Conversations.
иногда fingerprints совсем левые (-;]
А консерва откуда, с ф-дроид или с гуглоплея?
Источник
