Opened 10 years ago

Closed 9 years ago

#1284 closed defect (invalid)

Still problems with options in 0.0.4 release

Reported by: Sebastian Owned by: n8fr8
Priority: Low Milestone:
Component: Applications/Orbot Version: 1.0
Severity: Keywords:
Cc: Sebastian, gouki Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by ioerror)

This is going to be qute a few things ;)

I can check "Transparent Proxying" on a non-rooted device, without an
error message

Bridges and Update from Authority should be greyed out and inactive
while Use Bridges is off

Same for Relay Port and Nickname

Woah, I cannot define my exit policy? Bad idea.

The Reachable Addresses and Reachable Ports options are greyed out
and cannot be changed

I can check both Relaying and Use Bridges feature

I can enter any kind of garbage as the bridge address

I cannot enter the bridge fingerprint, so my bridge can be mitm'd

Generally, before allowing me to save a configuration, Orbot should
run tor with --verify-config to make sure the config is still accepted
and sane stuff has been entered.

Also, when I change config options, it seems they aren't immediately
effective, but rather require Tor to be restarted. The ui should tell the
user or offer a restart option or go ahead and restart.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (2)

comment:1 Changed 10 years ago by n8fr8

There is additional field validation for settings now within the app, but running "--verify-config" and displaying/parsing the output does make sense. Will add that.

We *should* be displaying root features on non-root devices, but apparently that isn't working.

Restart option is a good idea! Some things are changed - for instance, iptables/root options are updated, but yes, any torrc config changes require a tor restart.

comment:2 Changed 9 years ago by ioerror

Description: modified (diff)
Resolution: Noneinvalid
Status: assignedclosed

This should be multiple bugs. It's impossible to track progress on all of these issues and so this bug report has gotten no love at all.

Note: See TracTickets for help on using tickets.