Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CW L2 attack uses predictions instead of logits #618

Open
ines21 opened this issue Feb 22, 2021 · 3 comments
Open

CW L2 attack uses predictions instead of logits #618

ines21 opened this issue Feb 22, 2021 · 3 comments
Assignees

Comments

@ines21
Copy link

ines21 commented Feb 22, 2021

Running the Carlini and Wagner attack, I was having less success than the paper stated. I noticed that the implementation in Foolbox was using the final normalised predictions instead of the unnormalised logits, which makes the attack less effective than it is supposed to be (especially against defensive distillation).

This might be the task of the person running the attack to pass a logits model, but it is still worth mentioning maybe in the documentation?

@jangop
Copy link

jangop commented Jan 28, 2022

If I am not mistaken, this does not only pertain to CW, correct?

This should definitely be mentioned in the documentation, and it might even be worthwhile to include a heuristic check when initializing an fmodel to ensure that the final layer does not resemble softmax. I remember doing something similar (in a different context) when comparing several pretrained models to ensure all gave me logits.

@zimmerrol
Copy link
Member

I agree that the documentation should be more concreate in that regard. I suppose it makes sense to overhaul the documentation, soon. We can collect these ideas in #654.

@ines21
Copy link
Author

ines21 commented Jan 28, 2022

yep @jangop that is what I ended up implementing myself. It is been a long time since I was working on this project, but if I remember correctly lots of other attacks were working well for softmax models. C&W was the one for which this was crucial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants