Thanks. Our further clarification about the terminology.
We greatly appreciate your patient explanation, and now we clearly get the point that makes you confusing.
Firstly, we think the descriptions from Paragraph 3 to 5 (*i.e.*, *"The backdoor is a property ... compared to an undefended model."*) are very very clear, showing your deep understanding of backdoor learning.
However, in terms of the description *"but there remains a different backdoor"* in Paragraph 6, we would like to further discuss with you. Let's consider backdoor learning from the adversary's perspective.
* **The adversary's ultimate goal** is to cause a model to behave as it desires during inference, *i.e.*, predicting the poisoned sample that contains a trigger as the target label, while predicting clean samples correctly.
* To ahieve that goal, usually, the adversary should do **two steps**:
* **Step 1: Backdoor injection.** It aims to form a stable mapping from a trigger to the target label in a model, through manipulating the training dataset (*i.e.*, data poisoning based), manipulating the training process (*i.e.*, training controllable based), or manipulating both.
* **Step 2: Backdoor activation.** When the backdoored model is deployed by the model owner to provide query service to the customer, the adversary will try to activate the injected backdoor to achieve its goal, via querying the model with the poisoned sample containing a trigger.
* **What will happen if the backdoor activation fails?** There will be two results for the backdoor activation step, *i.e.*, **success** or **fail**. If success, then the adversary wins. If fail, what the adversary can do? Firstly, it may guess that some post-training defenses have been conducted by the owner on the backdoored model to change the parameters, such that the original mapping from the original trigger to the target label **cannot be activated**. Unfortunately, there is no chance for the adversary to change the model. **If the adversary aims to re-activate the backdoor, its only choice is changing the trigger, using our re-activation attack methods.** Although the new trigger is different with the trigger used in backdoor injection, and the model is also changed by the defender, the ultimate goal of the adversary has been achieved.
* **For backdoor attack, is it necessary to keep the trigger same in both backdoor injection and backdoor activation? Our answer is NO.** We notice that, in most existing backdoor attacks, there is one default setting that, the triggers used in backdoor injection and backdoor activation are same. But, is it really necessary? NO.
* Firstly, from the above description of the adversary's ultimate goal (or from previous backdoor learning works), we don't see such a requirement. Thus, changing this setting will not violate the definition of backdoor attack.
* Actually, this setting has been violated in a few existing works, such as Alpha-Blend [1] (where it calls asymmetric trigger), and distributed Backdoor attack [2]. However, note that their activated model is still the original backdoored model, and their succeeding reasons are mainly due to the trigger generalization phenomenon. They are intrinsically different with our re-activation attack, as the model has been changed by the defender, and the succeeding reason is also different (please refer to the common response, here we don't repeat).
**In summary**, from the adversary's perspective, we think it is reasonable to call our attack as **backdoor re-activation**, because its goal has been achieved, though the trigger is not exactly same with the trigger used in backdoor injection and the backdoored model is also changed by the defender.
We sincerely hope the above descriptions can make the terminology more clear. However, we will not insist on what it calls. The most important thing is to make real contribution to the field of backdoor learning. We believe, and you may have agreed with us that, **this work could attract the researchers' attention to re-investigate the effectiveness of post-training backdoor defenses, and inspire future works for safer defenses**.
The in-depth discussions with you are very enjoyful, and really helpful to make this work more solid. Greatly appreciated.
**References:**
[1] Revisiting the Assumption of Latent Separability for Backdoor Defenses. ICLR, 2023.
[2] Distributed Backdoor Attacks against Federated Learning. ICLR, 2019.