Busybox identification
Nigel Hopper via busybox <[email protected]>
| Newsgroups | gmane.linux.busybox |
|---|---|
| Message-ID | <IA0PPF5259F06B7A77741825034812A4524C549A@IA0PPF5259F06B7.namprd15.prod.outlook.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. Kind regards, Nigel Hopper Security Consultant: Cybersecurity Assessment & Response Services Open Source Software Auditor Advisory Software Engineer QSE Development Top Gun My working week is Tuesday to Friday. [signature_1589533700] E-mail: [email protected]<mailto:[email protected]> Security and Legal Scanning Services IBM UK Ltd, Mail Point 168, Hursley Park, Winchester, Hampshire SO21 2JN "One person with a belief is equal to a force of ninety-nine who only have interest." "What distinguishes the majority of men from the few is their inability to act according to their beliefs." - John Stewart Mill 1806 –1873 IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN _______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox
img-5ba34267-ea5b-40c6-87ed-dd0388190870
(application/octet-stream, 14.1 KB) - not displayed