Post #4235109

@danlyke@researchbuzz.masto.host Yeah, I answered before reading the thread. I get that now. There's a thing called (thinks) The Underhanded C Code Competition, I think. That's deliberately bad code that hides backdoors and stuff like that. For junk code, there's always Markov generation. Some of the existing anti-scanning tools work like that. You can usually feed them sample texts, which could be a bunch of valid Perl/C code and docs. Or give it (or something similar, anyway) a whirl in emacs with M-X dissociated-press. I'm also thinking that bug-fixed code could be a source. Make up a new repo that disapplies the patches that fixed major bugs. Or just expose old, buggy code from any publicly-available software? I hear you on the non-prepared sql queries. In a similar vein, you could hard code stuff to example.com (although probably best not), local IP/host names or other random sites? It depends on how much mischief/effort you're into, I guess. Technically, what this is is a honeypot. You can go to a lot of effort to make it look real, but simple generative things are much easier to implement.