Package: tor
Version: 0.3.4.8-1
Severity: normal
Dear Maintainer,
It is often handy to create shell aliases to do tasks that would otherwise
require a lot
of retyping the same thing over and over. For example 'git push' might very
well be
aliased to 'push' at the shell level by
alias push='git push'
then you could conceivably use
> torify push
as a shorthand for
> torify git push
this however fails: torify does not expand the aliases and doesn't know what
'push' is.
As mentioned in the ubuntu downstream bug (
https://bugs.launchpad.net/ubuntu/+source/tor/+bug/1687037 )
it doesn't matter what shell you use, torify just doesn't check.
what happens: torify takes the arguments passed in without checking if there
are aliases involved
what should happen: is torify should be alias-aware.
tor:Installed: 0.3.4.8-1
debian: buster
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tor depends on:
ii adduser 3.117
ii libc6 2.27-6
ii libcap2 1:2.25-1.2
ii libevent-2.1-6 2.1.8-stable-4
ii liblzma55.2.2-1.3
ii libseccomp2 2.3.3-3
ii libssl1.1 1.1.0h-4
ii libsystemd0 239-9
ii libzstd11.3.5+dfsg-1
ii lsb-base9.20170808
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages tor recommends:
ii logrotate3.14.0-4
ii tor-geoipdb 0.3.4.8-1
ii torsocks 2.2.0-2
Versions of packages tor suggests:
pn apparmor-utils
pn mixmaster
pn obfs4proxy
pn socat
pn tor-arm
pn torbrowser-launcher
-- no debconf information