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
inswapper_128.onnx in the wild - please verify the hashsums? #2315
Comments
so which one is the correct? |
@felixsanz it's a single file, but I printed out both the SHA256 and MD5 hashes so that the deepinsight devs could verify |
I will not officially support this model due to the substantial risks associated with video deepfakes. |
Well, the risk of deepfakes is still there (model is public), you are just supporting the risk of malware and ransomware not saying what the correct hash it. Also there is more deepfakes generation software like https://github.com/neuralchen/SimSwap, so deepfakes will exist anyway And remember this is a tool. A knife can also kill a lot of people. It's not the tool but how you use it. There is nothing wrong or harmful on this |
Yeah, i mean which correct hashes have the official model, either sha256 or md5sum |
In the past few weeks you've said you won't release or support this model publicly due to a) the imminent release of a paper, b) because your Discord bot offers superior quality to the 128x128 model, and now c) the risk of video deepfakes. I'll admit I am somewhat skeptical of all of these excuses. Anyway, I am commenting to confirm that the checksums in the original post by @chrisbward match the version of the model I previously downloaded from the official links before they were removed. |
I have too many versions of the model, making it impossible to confirm. There are over ten models at a resolution of 128 alone, and I simply chose one at random at the time. |
but your discord bot generate them, right? |
discord bot only generates images |
Btw it's not impossible, it's just:
To confirm this model on the internet is malicious or not. People can use it anyway but you can avoid a lot of bad things |
could you perhaps provide instructions on how to train it from scratch then with some sample data to start? |
@nttstar |
Hi @nttstar - it's too late, the model is out there and if you do not publish the hashes then the risk of malware being distributed is far greater! We're not asking you to publish the model, just the hashes. Thanks |
please @nttstar |
paid services are providing 100% quality sound cloning and face cloning i think best way to combat is educating everyone and i am 100% sure malicious actors have already much better models at their hands by the way from this repo i feel like the aim was mass surveillance to help chinese government :d |
"discord bot only generates images" hosently that's not a good excuse, people will create fake discord accounts to bybass the 50 images per-day per-account rules then join frames with ffmpeg & interpolate the frames with another free tool, they could also bypass any nsfw filters by masking the target video then overlaying results with the original footage. So if you truley belive roop 'an easily detectable swapping tool' is bad then you might as well delete your discord for the saftey concerns you keep mentioning due to the supiror deepfake qaulity you provide free of charge to anybody with a computer, or at the very least limit the amount of image swaps per day to 6. |
I will no longer answer questions about this model, but this issue will not be closed for the time being. You are free to discuss here. |
WARNING - DO NOT USE THIS VERSION OF ROOP I have jailed the binary inside a Docker container and will be forking/porting to Golang. |
what does that mean? |
But there's already more popular deepfake repos so i don't see the point |
Regardless if you guys have pulled the model for any which reason, it's probably best to verify the hashes below so that people don't download anything malicious?
Below is the version I discovered, matching another copy in the wild.
The text was updated successfully, but these errors were encountered: