diffusionbee-stable-diffusion-ui VS fickling

Got the no-unpickling weight extractor working, you can see it here. Currently everything is in the two no_pickle_ files, but I'll probably be pushing a version up that puts them into convert_model.py and fake_torch.py, with an option passed to convert_model determining whether unpickling is used. I made another branch (visible from my GitHub profile) with a proper restricted unpickler, that the forthcoming push will merge into this.

You're right! You should probably use Trail of Bits Fickling tool to investigate. https://github.com/trailofbits/fickling

I tested the Anything V3 pruned from Hugging Face, and indeed nothing funny in its pickle. I used the Fickling library to decompile it. I do not use Windows so my interests in .ckpt security are largely related to Pickle exploits— which could extract malicious code from a data file and then do something with it, but the data files themselves are not executed. I will edit this comment with lines referencing that data file.

I've been using Diffusion Bee on my Mac, and it's just gained the ability to import models (which it converts), but it is unpickling to do so— but barely. It unpickles, figures out what sort of data is in every data file and then computes what it wants from them on its own. I would love it to not use unpickling at all, so my intention is if I can figure it out, to write a script to decode the pickle file (with Fickling or otherwise) and then just do the weight calculation/assignment.

Something you won't gather from skim-reading the headline is that this is that the author has also created a tool, Fickling: https://github.com/trailofbits/fickling - to aid in playing around with pickle files.

From the article: [Fickling] can help you reverse engineer, test, and even create malicious pickle files.