From klemens at posteo.de  Sun Jan 17 11:10:54 2021
From: klemens at posteo.de (Klemens Nanni)
Date: Sun, 17 Jan 2021 11:10:54 +0100
Subject: [profanity] "/oememo log on" refers to nonexistent "/chlog on"
	command
Message-ID: <YAQNLuTmGF08Io78@eru>

(Please Cc me in replies as I am not subscribed to the list.)

Running on

	$ uname -smr
	OpenBSD 6.8 amd64

	$ profanity --version
	Profanity, version 0.10.0
	Copyright (C) 2012 - 2019 James Booth <boothj5web at gmail.com>.
	Copyright (C) 2019 - 2021 Michael Vetter <jubalh at iodoru.org>.
	License GPLv3+: GNU GPL version 3 or later <https://www.gnu.org/licenses/gpl.html>

	This is free software; you are free to change and redistribute it.
	There is NO WARRANTY, to the extent permitted by law.

	Build information:
	XMPP library: libmesode
	Desktop notification support: Disabled
	OTR support: Enabled (libotr 4.1.1)
	PGP support: Enabled (libgpgme 1.14.0)
	OMEMO support: Enabled
	C plugins: Enabled
	Python plugins: Enabled (3.8.7)
	GTK icons: Disabled

I noticed the following while configuring OMEMO:

	/omemo log on
	11:06:38 - OMEMO messages will be logged as plaintext.
	11:06:38 - Chat logging is currently disabled, use '/chlog on' to enable.

	/chlog on
	11:06:40 - Unknown command: /chlog on

	/help chlog
	11:06:40 - No such command.

From jubalh at iodoru.org  Sun Jan 17 11:25:28 2021
From: jubalh at iodoru.org (Michael Vetter)
Date: Sun, 17 Jan 2021 11:25:28 +0100
Subject: [profanity] "/oememo log on" refers to nonexistent "/chlog on"
 command
In-Reply-To: <YAQNLuTmGF08Io78@eru>
References: <YAQNLuTmGF08Io78@eru>
Message-ID: <20210117112528.2af88f5c@maitreya.fritz.box>

Hi,

On Sun, 17 Jan 2021 11:10:54 +0100
Klemens Nanni <klemens at posteo.de> wrote:
> I noticed the following while configuring OMEMO:
> 
> 	/omemo log on
> 	11:06:38 - OMEMO messages will be logged as plaintext.
> 	11:06:38 - Chat logging is currently disabled, use '/chlog
> on' to enable.
> 
> 	/chlog on
> 	11:06:40 - Unknown command: /chlog on
> 
> 	/help chlog
> 	11:06:40 - No such command.

Thanks for noticing. I'll fix that later.
The command has been moved a few releases ago.

In case you haven't found it yet, the new command is:
/logging chat on

From hadaqada at gmail.com  Fri Mar 12 12:41:47 2021
From: hadaqada at gmail.com (Seswu M. Fafnan)
Date: Fri, 12 Mar 2021 12:41:47 +0100
Subject: [profanity] 0.10.0: ./configure exits with error
Message-ID: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>


Hello all,

I am unable to connect to my server with version 0.6.0, the package distributed for my system (while Psi does connect), so I have been trying to manually install 0.10.0 which according to someone helpful does connect as it should.

I have installed the large number of dependencies, including libstrophe-dev, but while ./bootstrap.sh exits fine, ./configure fails.

Last messages are:
checking for libmesode... no
checking for libstrophe... no
checking whether  works... configure: error:  is broken, check config.log for details

It appears that it does not find libstrophe. However, libstrophe is there.
"libstrophe0 is already the newest version (0.9.2-2)".

System is raspbian GNU/Linux 10, buster, running on a raspberry pi 3.

config.log.. does show something interesting.
Line 70-80:
------------------------------
configure:3326: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/8/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: [...]
Thread model: posix
gcc version 8.3.0 (Raspbian 8.3.0-6+rpi1) 
configure:3337: $? = 0
configure:3326: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
------------------------------

gcc is called with -v one time, and it goes well, -V another, and it's unrecognized.
Later on there is some complaints over a missing .h file, so perhaps the entire process went astray over this and it failed to fail when it should?

Anyway, config.log included as attachment.

Kind regards, Seswu/Fluxus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 34720 bytes
Desc: not available
URL: <http://lists.notraces.net/pipermail/profanity/attachments/20210312/8b84a91f/attachment-0001.obj>

From jubalh at iodoru.org  Fri Mar 12 13:34:16 2021
From: jubalh at iodoru.org (Michael Vetter)
Date: Fri, 12 Mar 2021 13:34:16 +0100
Subject: [profanity] 0.10.0: ./configure exits with error
In-Reply-To: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>
References: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>
Message-ID: <20210312133416.463e2630@maitreya>

On Fri, 12 Mar 2021 12:41:47 +0100
"Seswu M. Fafnan" <hadaqada at gmail.com> wrote:

> It appears that it does not find libstrophe. However, libstrophe is
> there. "libstrophe0 is already the newest version (0.9.2-2)".

That's not the latest version. 0.10.1 is. And Profanity needs at least
0.10 :-)

Good luck!

From debacle at debian.org  Fri Mar 12 13:49:16 2021
From: debacle at debian.org (Martin)
Date: Fri, 12 Mar 2021 13:49:16 +0100
Subject: [profanity] 0.10.0: ./configure exits with error
In-Reply-To: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>
References: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>
Message-ID: <YEtjTPoTVvwtdmHj@fama>

On 2021-03-12 12:41, Seswu M. Fafnan wrote:
> It appears that it does not find libstrophe. However, libstrophe is there.
> "libstrophe0 is already the newest version (0.9.2-2)".
>
> System is raspbian GNU/Linux 10, buster, running on a raspberry pi 3.

I'm not familiar with raspbian, but in Debian 10 buster,
libstrophe 0.10.0 is available via the official backports. The
Debian package version is 0.10.0-1~bpo10+1. Furthermore, you can
install profanity 0.10.0-1~bpo10+1 via backports, too. But I
have no idea how this applies to raspbian, sorry.

Cheers

From martin at mdosch.de  Fri Mar 12 16:15:32 2021
From: martin at mdosch.de (Martin Dosch)
Date: Fri, 12 Mar 2021 16:15:32 +0100
Subject: [profanity] 0.10.0: ./configure exits with error
In-Reply-To: <YEtjTPoTVvwtdmHj@fama>
References: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>
 <YEtjTPoTVvwtdmHj@fama>
Message-ID: <20210312151532.lwgaprwzp6nxsfnz@mdosch.de>

On 12.03.2021 13:49, Martin wrote:
>I'm not familiar with raspbian, but in Debian 10 buster,
>libstrophe 0.10.0 is available via the official backports. The
>Debian package version is 0.10.0-1~bpo10+1. Furthermore, you can
>install profanity 0.10.0-1~bpo10+1 via backports, too. But I
>have no idea how this applies to raspbian, sorry.

I'm also not familiar with raspbian, but I guess you could just take the 
armhf repo of debian backports:

apt policy profanity
profanity:
   Installiert:           (keine)
   Installationskandidat: 0.6.0-1
   Versionstabelle:
      0.10.0-1~bpo10+1 100
         100 https://deb.debian.org/debian buster-backports/main armhf Packages
      0.6.0-1 900
         900 https://deb.debian.org/debian buster/main armhf Packages

Best regards,
Martin
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : signature.asc
Dateityp    : application/pgp-signature
Dateigr??e  : 833 bytes
Beschreibung: nicht verf?gbar
URL         : <http://lists.notraces.net/pipermail/profanity/attachments/20210312/efd80aaa/attachment.sig>

From martin at mdosch.de  Fri Mar 12 16:17:49 2021
From: martin at mdosch.de (Martin Dosch)
Date: Fri, 12 Mar 2021 16:17:49 +0100
Subject: [profanity] 0.10.0: ./configure exits with error
In-Reply-To: <YEtjTPoTVvwtdmHj@fama>
References: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>
 <YEtjTPoTVvwtdmHj@fama>
Message-ID: <20210312151749.bq2wgki4nda4xlps@mdosch.de>

I forgot to mention: If you're running a headless system on your RPi you 
might go for profanity-light. :)
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : signature.asc
Dateityp    : application/pgp-signature
Dateigr??e  : 833 bytes
Beschreibung: nicht verf?gbar
URL         : <http://lists.notraces.net/pipermail/profanity/attachments/20210312/a8765a62/attachment.sig>

From debacle at debian.org  Fri Mar 12 16:32:06 2021
From: debacle at debian.org (Martin)
Date: Fri, 12 Mar 2021 16:32:06 +0100
Subject: [profanity] 0.10.0: ./configure exits with error
In-Reply-To: <20210312151749.bq2wgki4nda4xlps@mdosch.de>
References: <20210312124147.9ac59dee3c8d72bc6277c0dd@gmail.com>
 <YEtjTPoTVvwtdmHj@fama> <20210312151749.bq2wgki4nda4xlps@mdosch.de>
Message-ID: <YEuJditGP6rVnZKz@fama>

On 2021-03-12 16:17, Martin Dosch via profanity wrote:
> I forgot to mention: If you're running a headless system on your RPi you
> might go for profanity-light. :)

+1 for profanity-light!

From lists.trs-80 at isnotmyreal.name  Fri Mar 12 21:08:56 2021
From: lists.trs-80 at isnotmyreal.name (TRS-80)
Date: Fri, 12 Mar 2021 15:08:56 -0500
Subject: [profanity] Opening aesgcm:// links
Message-ID: <fd0345808235a613b59edf8ff213c9db@isnotmyreal.name>

Hai Guise!

First, thanks a lot for all your work and for sharing Profanity!  I am
very thankful to be able to enjoy every day using a terminal based
client that is capable of handling OMEMO!  :D

So, some clients[0] send these encrypted aesgcm://... links instead of
regular https://... links when sending pictures via OMEMO.

Today I stumbled across ImageDownloader[1] which is a small java
program to decrypt these files and output the result to STDOUT.  With
a small wrapper shell script[2] it can even automatically discern
between encrypted and regular links, decoding the former and passing
the latter directly through to the browser.

So far so good.

However the problem seems to be that aesgcm:// is not recognized as a
protocol, and thus, is not clickable in the same way a "regular"
(http(s)://) link is.

Now, in fairness, I am not even sure this is an issue with Profanity
itself.  It could have more to do with my terminal for all I know
(currently using xfce4-terminal).  Or even...?

I was digging through all the Profanity settings, but could not seem
to find anything relevant.  I did not go so far as digging through
source (yet).  After spending couple hours digging into this, I
thought, maybe better ask on list, as I might be going down entirely
wrong path.

Any suggestions which direction to look would be appreciated.

Cheers,
TRS-80


[0] At least Conversations on Android and ChatSecure on iOS, that I am
aware of.

[1] https://github.com/iNPUTmice/ImageDownloader

[2] 
https://github.com/iNPUTmice/ImageDownloader/blob/master/openbrowser.sh

From jubalh at iodoru.org  Fri Mar 12 22:23:12 2021
From: jubalh at iodoru.org (Michael Vetter)
Date: Fri, 12 Mar 2021 22:23:12 +0100
Subject: [profanity] Opening aesgcm:// links
In-Reply-To: <fd0345808235a613b59edf8ff213c9db@isnotmyreal.name>
References: <fd0345808235a613b59edf8ff213c9db@isnotmyreal.name>
Message-ID: <20210312222312.1806d8aa@maitreya>

On Fri, 12 Mar 2021 15:08:56 -0500
TRS-80 <lists.trs-80 at isnotmyreal.name> wrote:

> Hai Guise!
> 
> First, thanks a lot for all your work and for sharing Profanity!  I am
> very thankful to be able to enjoy every day using a terminal based
> client that is capable of handling OMEMO!  :D
> 
> So, some clients[0] send these encrypted aesgcm://... links instead of
> regular https://... links when sending pictures via OMEMO.

Profanity 0.10.0 can open/save them :-)
See:
https://github.com/profanity-im/profanity/issues/1262
https://github.com/profanity-im/profanity/pull/1375

There is also another commandline tool which get download these files.
Done by wstrm again: https://github.com/wstrm/omemo-utils

> Now, in fairness, I am not even sure this is an issue with Profanity
> itself.  It could have more to do with my terminal for all I know
> (currently using xfce4-terminal).  Or even...?

I think that's the terminals job. But most likely none will know about
aesgcm.

Hope this helps,
Michael

From lists.trs-80 at isnotmyreal.name  Fri Mar 12 23:27:12 2021
From: lists.trs-80 at isnotmyreal.name (TRS-80)
Date: Fri, 12 Mar 2021 17:27:12 -0500
Subject: [profanity] Opening aesgcm:// links
In-Reply-To: <20210312222312.1806d8aa@maitreya>
References: <fd0345808235a613b59edf8ff213c9db@isnotmyreal.name>
 <20210312222312.1806d8aa@maitreya>
Message-ID: <1e49ff012737951c2c269e03a03b7a58@isnotmyreal.name>

On 2021-03-12 16:23, Michael Vetter wrote:
> On Fri, 12 Mar 2021 15:08:56 -0500
> TRS-80 <lists.trs-80 at isnotmyreal.name> wrote:
> 
>> So, some clients[0] send these encrypted aesgcm://... links instead
>> of regular https://... links when sending pictures via OMEMO.
> 
> Profanity 0.10.0 can open/save them :-)
> See:
> https://github.com/profanity-im/profanity/issues/1262
> https://github.com/profanity-im/profanity/pull/1375

OK, so even though I was already reading about /url in my search
through docs, this did not fully dawn on me until your hint just now,
which I tried and of course it worked.  :D

So, for benefit of other people who might be thick like myself, here
is what you do (in a buffer where you received one of these
aesgcm://... links):

/url open <tab>

Which will autocomplete the last link received.  Pressing <tab> again
gives you the one before that, etc.  Press enter and it will fetch and
decode the file and then open it up in the system browser like normal.

If you want to save instead, I presume you would use save instead of
open.

No need to click on a link then.  Which will work fine for me as I
prefer keyboard workflow anyway.

> There is also another commandline tool which get download these
> files.  Done by wstrm again: https://github.com/wstrm/omemo-utils

Interesting, thanks!

>> Now, in fairness, I am not even sure this is an issue with
>> Profanity itself.  It could have more to do with my terminal for
>> all I know (currently using xfce4-terminal).  Or even...?
> 
> I think that's the terminals job. But most likely none will know
> about aesgcm.

I think you are right, that it is up to terminal to recognize
URI/links.  I was going to pursue that some more, but as I said I
prefer keyboard anyway, so I will leave this part of research for
other people who might need it.

Thanks Michael for the very fast reply!  I had a funny feeling I was
heading down the wrong path, so I am glad I decided to post to the
list.

Have a great weekend, mate!

Cheers,
TRS-80

From stefan at devlug.de  Sat Mar 13 10:54:49 2021
From: stefan at devlug.de (Stefan)
Date: Sat, 13 Mar 2021 10:54:49 +0100
Subject: [profanity] OMEMO and OX
Message-ID: <20210313095449.2vzk2u6yixhn33df@devlug.de>

Hello,

# OMEMO

## Start Session after Roster received

I did a small change which is on master branch.
commit b460d427bc132aa088f5787a17d045d2ece172d5

Before this change, profanity has requested all OMEMO keys for all
users in the roster. Sometimes I got "Lost connection", which may due
to to much things happened during started up.

The session start will be done when you open a window. I think this is
the same what conversations / gajim doing - I have a least the
feeling. Let my know if you face any issues due to this change.
I'm not the OMEMO Power User :-)

## Trust mode

With "OMEMO - trust mode #1506" I started on the implementation of
OMEMO trust mode. There will be a new subcommand for /omemo.

	/omemo trustmode manual|tofu|blind

This is a preference setting and will be stored with /save in [omemo].

 * manual - It should be the same like it is now.
 The user has to confirm all key manually - good luck!

 * ToFu - Is not implemented yet.
 If there is no trusted key of a user, we will trust all keys.
 If there is at least one trusted key, we won't touch anything.

 * blind - Trust all new keys

Feel free to have a look into #1506 for feedback.

## Blog post about OMEMO

Maybe it would be a nice idea to have a blog post of OMEMO usage in
profanity. Maybe there is a volunteer around to write something down?
;-)

# OX

## OX: Bugfixes for OX implementation #1487

There are some bugs in OX where I started to work on and I'm
going to continue testing. If there are some volunteers for testing
etc, please let me now.

-- 
Mit freundlichen Gr??en,
Stefan

From martin at mdosch.de  Sat Mar 13 15:54:01 2021
From: martin at mdosch.de (Martin Dosch)
Date: Sat, 13 Mar 2021 14:54:01 +0000
Subject: [profanity] OMEMO and OX
In-Reply-To: <20210313095449.2vzk2u6yixhn33df@devlug.de>
References: <20210313095449.2vzk2u6yixhn33df@devlug.de>
Message-ID: <483CF844-0154-4087-9ED7-5BF4868C81CA@mdosch.de>

Will tofu show you a hint if there are new (untrusted) keys?

From stefan at devlug.de  Sat May  8 09:35:46 2021
From: stefan at devlug.de (Stefan)
Date: Sat, 8 May 2021 09:35:46 +0200
Subject: [profanity] OMEMO bug-squashing
Message-ID: <20210508073546.jeq5gp2vm7rfbeiq@devlug.de>

Hello,

I did some OMEMO tests. OMEMO is working, but there are some issues. It
looks profanity is not always consistent.

# 1) Skipping own device
https://xmpp.org/extensions/xep-0384.html#encrypt

It looks it will be done via chat messages, but not via groupchat.
We may should add the same rule into the groupchat?

# 2) New buddy will join a MUC

You are in a room. New buddy joins the room ( not in the roster )
Do we get the device list? Maybe not at the right time?

# 3) When do we get this message?

08/05/2021 08:40:57: prof: INF: [OMEMO][SIGNAL] We've already setup a session for this V3 message, letting bundled message fall through...
08/05/2021 08:40:57: prof: INF: [OMEMO][SIGNAL] Bad MAC
08/05/2021 08:40:57: prof: WRN: [OMEMO][SIGNAL] Message mac not verified
08/05/2021 08:40:57: prof: WRN: [OMEMO][SIGNAL] No valid sessions

Maybe if we try to decrypted a message with no RID of our device.
Messages from own device?

Do we check - before decryption, if the message has been encrypted for the current device?
( Should be possible?! - are we doing this currently? )

# 4) MAM

When I open a chat window with a buddy. I get ( maybe via mam ) 

22:19:36 - me: You received a message encrypted with OMEMO but your client doesn't support OMEMO.
22:19:40 - me: You received a message encrypted with OMEMO but your client doesn't support OMEMO.
22:21:10 - me: You received a message encrypted with OMEMO but your client doesn't support OMEMO.

# 5) untrust a trusted fingerprint

untrust a fingerprint of contact which is not in the roster, is working.
Depending on the trust / untrust I can read or not read the message.
=> OK

In the log file I can see an error
08/05/2021 09:21:32: stderr: ERR: (profanity:1486): GLib-CRITICAL **: 09:21:32.453: g_hash_table_iter_next: assertion 'ri->version == ri->hash_table->version' failed

# Logging

I think we should add some more logging for the OMEMO functionality.

-- 
Mit freundlichen Gr??en,
Stefan ( xmpp:stefank at conversations.im )
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.notraces.net/pipermail/profanity/attachments/20210508/e3147bb3/attachment.sig>

From martin at mdosch.de  Sat May  8 10:33:46 2021
From: martin at mdosch.de (Martin Dosch)
Date: Sat, 8 May 2021 10:33:46 +0200
Subject: [profanity] OMEMO bug-squashing
In-Reply-To: <20210508073546.jeq5gp2vm7rfbeiq@devlug.de>
References: <20210508073546.jeq5gp2vm7rfbeiq@devlug.de>
Message-ID: <20210508083346.jimvfpwz6xdmrbqr@mdosch.de>

Hello together,

>I did some OMEMO tests. OMEMO is working, but there are some issues. It
>looks profanity is not always consistent.

I agree, it works but there are some issues. Especially the one where it 
can't find keys to encrypt after a reconnect (#1530) is a bit annoying.
Hopefully I find some more time to have a closer look and help debugging 
than I had in the last weeks.

># 4) MAM
>
>When I open a chat window with a buddy. I get ( maybe via mam )
>
>22:19:36 - me: You received a message encrypted with OMEMO but your client doesn't support OMEMO.
>22:19:40 - me: You received a message encrypted with OMEMO but your client doesn't support OMEMO.
>22:21:10 - me: You received a message encrypted with OMEMO but your client doesn't support OMEMO.

Afaik this is a known issue as the experimental MAM support also reads 
OMEMO messages from MAM and due to the nature of OMEMO (PFS in this 
case) it's not possible to decrypt a message twice. Profanity should not 
show this for messages received from MAM and rather show the messages 
from the local DB.

Best regards,
Martin
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : signature.asc
Dateityp    : application/pgp-signature
Dateigr??e  : 833 bytes
Beschreibung: nicht verf?gbar
URL         : <http://lists.notraces.net/pipermail/profanity/attachments/20210508/b3af0372/attachment.sig>