winapps-org/winapps

Preventing the VM being detected as a VM

Open

#99 opened on May 24, 2024

View on GitHub
 (16 comments) (0 reactions) (0 assignees)Shell (15,020 stars) (463 forks)batch import
good first issuepriority: medium

Description

I've started working on incorporating https://github.com/zhaodice/qemu-anti-detection into the windows docker image. However, I can't quite seem to get QEMU to compile inside docker. See https://github.com/oskardotglobal/docker-qemu-anti-detection and https://github.com/oskardotglobal/docker-qemu-anti-detection/actions/runs/9178044026/job/25237029138

Contributor guide

Tech stack
cdockershell
Domain
securityinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
QEMU basicsDocker build processC compilationVM detection concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the referenced qemu anti detection repository (https://github.com/zhaodice/qemu anti detection) to understand the patches applied to QEMU. Examine the failed Docker build logs in the linked workflow run (https://github.com/oskardotglobal/docker qemu anti detection/actions/runs/9178044026/job/25237029138) to identify compilation errors. Determine the required build dependencies and toolchain modifications needed to compile QEMU with anti detection patches inside a Docker container. Consider alternative approaches such as using a precompiled QEMU binary with patches or adjusting the Dockerfile's build environment settings.