win-sshproxy binay was blocked by CloudStrike during version 5.2.0~5.2.5
Steps to reproduce the issue
Steps to reproduce the issue
install CloudStrike
setup podman default machine for windows
podman machine start
Describe the results you received
Starting machine "podman-machine-default"
This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:
podman machine set --rootful
API forwarding for Docker API clients is not available due to the following startup failures.
fork/exec \podman\5.2.5\usr\bin\win-sshproxy.exe: Access is denied.
Podman clients are still able to connect.
Describe the results you expected
Starting machine "podman-machine-default"
This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:
podman machine set --rootful
API forwarding listening on: npipe:////./pipe/docker_engine
Docker API clients default to this address. You do not need to set DOCKER_HOST.
Machine "podman-machine-default" started successfully
It is not clear what you are expecting from us to do about that? Ask the security vendor why this is flagged, it doesn't seem to be flagged by others and I am not aware of any problems with it from users
Issue Description
win-sshproxy binay was blocked by CloudStrike during version 5.2.0~5.2.5
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Starting machine "podman-machine-default"
This machine is currently configured in rootless mode. If your containers require root permissions (e.g. ports < 1024), or if you run into compatibility issues with non-podman clients, you can switch using the following command:
API forwarding for Docker API clients is not available due to the following startup failures. fork/exec\podman\5.2.5\usr\bin\win-sshproxy.exe: Access is denied.
Podman clients are still able to connect.
Describe the results you expected
Starting machine "podman-machine-default"
This machine is currently configured in rootless mode. If your containers require root permissions (e.g. ports < 1024), or if you run into compatibility issues with non-podman clients, you can switch using the following command:
API forwarding listening on: npipe:////./pipe/docker_engine
Docker API clients default to this address. You do not need to set DOCKER_HOST. Machine "podman-machine-default" started successfully
podman info output
host: arch: amd64 buildahVersion: 1.37.3 cgroupControllers: [] cgroupManager: cgroupfs cgroupVersion: v1 conmon: package: conmon-2.1.12-2.fc40.x86_64 path: /usr/bin/conmon version: 'conmon version 2.1.12, commit: ' cpuUtilization: idlePercent: 95.87 systemPercent: 1.25 userPercent: 2.89 cpus: 8 databaseBackend: sqlite distribution: distribution: fedora variant: container version: "40" eventLogger: journald freeLocks: 2046 hostname: ZHADSCOE03-W10 idMappings: gidmap:
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response