Analyze Code via .NET Core Docker File about puma-scan HOT 7 CLOSED

Yikes! It definitely has not been tested over on VS for Mac yet. Might be worth playing with a bit to see if it is possible in that IDE at some point.

from puma-scan.

Watch MS connect conference yesterday. VS for mac only supports .net core.

On Thu, Nov 17, 2016 at 2:20 PM, Eric Johnson [email protected]
wrote:

Yikes! It definitely has not been tested over on VS for Mac yet. Might be
worth playing with a bit to see if it is possible in that IDE at some point.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#20 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANT2K7vRvwqRRtvn3K23QExWy7zfc5cUks5q_LbwgaJpZM4K1wja
.

from puma-scan.

Ah, that would explain it. We have libs in use that are not in .NET core. We'd need to fork a version for core, which isn't a bad idea anyway going forward.

from puma-scan.

To my knowledge, this is still not possible. Let me know if I'm wrong.

from puma-scan.

https://github.com/lambci/docker-lambda/blob/master/dotnetcore2.1/build/Dockerfile

I'd load up that Docker container and annotate this thread with what breaks when you install/run Puma headless tooling. Ideally it would be nice to add to this Docker file so Puma can run in anybody's CI pipeline without a Windows dependency.

from puma-scan.

This may be possible now. I didn't think the analyzers would work in .NET Core yet, however this seems to have been done before. I'm not sure if it's Windows specific or not:
https://github.com/dotnet/cli/issues/3175

The export results seem to be able to output to the SARIF format as well:
dotnet/roslyn#430

from puma-scan.

Closing this issue. Scans are working inside the Docker container and from standard "dotnet build" commands. See wiki for details. https://github.com/pumasecurity/puma-scan/wiki/Puma-Scan-Hunting

from puma-scan.