Earlier quoted context omitted.
> If you did so too, you would've read the message from github which says "...disallow usage of camo to disclose sensitive victim user content" They use "camo" to proxy all image urls, but they in fact did remove the rendering of all inline images in markdown, removing the ability to exfil data using images. > Now why on earth would I take all the effort to come up with a new way of fooling this stupid AI only to giv…
I'm not sure how you could arrive at the conclusion that I've discovered any technique involving copilot whatsoever. Feel free to spout more nonsense. I was somewhat puzzled and dismayed at first, but now it amuses me.
CamoLeak: Critical GitHub Copilot Vulnerability Leaks Private Source Code
41–44 of 44 posts
Re: CamoLeak: Critical GitHub Copilot Vulnerability Leaks Private Source Code
#42Earlier quoted context omitted.
I'm not sure how you could arrive at the conclusion that I've discovered any technique involving copilot whatsoever. Feel free to spout more nonsense. I was somewhat puzzled and dismayed at first, but now it amuses me.
Because we know exactly what you did and the whole copilot team is laughing at you now! The base64 encoded source code you md5 hashed into our mainframe, you know what you did there is no denying it now. You are on thin ice buddy!
Re: CamoLeak: Critical GitHub Copilot Vulnerability Leaks Private Source Code
#43Earlier quoted context omitted.
Because we know exactly what you did and the whole copilot team is laughing at you now! The base64 encoded source code you md5 hashed into our mainframe, you know what you did there is no denying it now. You are on thin ice buddy!
What the fuck?