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

about image size #14

Open
payphone131 opened this issue Dec 10, 2024 · 2 comments
Open

about image size #14

payphone131 opened this issue Dec 10, 2024 · 2 comments

Comments

@payphone131
Copy link

An image generated by HADES needs to be resized when it is sent into the image processor of the victim MLLM. Do you think that resizing the adversarial noise part will reduce the jailbreak ability of the image? If so, is it better to let the image size consistent with the default image size of the image processor when adding adversarial noise to it? Since the final image doesn't have to be resized when sent into the victim MLLM in this way.

@AoiDragon
Copy link
Owner

Hello @payphone131,
We agree with your point about image resolution. In practice, instead of optimizing and then attaching the blank image, we first attach the blank image to the original image before performing gradient updates. This ensures that the size of the adversarial image remains consistent with the training process.

@payphone131
Copy link
Author

Thanks, what you say really helps. But I still wonder whether it will reduce the jailbreak ability of HADES if the victim MLLM uses an image processor demanding a fixed image size (such as 224*224) while the output images of HADES are not of this size.

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

2 participants