Re: Busybox identification
"Roberto A. Foglietta via busybox" <[email protected]>
| Newsgroups | gmane.linux.busybox |
|---|---|
| Message-ID | <CAJGKYO51Mfxcn0SBzcAFgn7iXrDuu=xZwDEi8ioQJ1Td4=FROA@mail.gmail.com> |
On Wed, 25 Mar 2026 at 16:19, Nigel Hopper via busybox <[email protected]> wrote: > > Hi > > Thank you. I guess I should have been clearer. My apologies. We save Docker images to disk and then unpack them and explore them as a file system to identify what is in them. From a layer perspective this works as we have to identify anything in each of the layers, even if the intent was to delete them. > > This will rule out running any commands in the Docker image and just relying on what can be found in the file system and its structure. Then you are searching for an executable, not just a path that can be a link. Also libraries are somehow a kind of executables, also scripts in various languages. Usually the command "file" coupled with a good signature databases is able to identify the nature of the file. Note that scripts are text, when they haven't the execution bit enabled nor shebang. However, I do not think that busybox is the correct place for this debate about what is an OS or an executable in strict or generic terms. IMHO, obviously. Best regards, -- Roberto A. Foglietta +49.176.274.75.661 +39.349.33.30.697