Live data from Hacker News

Ask HN: How do you detect license infringement on closed source software?

news.ycombinator.com

1–6 of 6 posts

Re: Ask HN: How do you detect license infringement on closed source software?

#3
post #2

Bugs and symbols. There's a mac command line tool I can't remember the name of that pulls all the readable (and more) text from an application, this has been used to find out what made a closed source app (e.g. private iOS apis).

Is it maybe the strings utility: https://linux.die.net/man/1/strings?

Re: Ask HN: How do you detect license infringement on closed source software?

#4
post #2

Bugs and symbols. There's a mac command line tool I can't remember the name of that pulls all the readable (and more) text from an application, this has been used to find out what made a closed source app (e.g. private iOS apis).

Is it maybe the strings utility: https://linux.die.net/man/1/strings ?

There's also nm(1) and objdump(1).

Re: Ask HN: How do you detect license infringement on closed source software?

#6
post #4

Earlier quoted context omitted.

Is it maybe the strings utility: https://linux.die.net/man/1/strings ?

There's also nm(1) and objdump(1).

There are also tools which are platform specific. On macOS, for e.g., the Mach-O format can be disassembled by `otool`, for objective-c projects (and maybe Swift) you can use `class-dump`