currently, aoa-proxy only forwards stdin and stdout. So if you want to connect it to another service, you need to use netcat or socat in addition.
This has advantages:
only minimal functionality
less things could go wrong
very easy to interact with other easy to write programs
However, it does require for my default use case (forwarding to ssh) that
nc and bash are installed (because you would potential need the coroutine functionality of the shell)
minimal systems, e.g. in initramfs or minimal router setups often use dash or sh from busybox in which this setup could maybe done with pipes but is more complicated
alternatively socat can directly call aoa-proxy
Directly forwarding to a TCP target would significantly simplify usage.
jo-bitsch
commented
10 months ago
currently,
aoa-proxyonly forwards stdin and stdout. So if you want to connect it to another service, you need to usenetcatorsocatin addition.This has advantages:
However, it does require for my default use case (forwarding to ssh) that
ncandbashare installed (because you would potential need the coroutine functionality of the shell)dashorshfrombusyboxin which this setup could maybe done with pipes but is more complicatedsocatcan directly callaoa-proxyDirectly forwarding to a TCP target would significantly simplify usage.