> Copyright law is pretty scary around anti-circumvention rules – putting the name of the software right in an article about how to break its DRM/licensing just sounds like asking for trouble, so I never do. (Not legal advice – just my personal musings!)
> At least if the software is unnamed, the article is clearly more for educational purposes – you won't find the article if you've got the software and you're trying to break it, and you won't have access to the software if you're just reading the article.
Then again, I also exercised my skills from the Fravia/Searchlores era ;-)
Out of benign curiousity, was the software...?
- Industrial/control oriented (talking to bespoke hardware)
- An "internal" B2B line of business thing
- An off-the-shelf/productized/marketed piece of software
I suspect the latter.
I'm naturally also curious what it was for, but I suspect that even generally scoping that would make identification significantly easier for a large majority of people, so I'll leave it there :)
The broader point to make is that this is a general policy of mine – I deidentify all software that I discuss in any of my RE writeups. Having a blanket policy avoids needing to make ultimately arbitrary decisions about what to name and what not to name – and in any case, not naming the software doesn't prevent anyone from reading the writeup and taking inspiration from it if they choose.
I've always felt the biggest mistake people make is thinking no one is looking at their ramblings.