113 Commits

Author	SHA1	Message	Date
Jabber Developer	756d4e18cf	fix(accounts): complete client.name to client.account_name rename ... The previous rename of the account option key left "client.name" in accounts_set_client() and accounts_clear_client(), preventing the option from being set/cleared. Update both functions to use the correct "client.account_name" key. Note: existing configurations with the old key will not be migrated automatically; a migration fix will follow.	2026-07-08 11:00:31 +00:00
Jabber Developer	830479cf20	fix: OTR/presence/OMEMO correctness, stanza-id disco gate, build hardening ... - OTR: strip the whitespace tag by shifting the full message tail incl. the NUL, not tag_length bytes, so the body is no longer duplicated for messages longer than the tag. - presence: snapshot the resource fields before connection_add_available_resource() takes ownership, removing a use-after-free in the own-presence path. - OMEMO: propagate _omemo_finalize_identity_load() failure on connect (log + cons_show_error + stop) instead of leaving OMEMO silently unavailable. - OMEMO: guard NULL fingerprint decode in _omemo_fingerprint_decode / omemo_is_trusted_identity / omemo_trust and log every decode failure instead of failing silently. - stanza-id: gate XEP-0359 dedup on disco urn:xmpp:sid:0 (the `by` JID or its domain), falling back to no-dedup when caps are unknown; add functional tests for trusted vs untrusted server. - accounts: narrow the group-name sanitizer to the characters GKeyFile forbids in headers ([ ] \n \r), keeping `=` and `#`, so read/write stays symmetric. - build: re-introduce compiler/sanitizer flags in a Pikaur-safe form (opt-in sanitizers, -Wsign-compare) and fix the resulting -Wsign-compare warnings (incl. proftest _mkdir_recursive).fix: OTR/presence/OMEMO correctness, stanza-id disco gate, build hardening Author: jabber.developer2 <jabber.developer2@jabber.space>	2026-06-20 10:30:23 +00:00
Jabber Developer	72f4f186da	merge: sync upstream profanity-im/profanity ... Sync with upstream profanity-im/profanity. Major upstream changes incorporated: Memory management - Replace malloc+memset with g_new0 throughout codebase - Adopt auto_gchar / auto_gcharv / auto_gerror / auto_jid cleanup macros - Replace free() with g_free() for GAlloc'd memory Editor rewrite - Remove pthread-based async editor; use GChildWatch callback API - New launch_editor(initial_content, callback, user_data) interface - Proper signal handling (SIGINT, SIGTSTP, SIGPIPE reset in child) - ui_suspend()/ui_resume() integration for TTY management OMEMO improvements - Dual backend support: libsignal-protocol-c and libomemo-c - Proper pre-key removal after use (XEP-0384 compliance) - Automatic pre-key regeneration when store drops below threshold - New functions: omemo_is_device_active(), omemo_is_jid_trusted() - omemo_get_jid_untrusted_fingerprints() for better error messages - Fingerprint notifications on new device identity discovery - Deterministic pre-key ID generation tracking max_pre_key_id - omemo_trust_changed() UI updates on trust state changes JID validation - RFC 6122-compliant validation in jid_is_valid() - Character-level checks (RFC 6122 forbidden chars: & ' / : < > @) - Length limits: 1023 per component, 3071 total - New jid_is_valid_user_jid() for user vs. service JID distinction Database - Schema migration v3: UNIQUE constraint on archive_id for deduplication - Triggers for corrected message tracking (replaces_db_id / replaced_by_db_id) - db_history_result_t return type, _truncate_datetime_suffix() UI / console - win_warn_needed() / win_warn_sent() warning deduplication hash table - PAD_MIN_HEIGHT dynamic pad sizing with PAD_THRESHOLD auto-cleanup - Spellcheck integration in input field with Unicode word detection - cons_spellcheck_setting() for /settings ui output - /[command]? shortcut for command help Account config - Account name sanitization for GKeyFile special chars ([ ] = # \n \r) - Replace popen() with g_spawn_sync() for eval_password - TLS policy: add "direct" option alongside legacy Connection - Port validation with g_assert (0–65535) - SHA-256 certificate fingerprint support (XMPP_CERT_PUBKEY_FINGERPRINT_SHA256) - "direct" TLS policy alias for legacy SSL Common utilities - str_xml_sanitize() for XML 1.0 illegal character removal - string_matches_one_of() with formatted error messages - valid_tls_policy_option() helper - prof_date_time_format_iso8601() utility - Improved strip_arg_quotes() with backslash unescaping - prof_occurrences() uses g_slist_prepend + reverse for performance PGP / OX - Proper GPGME resource cleanup with goto-cleanup pattern - g_string_free(xmppuri) leak fix in _ox_key_lookup CSV export - Use GString + g_file_set_contents instead of raw write() syscalls Tests - Restructured into subdirectories: command/, config/, xmpp/, ui/, omemo/, otr/, pgp/ - New test_cmd_ac.c for autocompleter unit tests - Updated stubs for new UI suspend/resume functions License headers - Migrate to SPDX-3.0 identifiers (GPL-3.0-or-later WITH OpenSSL-exception) ──────────────────────────────────────────────────── cproof-specific preservations: - XEP-0308 LMC: replace_id ?: id logic in message/stanza/omemo - Force encryption: cmd_force_encryption, test_forced_encryption - CWE-134: format string protection (cons_show("%s", ...)) - y_start_pos-based paging in window.c - db_history_result_t return type, _truncate_datetime_suffix() Merge-time fixes: - common.c: format-security (-Werror) — cons_show(errmsg) → cons_show("%s", errmsg) - database.c: null-deref guard — !msg->timestamp → msg && !msg->timestamp - console.c: implicit size_t → int cast — (int)(maxlen + 1) - tlscerts.c: %d for size_t — %zu Build system: - Kept autotools (Makefile.am, configure.ac); upstream uses Meson - Restored deleted files: bootstrap.sh, autogen.sh, ax_valgrind_check.m4, configure-debug - Updated Makefile.am test paths for subdirectory structure - Added test_cmd_ac, test_forced_encryption to test sources Functional tests: - Use cproof version; upstream requires stbbr_for_xmlns from updated stabber - Not yet available in devs/stabber fork Closes #64 Merge author: jabber.developer2 Commits authors: Michael Vetter <jubalh@iodoru.org> & Steffen Jaeckel <s@jaeckel.eu>	2026-05-26 17:48:14 +00:00
Michael Vetter	07dfeec816	Release 0.15.0	2025-03-27 20:06:38 +01:00
Steffen Jaeckel	c5a131ee46	Introduce our own shutdown callback mechanism. ... Instead of adding stuff to `_shutdown()`, we can now register a shutdown routine from the respective `init()` function of our modules. This also has the advantage, that we're sure they're called in reverse order from how the initialization happened. I didn't simply use `atexit()` because POSIX says that the number of possible callbacks is limited (min 32) and I was not sure whether we will maybe extend this number at one point. Signed-off-by: Steffen Jaeckel <s@jaeckel.eu>	2025-03-07 21:09:16 +01:00
Michael Vetter	569e37f018	Update copyright to 2024	2024-01-22 16:03:48 +01:00
Steffen Jaeckel	b4c088232e	Improve const correctness ... Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>	2023-12-12 18:27:09 +01:00
Steffen Jaeckel	2b29d1baf3	Fix some glib nullptr-check warning messages ... Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>	2023-10-04 17:02:10 +02:00
Steffen Jaeckel	ca2df180d8	Introduce a shared implementation for keyfile loading ... Instead of copy&pasting the same code over again, use a common implementation. Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>	2023-09-04 09:59:09 +02:00
John Hernandez	865a056315	Cleanup g_strfreev() to auto_gcharv ... Include some additional minor cleanups	2023-07-13 17:05:07 +02:00
John Hernandez	029f1caa52	Cleanup jid_destroy to auto_jid ... Remove unused variables Apply minor cleanups	2023-07-13 17:05:07 +02:00
John Hernandez	8304ac86ff	g_free() to auto_gfree, introduce auto_guchar ... Fix 11 potential mem leaks in theme.c	2023-07-13 17:04:59 +02:00
John Hernandez	e1d137f4e6	Change char->free to auto_char char for autocleanup ... Replace `gchar` and `g_free` to `auto_gchar` Correct certain `char` functions/variables to `gchar` Related to #1819. Edited by @jubalh.	2023-07-11 13:26:37 +02:00
John Hernandez	07cc19ce10	Add sessions_alarm ... Introduce new feature: sessions_alarm. Added new account setting: max_connections. On exceeding this number, user will get an alert. If number is less than 1, no alert will happen. Tests altered to fit new feature.	2023-04-18 14:28:20 +02:00
John Hernandez	5d3c8ce7c1	Allow setting client identification name/version manually ... Add changes allowing user to switch client name and version. Useful for enhancing user privacy. Minor cleanup.	2023-04-09 14:17:01 +02:00
Steffen Jaeckel	302d0dd576	let account_new() take ownership of passed values ... Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>	2023-01-18 20:02:46 +01:00
Michael Vetter	3adc399da0	Update copyright year	2023-01-10 10:37:25 +01:00
Michael Vetter	14a2fb6e72	accounts: deduplicate code via helper function	2022-06-29 12:30:05 +02:00
MarcoPolo-PasTonMolo	e4e53d6e01	Don't forget encryption status for OX and PGP. ... Use a pgp.enabled and ox.enabled array the same way that omemo.enabled is used. Fixes https://github.com/profanity-im/profanity/issues/1694 Fixes https://github.com/profanity-im/profanity/issues/733	2022-06-17 15:43:54 +03:00
Michael Vetter	9bd635d7e6	accounts: get rid of guard around free	2021-07-17 23:13:01 +02:00
Dmitry Podgorny	e7b6051e57	Fix memory leak in accounts_get_login_status()	2021-07-17 18:11:32 +03:00
Thorben Günther	0fc3343d75	Restore last status string when connecting	2021-07-01 16:08:00 +02:00
Michael Vetter	057c9ad776	Add config.h in files were it was missing ... Related to https://github.com/profanity-im/profanity/issues/1512	2021-03-26 19:54:22 +01:00
Michael Vetter	35aecd425f	Declare counter var inside loop ... We require c99/gnu99 anyways.	2020-11-09 11:33:33 +01:00
Michael Vetter	304f63f204	Dont initialize i twice in accounts_get_account()	2020-11-05 09:38:57 +01:00
Michael Vetter	a2726b6a7d	Apply coding style	2020-07-07 14:18:57 +02:00
Michael Vetter	a4cadf78fa	Revert "Apply coding style" ... This reverts commit 9b55f2dec0. Sorting the includes creates some problems.	2020-07-07 13:53:30 +02:00
Michael Vetter	9b55f2dec0	Apply coding style ... Regards https://github.com/profanity-im/profanity/issues/1396	2020-07-07 09:43:28 +02:00
Michael Vetter	914c6752dd	Fix reading/writing linked files ... "base" was not really base but the filename :-) Fix https://github.com/profanity-im/profanity/issues/1362	2020-06-13 15:02:43 +02:00
Dmitry Podgorny	ac410445af	Add option for legacy authentication ... New options: /connect <account> [auth default|legacy] /account <account> set auth default|legacy Fixes #1236.	2020-06-05 11:37:51 +03:00
Paul Fariello	a52e3ea1d8	Add context to autocomplete_with_func and use it for omemo trust command ... Fix #1068	2020-01-31 10:07:08 +01:00
Michael Vetter	46fd7150e5	Add vim modeline	2019-11-13 12:11:05 +01:00
Paul Fariello	5f015e32b2	Add OMEMO policy ... There is 3 policy: - manual: OMEMO session are only started manually - automatic: OMEMO session are only started if they have been started manually before - always: OMEMO session are always started unless they have been ended manually before Closes #1040 and fixes #1052	2019-04-17 14:03:14 +02:00
Paul Fariello	9714d1d867	Add random string at the end of the default resource ... When connecting for the first time or when creating a new account don't use only 'profanity' as default resource. Some server don't support having 2 connection with same resource. Using profanity as default lead to deconnections.	2019-04-12 15:49:54 +02:00
Michael Vetter	706af9a900	Update copyright to include 2019	2019-01-22 11:31:45 +01:00
Dmitry Podgorny	7f65aaa9a2	Add option to trust server's certificate ... New tls policy "trust" added to /connect and /account. With the policy TLS connection is established even with invalid certificate. Note, that trust policy forces TLS connection and it fails when server doesn't support TLS. Examples: /connect <jid> tls trust /account <name> set tls trust	2018-11-06 14:09:02 +02:00
James Booth	250e972b7a	Update copyright	2018-01-21 15:00:02 +00:00
Dmitry Podgorny	1012e11283	Legacy SSL support ... Add "legacy" tls policy to /account and /connect commands. When this policy is specified the connection is connected with XMPP_CONN_LEGACY_SSL flag. Notice, legacy SSL and STARTTLS are not compatible and user has to know when exactly the new policy should be used. To enable it, run one of the next commands: /connect <jid> tls legacy [server <host>] /account <name> set tls legacy Notice, there is no SRV record for legacy SSL. Therefore, you may need "server" property to connect successfully. Refer to configuration provided by your server.	2017-06-24 21:33:30 +03:00
James Booth	6b830277a6	Allow previous autocompletion with shift tab	2017-04-01 00:27:11 +01:00
James Booth	68a3daedb9	Update Copyright	2017-01-28 17:24:22 +00:00
James Booth	e043029a50	Allow clearing account resource ... issue #880	2016-11-22 00:39:52 +00:00
James Booth	609d05366c	Use server features for account muc service ... issue #878	2016-11-20 02:09:34 +00:00
James Booth	a3a73cf003	Move all filepath handling to files.c	2016-07-24 21:49:35 +01:00
James Booth	29452f8f1b	Move xgd functions	2016-07-24 17:12:09 +01:00
James Booth	ef942bd27a	Add config/files.c	2016-07-24 16:22:15 +01:00
James Booth	0a57c4de78	Tidy headers	2016-07-24 15:43:51 +01:00
James Booth	1c5efaeb58	Moved jid.c	2016-07-24 14:59:28 +01:00
James Booth	e8fc80f5c1	Update GPL link in headers	2016-07-24 01:14:49 +01:00
James Booth	e53e94f1e2	Updated copyright	2016-02-14 22:54:46 +00:00
James Booth	53fc89f711	Added account theme property	2016-01-22 01:06:28 +00:00