I built a 90.7kb tool that strips out Windows screen capture protection, but now I am concerned about whether I should make it open source. I'm worried it can be misused for piracy or to violate DRM policies.

I built it because I had a piece of software that wouldn't let me copy text. I tried using Windows OCR to copy it, but it just showed a black screen.

The tool is great for personal use, but it can be misused, so I am concerned. Any thoughts on this? Will I get into legal trouble if I make it public on GitHub?

I don't want to get into any trouble, so I need expert advice from someone who is experienced.

you are viewing a single comment's thread
view the rest of the comments

[–] hoshikarakitaridia@lemmy.world 17 points 1 week ago (1 children)

It really depends on if you think this is a genuine exploit or not. If it is, look up Microsoft's track record on complying with disclosure and make yourself familiar with responsible disclosure guidelines.

If it's not then you just need to look into the EULA of the specific windows parts affected, so they don't pull your repository. Because that's usually the biggest thing they do if you don't specifically start fights with these companies.

Generally, you're probably fine. If you want me to look over it I can give you my discord or fluxer or whatever. Not an expert, just a Cybersecurity enthusiast.

[–] Aditya_151@lemmy.world 5 points 1 week ago

It’s just simple injection, it does not break the Windows EULA but it may break the EULA for the applications you inject into.