It would be great if tokens would work for RemoteForward keyword so one could use them to define "dynamically" unix socket paths, for example when running borg backup sw via unix sockets. Example: ---%>--- Host *.example.com User backup Compression no Ciphers aes128-ctr MACs umac-64-etm@openssh.com IdentitiesOnly yes IdentityFile ~/.ssh/id_ed25519.%r%-example.com ExitOnForwardFailure yes StreamLocalBindUnlink yes RemoteForward /home/%r/tmp/borg.sock ~/tmp/%h-borg.sock # here! PermitLocalCommand yes LocalCommand socat UNIX-LISTEN:$HOME/tmp/%h-borg.sock "EXEC:borg serve --append-only --restrict-to-path /borgbackup/example.com/%h --umask 0007 --verbose" & ---%<--- And ssh command... ---%>--- export BACKUP_CLIENT=foo.example.com export BACKUP_DOMAIN=$(echo ${BACKUP_CLIENT} | rev | cut -d'.' -f1-2 | rev) ssh -q ${BACKUP_CLIENT} "./bin/borgwrapper create --list -s --exclude-caches ssh://localhost/borgbackup/${BACKUP_DOMAIN}/${BACKUP_CLIENT}::'{now:%Y-%m-%dT%H:%M:%S}' /" ; pkill -f "socat .*${BACKUP_CLIENT}" ---%<---
*** Bug 3104 has been marked as a duplicate of this bug. ***
see also #3140
Created attachment 3371 [details] Add percent expansion to LocalForward and RemoteForward The patch implements this on OpenBSD. Unfortunately it relies on some recent changes only in HEAD so it won't apply directly to any current releases.
This has been added and will be in the next major release. Thanks.
closing resolved bugs as of 8.6p1 release
[spam removed]