JasonJAyalaP:
- There might be legal setup that can get rid of all disclaimers,
hence
whonix-setup-wizard could be abandoned.Are you suggesting a new tool that displays disclaimers separate from
setup/anon-wizard? I agree. New ticket?
Yes. That’s the plan.
tor-connection-wizard shall be non-Whonix specific, ready to be uploaded
to packages.debian.org. (Hopefully picked up by some Debian maintainer.)
- Merge whonixsetup (cli) into anon-connection-wizard?
It makes sense that the cli and gui version have the same codebase.
Well, the cli version is written in bash. Probably hard to have the
code base shared with Qt for gui and cli at the same time? @ivy
anon-connection-wizard could detect whether or not x is running (and
if qt is installed?) and load the GUI or CLI
Perhaps a wrapper, yes. More of a bonus feature.
What if running in a terminal in kde? Assume gui? I think so. Provide
–cli option? Sure, assuming it’s easy to do/maintain.
No --cli option.
/usr/bin/tor-connection-wizard bash wrapper → if running in gui →
/usr/bin/tor-connection-wizard-gui
/usr/bin/tor-connection-wizard bash wrapper → if running in cli X →
/usr/bin/tor-connection-wizard-gui
/usr/bin/tor-connection-wizard bash wrapper → if running in cli virtual
terminal → /usr/bin/tor-connection-wizard-cli
Then if someone wants cli from X, they could manually start
tor-connection-wizard-cli.
You’d have 3 or 4 sections/modules in wizard: - boot (confirm root,
check environment) - GUI (python qt) - CLI - Core
I don’t know how of a burden that will be on @iry. He doesn’t have to
code the CLI part – nasty bash stuff, no?
Might be theoretic. Cli/bash part is only a stub anyhow. No no actual
bridges support. Just textual help. And probably will stay that way for
a very long time.
Could you ask please on tor-dev if adding such a wrapper / the cli stub
version would be okay being added to tor-connection-wizard or if that
would a good idea? @iry