Dani J.

It would be for spinning up and shutting down local services that serve the namespace. I for example like to use dnscrypt-proxy, because I kinda enjoy having the added peace...

postUp.sh: ``` #!/bin/bash WORK_DIR="${HOME}/.vopono" mkdir -p ${WORK_DIR} SANDBOX_NAME=${1} SVC_NAME="dnscrypt-proxy" PROC_NAME="${SANDBOX_NAME}-${SVC_NAME}" FILE_ROOT=${WORK_DIR}/${PROC_NAME} LOG_FILE=${FILE_ROOT}.log PID_FILE=${FILE_ROOT}.pid LOCK_FILE=${FILE_ROOT}.lock CFG_FILE="${WORK_DIR}/dnscrypt-proxy.toml" SVC_COMMAND="/usr/sbin/dnscrypt-proxy -config ${CFG_FILE}" sudo daemonize -a -c ${WORK_DIR} -e ${LOG_FILE} -p ${PID_FILE} -l ${LOCK_FILE} ${SVC_COMMAND}...

Alright, I'll have a look!

Okay there is one thing... Could you set an environment variable inside the sandbox with the sandbox name, that's available to these scripts?

Something incredibly weird is happening. ``` dani@gorillo:~$ cat ~/bin/vpnbash #!/bin/bash POSTUP="${HOME}/bin/vpn_postup.sh" PREDOWN="${HOME}/bin/vpn_predn.sh" vopono -v exec --dns 127.0.0.16 --provider mullvad --server ${1} --postup ${POSTUP} --predown ${PREDOWN} "bash" dani@gorillo:~$ cat ~/bin/vpn_postup.sh #!/bin/bash...

One clear and rather big issue, even if it didn't blow up, would be that the postup and predown script execution isn't even mentioned in the (verbose) log output.

Okay so I made a wrapper script that just allows me to kick off bash sessions with a set vpn connection and dnscrypt. I'll include it here (also as an...

TBH dnscrypt wouldn't even need support from the VPN provider... I'm thinking that _not_ using the provider's DNS servers, and instead allowing arbitrary third party dnscrypt servers to be configured...

I feel like this would be pretty important... sudo is a major risk because the sudo password timeout counts across child processes. So on most Linux systems, by invoking a...

User-level cargo installs are broken anyway, as ~/.cargo/bin is dropped from path by sudo... I guess this should be its own issue, shouldn't it...? :D I think the prudent choice...