Refactor ransomware application structure and enhance documentation

- Removed `main_v2.py` and integrated its functionality into `main.py` for a cleaner codebase.
- Updated `.env.example` to include a newline at the end of the file for consistency.
- Enhanced `README.md` with detailed instructions for running the application in Docker, including support for GUI via X11 forwarding.
- Updated `requirements.txt` to include additional dependencies for improved functionality and testing.

Author: Mudityadev

.env.example

@@ -9,4 +9,6 @@
    extension=.wasted
    host=127.0.0.1
    port=8080
-   PAYMENT_ADDRESS=your_bitcoin_address_here
+   PAYMENT_ADDRESS=your_bitcoin_address_here
+
+

.github/workflows/ci.yml

@@ -0,0 +1,28 @@
+name: CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.10'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt
+      - name: Lint with flake8
+        run: |
+          pip install flake8
+          flake8 ransomware tests
+      - name: Run tests
+        run: |
+          pytest tests 

Dockerfile

@@ -0,0 +1,18 @@
+FROM python:3.10-slim
+
+# Install system dependencies for GUI
+RUN apt-get update && \
+    apt-get install -y python3-tk xauth x11-apps && \
+    rm -rf /var/lib/apt/lists/*
+
+WORKDIR /app
+
+COPY requirements.txt ./
+RUN pip install --no-cache-dir -r requirements.txt
+
+COPY . .
+
+# Set environment variables for GUI (X11)
+ENV DISPLAY=:0
+
+CMD ["python", "main.py", "-e", "-p", "./testDir/banking_samples"] 

README.md

@@ -86,4 +86,61 @@ from ransomware import discover, modify
 from ransomware.gui_main import WannaCryGUI
 ```
 
-All previous functionality is preserved, but now organized for clarity and maintainability.
+All previous functionality is preserved, but now organized for clarity and maintainability.
+
+## Running with Docker (with GUI/X11 Support)
+
+This project supports running in a Docker container, including the GUI (Tkinter) via X11 forwarding.
+
+### 1. Build the Docker Image
+
+```sh
+docker build -t ransomware-poc .
+```
+
+### 2. Run the Container with X11 Forwarding
+
+#### **On Linux**
+
+```sh
+xhost +local:root  # Allow local root to access X11
+
+docker run -it \
+    -e DISPLAY=$DISPLAY \
+    -v /tmp/.X11-unix:/tmp/.X11-unix \
+    ransomware-poc
+```
+
+#### **On macOS**
+- Install XQuartz and start it (`open -a XQuartz`).
+- In XQuartz preferences, enable "Allow connections from network clients".
+- Run:
+
+```sh
+IP=$(ifconfig en0 | grep inet | awk '$1=="inet" {print $2}')
+export DISPLAY=$IP:0
+xhost + $IP
+
+docker run -it \
+    -e DISPLAY=$DISPLAY \
+    -v /tmp/.X11-unix:/tmp/.X11-unix \
+    ransomware-poc
+```
+
+#### **On Windows (with WSL2)**
+- Install an X server (e.g., VcXsrv or Xming) and start it.
+- Set the DISPLAY variable in your WSL2 shell:
+
+```sh
+export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0.0
+export LIBGL_ALWAYS_INDIRECT=1
+
+docker run -it \
+    -e DISPLAY=$DISPLAY \
+    -v /tmp/.X11-unix:/tmp/.X11-unix \
+    ransomware-poc
+```
+
+**Note:**
+- The GUI will appear on your host system if X11 is set up correctly.
+- For headless or server environments, you can run without the GUI by modifying the entrypoint in the Dockerfile.