RE: Busybox identification
ale5000 via busybox <[email protected]>
| Newsgroups | gmane.linux.busybox |
|---|---|
| Message-ID | <CAAUzaA+QTWwSfeYN5w02pqJ+c-WxZ6d=Kb7cM3rFXasOmaQgXQ@mail.gmail.com> |
> Hi > I work for a team that audits software. This includes Docker Images, many that contain Busybox. I believe all the other Linux Operating Systems use the os-release file to identify which version of the OS is installed. > > My understanding is that Busybox does not do this as it sees itself as a collection of utilities that ‘acts’ like an OS, just in a very stripped-down way. > > Using the os-release file allows us to correctly identify which OS we are processing and how to ID all the packages in it. > > Is there any way Busybox can be identified as being the 'installed OS’ other than if it was listed in an os-release file? > >It would significantly make our processing much simpler. I don't know if it helps but you can grep /etc/shells to get the list of shells and it is possible that busybox is in it in some way but I'm not sure. In the latest code of BusyBox there is a "--version" parameter but it was added recently and probably there isn't yet any stable release wth it. If it can help I have created a shell script that works on any OS and it is able (beside the other functions) to parse binary files and detect binary type: https://github.com/micro5k/microg-unofficial-installer/blob/main/tools/bits-info.sh _______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox