You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are attempting to generate SBOM using sbom-tool in our GitLab jobs using powershell within windows docker container, but receive the following error message:
Since dotnet publish was able to create the folder and write into it and other commands such as Compress-Archive -Path wpf_client -DestinationPath ProfiSignalDesktop.zip -Force are able to read the folder, we assume that read permissions are not the issue in our case.
It seems that the source code checking folder permissions is missing logging statements and simply returns false in case of exceptions. This might lead to false reports of missing permissions eventhough the actual problem is somewhere else.
Without any logs we currently do not know why sbom-tool is failing.
@DelphinRP, version 2.2.5 has been released. Please give it a try to see if the logging reveals more details about what is failing in the directory check. If it's still failing, please feel free to open a new issue with the failure details. Thanks!
Hello everyone,
we are attempting to generate SBOM using sbom-tool in our GitLab jobs using powershell within windows docker container, but receive the following error message:
Since
dotnet publish
was able to create the folder and write into it and other commands such asCompress-Archive -Path wpf_client -DestinationPath ProfiSignalDesktop.zip -Force
are able to read the folder, we assume that read permissions are not the issue in our case.It seems that the source code checking folder permissions is missing logging statements and simply returns
false
in case of exceptions. This might lead to false reports of missing permissions eventhough the actual problem is somewhere else.Without any logs we currently do not know why sbom-tool is failing.
sbom-tool/src/Microsoft.Sbom.Common/WindowsFileSystemUtils.cs
Lines 52 to 56 in 80d0b27
The text was updated successfully, but these errors were encountered: