Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: add support for VB6 #1088

Open
SimonvanAs opened this issue Apr 26, 2024 · 3 comments
Open

Request: add support for VB6 #1088

SimonvanAs opened this issue Apr 26, 2024 · 3 comments
Labels
.NET Pull requests that update .net code status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@SimonvanAs
Copy link

Hi, as maintainer of a VB6 project and upcoming law in the EU (NIS2) we are obliged to have an SBoM. WOuld love to be able to integrate https://github.com/microsoft/sbom-tool (which uses the component-detection) in my build pipeline.
Any option to include that in the component-detection?

@cobya cobya added status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) .NET Pull requests that update .net code labels May 15, 2024
@cobya
Copy link
Contributor

cobya commented May 15, 2024

@SimonvanAs can you please provide some documentation on the related build package formats used by VB6? I'm unfamiliar with the tooling there.

@SimonvanAs
Copy link
Author

First I used Syft on the actual codebase that I had in a filelocation:
image
But that gave too little information, although it did see the VB virtual machine

We have now used DependencyWalker for the .exe analysis and the .dll decomposition. It looks like this:
DependencyWalker_NMEXPEDICION

I'm not sure this is the information you requested, but the build is done on a 32-bit Windows machine and as far as I'm concerned it 'just' creates .exe files

@dylanb6
Copy link

dylanb6 commented Aug 5, 2024

Hi,

This page from Microsoft is a resource regarding the dependencies used by VB6 programs. The use of .dep files under the packaging and setup wizard is a good thread to follow.

However, in the case that an application does not use these, I think it may be worth looking into the source files themselves (e.g. .vbp, .frm, .bas, etc). Opening a couple in Notepad++ yields a list of references and components used by that particular program or form. There's also this thread from VBForums regarding SBOMs for VB6.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.NET Pull requests that update .net code status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
Development

No branches or pull requests

3 participants