@@ -2494,76 +2494,6 @@ void dc_imex (dc_context_t* context, int what, c
24942494char * dc_imex_has_backup (dc_context_t * context , const char * dir );
24952495
24962496
2497- /**
2498- * Initiate Autocrypt Setup Transfer.
2499- * Before starting the setup transfer with this function, the user should be asked:
2500- *
2501- * ~~~
2502- * "An 'Autocrypt Setup Message' securely shares your end-to-end setup with other Autocrypt-compliant apps.
2503- * The setup will be encrypted by a setup code which is displayed here and must be typed on the other device.
2504- * ~~~
2505- *
2506- * After that, this function should be called to send the Autocrypt Setup Message.
2507- * The function creates the setup message and adds it to outgoing message queue.
2508- * The message is sent asynchronously.
2509- *
2510- * The required setup code is returned in the following format:
2511- *
2512- * ~~~
2513- * 1234-1234-1234-1234-1234-1234-1234-1234-1234
2514- * ~~~
2515- *
2516- * The setup code should be shown to the user then:
2517- *
2518- * ~~~
2519- * "Your key has been sent to yourself. Switch to the other device and
2520- * open the setup message. You should be prompted for a setup code. Type
2521- * the following digits into the prompt:
2522- *
2523- * 1234 - 1234 - 1234 -
2524- * 1234 - 1234 - 1234 -
2525- * 1234 - 1234 - 1234
2526- *
2527- * Once you're done, your other device will be ready to use Autocrypt."
2528- * ~~~
2529- *
2530- * On the _other device_ you will call dc_continue_key_transfer() then
2531- * for setup messages identified by dc_msg_is_setupmessage().
2532- *
2533- * For more details about the Autocrypt setup process, please refer to
2534- * https://autocrypt.org/en/latest/level1.html#autocrypt-setup-message
2535- *
2536- * @memberof dc_context_t
2537- * @param context The context object.
2538- * @return The setup code. Must be released using dc_str_unref() after usage.
2539- * On errors, e.g. if the message could not be sent, NULL is returned.
2540- */
2541- char * dc_initiate_key_transfer (dc_context_t * context );
2542-
2543-
2544- /**
2545- * Continue the Autocrypt Key Transfer on another device.
2546- *
2547- * If you have started the key transfer on another device using dc_initiate_key_transfer()
2548- * and you've detected a setup message with dc_msg_is_setupmessage(), you should prompt the
2549- * user for the setup code and call this function then.
2550- *
2551- * You can use dc_msg_get_setupcodebegin() to give the user a hint about the code (useful if the user
2552- * has created several messages and should not enter the wrong code).
2553- *
2554- * @memberof dc_context_t
2555- * @param context The context object.
2556- * @param msg_id The ID of the setup message to decrypt.
2557- * @param setup_code The setup code entered by the user. This is the same setup code as returned from
2558- * dc_initiate_key_transfer() on the other device.
2559- * There is no need to format the string correctly, the function will remove all spaces and other characters and
2560- * insert the `-` characters at the correct places.
2561- * @return 1=key successfully decrypted and imported; both devices will use the same key now;
2562- * 0=key transfer failed e.g. due to a bad setup code.
2563- */
2564- int dc_continue_key_transfer (dc_context_t * context , uint32_t msg_id , const char * setup_code );
2565-
2566-
25672497/**
25682498 * Signal an ongoing process to stop.
25692499 *
@@ -4682,7 +4612,10 @@ uint32_t dc_msg_get_info_contact_id (const dc_msg_t* msg);
46824612#define DC_INFO_GROUP_IMAGE_CHANGED 3
46834613#define DC_INFO_MEMBER_ADDED_TO_GROUP 4
46844614#define DC_INFO_MEMBER_REMOVED_FROM_GROUP 5
4615+
4616+ // Deprecated as of 2026-03-16, not used for new messages.
46854617#define DC_INFO_AUTOCRYPT_SETUP_MESSAGE 6
4618+
46864619#define DC_INFO_SECURE_JOIN_MESSAGE 7
46874620#define DC_INFO_LOCATIONSTREAMING_ENABLED 8
46884621#define DC_INFO_LOCATION_ONLY 9
@@ -4712,40 +4645,6 @@ uint32_t dc_msg_get_info_contact_id (const dc_msg_t* msg);
47124645char * dc_msg_get_webxdc_href (const dc_msg_t * msg );
47134646
47144647
4715- /**
4716- * Check if the message is an Autocrypt Setup Message.
4717- *
4718- * Setup messages should be shown in an unique way e.g. using a different text color.
4719- * On a click or another action, the user should be prompted for the setup code
4720- * which is forwarded to dc_continue_key_transfer() then.
4721- *
4722- * Setup message are typically generated by dc_initiate_key_transfer() on another device.
4723- *
4724- * @memberof dc_msg_t
4725- * @param msg The message object.
4726- * @return 1=message is a setup message, 0=no setup message.
4727- * For setup messages, dc_msg_get_viewtype() returns #DC_MSG_FILE.
4728- */
4729- int dc_msg_is_setupmessage (const dc_msg_t * msg );
4730-
4731-
4732- /**
4733- * Get the first characters of the setup code.
4734- *
4735- * Typically, this is used to pre-fill the first entry field of the setup code.
4736- * If the user has several setup messages, he can be sure typing in the correct digits.
4737- *
4738- * To check, if a message is a setup message, use dc_msg_is_setupmessage().
4739- * To decrypt a secret key from a setup message, use dc_continue_key_transfer().
4740- *
4741- * @memberof dc_msg_t
4742- * @param msg The message object.
4743- * @return Typically the first two digits of the setup code or an empty string if unknown.
4744- * NULL is never returned. Must be released using dc_str_unref() when done.
4745- */
4746- char * dc_msg_get_setupcodebegin (const dc_msg_t * msg );
4747-
4748-
47494648/**
47504649 * Gets the error status of the message.
47514650 * If there is no error associated with the message, NULL is returned.
@@ -6339,7 +6238,7 @@ void dc_event_unref(dc_event_t* event);
63396238 * should not be disturbed by a dialog or so. Instead, use a bubble or so.
63406239 *
63416240 * However, for ongoing processes (e.g. dc_configure())
6342- * or for functions that are expected to fail (e.g. dc_continue_key_transfer())
6241+ * or for functions that are expected to fail
63436242 * it might be better to delay showing these events until the function has really
63446243 * failed (returned false). It should be sufficient to report only the _last_ error
63456244 * in a message box then.
0 commit comments