## go-judger Under developing. Goal is to reimplement [uoj-judger/run_program](https://github.com/vfleaking/uoj) in GO language using [libseccomp](https://github.com/seccomp/libseccomp-golang). Install: - install go compiler: `apt install golang-go` - install libseccomp-dev: `apt install libseccomp-dev` - install: `go install github.com/criyle/go-judger/...` Features (same as uoj-judger/run_program): 1. Restricted computing resource: Time & Memory (Stack) & Output 2. Restricted syscall access (by libseccomp & ptrace) 3. Restricted file access (read & write & access & exec) New Features: 1. Percise resource limits (s -> ms, mb -> kb) 2. More architectures (arm32, arm64, x86) 3. Allow multiple traced programs in different threads 4. Allow pipes as input / output files Default file access action: - check file read / write: `open`, `openat` - check file read: `readlink`, `readlinkat` - check file write: `unlink`, `unlinkat`, `chmod`, `rename` - check file access: `stat`, `lstat`, `access`, `faccessat` - check file exec: `execve` Packages: - seccomp: provides utility function that wrappers libseccomp - mount: provides utility function that wrappers mount syscall - rlimit: provides utility function that defines rlimit syscall - forkexec: fork-exec provides mount, unshare, ptrace, seccomp, capset before exec - tracer: ptrace tracer and provides syscall trap filter context - runprogram: wrapper to call forkexec and trecer - rununshared: wrapper to call forkexec and unshared namespaces - runconfig: defines arch & language specified trace condition Executable: - run_program: under construction Configuations: - run_program/config.go: all configs toward running specs TODO: 1. Use Linux Namespace to isolate file access (elimilate ptrace) 2. Use Linux Control Groups to limit & acct CPU & memory (elimilate wait4 rusage)