kipyegonmark

As others have noted, README should be simple and short, but a good README can save time especially if it's for something like command-line parameter parsing library.

Here's what I think it should include:

name of the projects and all sub-modules and libraries (sometimes they are named different and very confusing to new users)
descriptions of all the project, and all sub-modules and libraries
5-line code snippet on how its used (if it's a library)
copyright and licensing information (or "Read LICENSE")
instruction to grab the documentation

instructions to install, configure, and to run the programs

kipyegonmark

# Simulate fake processes of analysis sandbox/VM that some malware will try to evade
# This just spawn ping.exe with different names (wireshark.exe, vboxtray.exe, ...)
# It's just a PoC and it's ugly as f*ck but hey, if it works...

# Usage: .\fake_sandbox.ps1 -action {start,stop}

param([Parameter(Mandatory=$true)][string]$action)

$fakeProcesses = @("wireshark.exe", "vmacthlp.exe", "VBoxService.exe",
    "VBoxTray.exe", "procmon.exe", "ollydbg.exe", "vmware-tray.exe",

kipyegonmark

[Unit]
Description=Renew Let's Encrypt certificates

[Service]
Type=simple
ExecStart=renew-certificate.sh

kipyegonmark

On target machine (192.168.0.10)

$ nc -l -p 9999 > log.txt

On OSX target machine

$ nc -l 9999 > log.txt

On source machine

kipyegonmark

# Compiled source #
###################
*.com
*.class
*.dll
*.exe
*.o
*.so

# Packages #