| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
| |
To make the destinction clearer and easier to search.
|
|
|
|
|
|
|
| |
Should have been done alogn with e9f218cdf6e15f4469d77cbaee59cc8501ed4e82.
Like this people who are not in the roster can get our public key and
write messages to use.
|
| |
|
|\
| |
| | |
Several OX improvements
|
| |
| |
| |
| |
| |
| |
| | |
strcpy() can't work here because the data doesn't have to be
NULL-terminated. So let's use memcpy.
Fix memleak of plain_str.
|
| |
| |
| |
| |
| | |
Mention new man page.
Correct the usage of /ox request.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Maybe we can make this configurable later.
So users have the freedom to be more strict.
This commit partly reverts 62018f48c5f1a0410445fce5bca5fdd6a9e4d907.
Example to edit trust level:
```
gpg --edit-key somekeyid
gpg (GnuPG) 2.3.4; Copyright (C) 2021 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa4096/keyid
created: 2020-06-26 expires: 2022-06-26 usage: SC
trust: unknown validity: full
sub rsa4096/keyid
created: 2020-06-26 expires: 2022-06-26 usage: E
[ full ] (1). xmpp:user@domain.de
gpg> trust
pub rsa4096/keyid
created: 2020-06-26 expires: 2022-06-26 usage: SC
trust: unknown validity: full
sub rsa4096/keyid
created: 2020-06-26 expires: 2022-06-26 usage: E
[ full ] (1). xmpp:user@domain.de
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 3
pub rsa4096/keyid
created: 2020-06-26 expires: 2022-06-26 usage: SC
trust: marginal validity: full
sub rsa4096/keyid
created: 2020-06-26 expires: 2022-06-26 usage: E
[ full ] (1). xmpp:user@domain.de
Please note that the shown key validity is not necessarily correct
unless you restart the program.
gpg> quit
```
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
________________________________________
< No comment - should be much better now >
----------------------------------------
\
\
\ >()_
(__)__ _
|
| |
| |
| |
| |
| |
| |
| | |
* Added logging messages (INFO if key can not be used)
* Check owner_trust < GPGME_VALIDITY_MARGINAL
The key can not be used if the owner_trust is less than MARGINAL.
|
| | |
|
| | |
|
| |
| |
| |
| | |
We also need to be able to stop an ox conversation :-)
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This man page should help people to set up OX in profanity.
We have profanity-ox.1 which is the same as `/help ox` and describes how
to use OX.
This man page will help with the setup with the external gpg program.
Based on the blogpost of Stefan:
https://profanity-im.github.io/blog/post/openpgp-for-xmpp-ox/
|
|/
|
|
|
|
|
|
|
| |
This was done before OX was implemented. In 0.10 ox landed in Profanity
and we have the blogpost:
https://profanity-im.github.io/blog/post/openpgp-for-xmpp-ox/ to
describe the usage.
We will have a man page to help users with the setup as well.
|
|
|
|
|
|
|
|
|
|
|
|
| |
@mdosch discovered that we now don't print `:` for messages from others
anymore.
Until
https://github.com/profanity-im/profanity/pull/1663#issuecomment-1114625151
is fixed lets restore the default behaviour to always add `:` in
`_win_print_internal()`.
The result will be that a stamp set to `-->` will also look like `-->:`.
|
|\
| |
| | |
Fix autocomplete for `/ox discover`.
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
Log file improvements
|
| |
| |
| |
| |
| |
| |
| |
| | |
Rotated log files will now be: `.local/share/profanity/logs/profanity.001.log`
We only use logrotation if we use the default log file ending with .log.
So Replacing the `.` should be fine.
User supplied log files are not rotated.
|
| |
| |
| |
| | |
profanity.log.001 -> 999.
|
|/
|
|
| |
In case logrotate is on.
|
|\
| |
| | |
Use ISO8601 as date format in log files
|
| | |
|
| |
| |
| |
| | |
For both 1:1 and groupchat.
|
|\ \
| |/
|/| |
Add option to configure incoming/outgoing stamps
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Add support for offline MUC notifications
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Sometimes this happened:
`ox d<tab>` → `/ox request`
`ox a<tab>` → `/ox request`
`ox c<tab>` → `/ox keys`
`ox s<tab>` → `/ox keys`
`ox e<tab>` → `/ox keys`
We didn't reset the ox_*_ac variables.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fix https://github.com/profanity-im/profanity/issues/1693
```
@StefanKropp @DebXWoody please check `_handle_ox_chat()` I don't
understand what you are doing there.
1)
First plain is assigned `message->plain =
p_ox_gpg_decrypt(xmpp_stanza_get_text(ox));`
and then in the same if block you overwrite this with `message->plain =
xmpp_stanza_get_text(b);` without freeing the old value as far as I can
see.
2)
Sometimes even doing `message->plain = "OX error: No payload found";`.
Shouldn't there be a `strdup()`? I think later on we try to free the
whole message struct. So we can't mix this static things.
```
|
|\ \ \
| | | |
| | | | |
Fix SIGABRT when using wrong argument order for receiving ox key
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Asserting here is not the right thing to do at all.
A person could have a typo in the fingerprint. Or like in the case of
the reported bug just confuse the arguments.
An additional check for valid jid should be added later to the calling
function maybe.
Fix https://github.com/profanity-im/profanity/issues/1698
|
| | | | |
|
| |/ / |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Fix xscreensaver detection
|
|/ /
| |
| |
| |
| |
| |
| | |
Using pkg-config to find libraries requires explicit mention of the
relevant _CFLAGS and _LIBS variables.
Fixes #1695.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Show return symbol for embedded newlines
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When editing multi-line messages or comments everything past the first
newline becomes invisible.
This patch fixes it by substituting a Unicode symbol for "return"
instead of printing the newline as is. On locales where it's not
available single backslash is used instead.
|