@@ -2471,76 +2471,6 @@ void dc_imex (dc_context_t* context, int what, c
24712471char * dc_imex_has_backup (dc_context_t * context , const char * dir );
24722472
24732473
2474- /**
2475- * Initiate Autocrypt Setup Transfer.
2476- * Before starting the setup transfer with this function, the user should be asked:
2477- *
2478- * ~~~
2479- * "An 'Autocrypt Setup Message' securely shares your end-to-end setup with other Autocrypt-compliant apps.
2480- * The setup will be encrypted by a setup code which is displayed here and must be typed on the other device.
2481- * ~~~
2482- *
2483- * After that, this function should be called to send the Autocrypt Setup Message.
2484- * The function creates the setup message and adds it to outgoing message queue.
2485- * The message is sent asynchronously.
2486- *
2487- * The required setup code is returned in the following format:
2488- *
2489- * ~~~
2490- * 1234-1234-1234-1234-1234-1234-1234-1234-1234
2491- * ~~~
2492- *
2493- * The setup code should be shown to the user then:
2494- *
2495- * ~~~
2496- * "Your key has been sent to yourself. Switch to the other device and
2497- * open the setup message. You should be prompted for a setup code. Type
2498- * the following digits into the prompt:
2499- *
2500- * 1234 - 1234 - 1234 -
2501- * 1234 - 1234 - 1234 -
2502- * 1234 - 1234 - 1234
2503- *
2504- * Once you're done, your other device will be ready to use Autocrypt."
2505- * ~~~
2506- *
2507- * On the _other device_ you will call dc_continue_key_transfer() then
2508- * for setup messages identified by dc_msg_is_setupmessage().
2509- *
2510- * For more details about the Autocrypt setup process, please refer to
2511- * https://autocrypt.org/en/latest/level1.html#autocrypt-setup-message
2512- *
2513- * @memberof dc_context_t
2514- * @param context The context object.
2515- * @return The setup code. Must be released using dc_str_unref() after usage.
2516- * On errors, e.g. if the message could not be sent, NULL is returned.
2517- */
2518- char * dc_initiate_key_transfer (dc_context_t * context );
2519-
2520-
2521- /**
2522- * Continue the Autocrypt Key Transfer on another device.
2523- *
2524- * If you have started the key transfer on another device using dc_initiate_key_transfer()
2525- * and you've detected a setup message with dc_msg_is_setupmessage(), you should prompt the
2526- * user for the setup code and call this function then.
2527- *
2528- * You can use dc_msg_get_setupcodebegin() to give the user a hint about the code (useful if the user
2529- * has created several messages and should not enter the wrong code).
2530- *
2531- * @memberof dc_context_t
2532- * @param context The context object.
2533- * @param msg_id The ID of the setup message to decrypt.
2534- * @param setup_code The setup code entered by the user. This is the same setup code as returned from
2535- * dc_initiate_key_transfer() on the other device.
2536- * There is no need to format the string correctly, the function will remove all spaces and other characters and
2537- * insert the `-` characters at the correct places.
2538- * @return 1=key successfully decrypted and imported; both devices will use the same key now;
2539- * 0=key transfer failed e.g. due to a bad setup code.
2540- */
2541- int dc_continue_key_transfer (dc_context_t * context , uint32_t msg_id , const char * setup_code );
2542-
2543-
25442474/**
25452475 * Signal an ongoing process to stop.
25462476 *
@@ -4659,7 +4589,10 @@ uint32_t dc_msg_get_info_contact_id (const dc_msg_t* msg);
46594589#define DC_INFO_GROUP_IMAGE_CHANGED 3
46604590#define DC_INFO_MEMBER_ADDED_TO_GROUP 4
46614591#define DC_INFO_MEMBER_REMOVED_FROM_GROUP 5
4592+
4593+ // Deprecated as of 2026-03-16, not used for new messages.
46624594#define DC_INFO_AUTOCRYPT_SETUP_MESSAGE 6
4595+
46634596#define DC_INFO_SECURE_JOIN_MESSAGE 7
46644597#define DC_INFO_LOCATIONSTREAMING_ENABLED 8
46654598#define DC_INFO_LOCATION_ONLY 9
@@ -4689,40 +4622,6 @@ uint32_t dc_msg_get_info_contact_id (const dc_msg_t* msg);
46894622char * dc_msg_get_webxdc_href (const dc_msg_t * msg );
46904623
46914624
4692- /**
4693- * Check if the message is an Autocrypt Setup Message.
4694- *
4695- * Setup messages should be shown in an unique way e.g. using a different text color.
4696- * On a click or another action, the user should be prompted for the setup code
4697- * which is forwarded to dc_continue_key_transfer() then.
4698- *
4699- * Setup message are typically generated by dc_initiate_key_transfer() on another device.
4700- *
4701- * @memberof dc_msg_t
4702- * @param msg The message object.
4703- * @return 1=message is a setup message, 0=no setup message.
4704- * For setup messages, dc_msg_get_viewtype() returns #DC_MSG_FILE.
4705- */
4706- int dc_msg_is_setupmessage (const dc_msg_t * msg );
4707-
4708-
4709- /**
4710- * Get the first characters of the setup code.
4711- *
4712- * Typically, this is used to pre-fill the first entry field of the setup code.
4713- * If the user has several setup messages, he can be sure typing in the correct digits.
4714- *
4715- * To check, if a message is a setup message, use dc_msg_is_setupmessage().
4716- * To decrypt a secret key from a setup message, use dc_continue_key_transfer().
4717- *
4718- * @memberof dc_msg_t
4719- * @param msg The message object.
4720- * @return Typically the first two digits of the setup code or an empty string if unknown.
4721- * NULL is never returned. Must be released using dc_str_unref() when done.
4722- */
4723- char * dc_msg_get_setupcodebegin (const dc_msg_t * msg );
4724-
4725-
47264625/**
47274626 * Gets the error status of the message.
47284627 * If there is no error associated with the message, NULL is returned.
0 commit comments