I see.
BTW it's certainly about fonts. here you can select whonix_firstrun-whonix-14-firstrun-20180915 from the dropdown above the screenshot (click eye icon at the right) and slide vertical bar to see old and new version.

marmarek (Marek Marczykowski-Górecki):

Is there a reason for fixed geometry of those widgets, instead of letting Qt figure it out based on the content?

Maybe different fonts installed? Is there a reason for fixed geometry of those widgets, instead of letting Qt figure it out based on the content? I suppose there may be more problems like this in the future. Especially if proper HiDPI support will come into play...

I have no idea why this started happening without changes. Perhaps due to underlying libraries changes. Anyhow, fixed in git master.

This can be easily done. A package with the merging has been tested already.

status update:

Could anyone please help me to test if these two pull request will be enough to Integrate anon-connection-wizard into whonix-setup-wizard?

Patrick pointed out:

Great! Please create new tickets for follow-ups or future work.

https://github.com/Whonix/anon-connection-wizard/pull/7 merged

https://github.com/Whonix/anon-connection-wizard/pull/7
merged

Consider it all merged, if possible.

Hi @joysn1980 and @Patrick !

• when parsingTorrc() parses a corrupt file, it will get an out-of-bound error, causing anon-connection-wizard can not be started. We need to give up parsing.

Thank you very much for your feedback!

Two screen shots below to disable Tor.
Screen 1

Hi @iry
Did you by any chance forgot to add verifications for the port#? I still see non-numbers, -ve numbers etc are accepted

sorry @iry I have been busy lately, will get back to you very soon on this

One small request - is it possible to make the first 4 characters of the bridge case insensitive?
Example:

obfs4 109.109.202.103:44514 C52DA34113488533340ECDDBEA7DA4FABEEE7A39 cert=FzzNqEIGM39D3Zb2SdVZFA8K//xx4N82zkmfiWM8MceuChlsNZ9eOSN0jRAjiYR801sAFQ iat-mode=0

as well as

OBFS4 109.109.202.103:44514 C52DA34113488533340ECDDBEA7DA4FABEEE7A39 cert=FzzNqEIGM39D3Zb2SdVZFA8K//xx4N82zkmfiWM8MceuChlsNZ9eOSN0jRAjiYR801sAFQ iat-mode=0

should work. You can handle this in your code by making the first 4 character case insensitive.

My mistake, it was indeed .org.
btw, I now see the url as https://bridges.torproject.org/options, which seems perfect

That is correct. This is how it was showed by the UX team. I think this will be good. All in same page, so validation and other stuff will be quite easy to handle

Thanks @iry for the detail explanation.

I am thinking about integrating three pages into one, which are the main connection page, bridge setting page and proxy page. It seems that this is also the design by TPO UX team.

Thank you very much for your detailed feedback!

One more issue

1. Click on configure
2. Choose obfs4
3. Next (do not choose proxy)
4. Next - Here we get the summary showing "Bridges" Provided Pbfs4"
5. Now go "Back", "back" twice and now choose "enter custom bridges".
6. Next, Next. Now see the summary pages. "Bridges:" info is not refreshed. It is still showing the old value.

Thanks for all the updates

Several termination-related problems have been fixed or improved:

Thank you very much for your feedback.

3 screen shots here - one after another

I have enabled the "X" button and fixed some quit-program related issues.

@iry - Is there any reason why the all windows doesn't have "X" at the top right corner even though they have "cancel" button?
There are some windows with "X" at the top and some doesn't.
Is it fine to have a "X" button for all windows which can be either "Cancel"led or "OK"ayed?

Does not have "X"

Packaging is sorted out.

This is probably not the proper way to install it. But I have not figured out how to package it as .deb

make deb-icup

copy all the ./directory to /directory, for example, cp ./usr/lib/python3/dist-packages/anon_connection_wizard /usr/lib/python3/dist-packages/anon_connection_wizard

I wish you had not started viewing my previous code. Because a huge amount of changes have been made to anon-connection-wizard, especially in terms of UX:

Forget about Whonix 13.

@iry Can you please let me know how to run your scripts in whonix13? The steps which I require to run/test your modified scripts. I could pull your changes to my local branch. But how do I run them?

Review is in progress.

Could you help me review my new pull request please ?

Yes. Sounds good.

(All of that is, as long we don't learn how exactly torrc.d will be
working and when deb.torproject.org will start shipping a stable package
with torrc.d enabled by default.)

Perhaps removing kde-accessible test wise (create a snapshot so you can
revert that) would help to debug this. Because then perhaps another
thing happens which makes it easier to identify why this is happening.

iry (iry):

iry added a comment.

tor_status.py module will be in anon-connection-wizard package,
instead of whonix-setup-wizard (which will be aborted?).

In tor_status.py
https://github.com/irykoon/anon-connection-wizard/blob/1472d5c5e6e6211f3f3919fbe2305695786eb6fe/usr/lib/python3/dist-packages/anon_connection_wizard/tor_status.py,
two of the situations are /etc/tor/torrc does not exist and
DisableNetwork 0 line does not exist.

My problem is whether we should fix these two situation, instead of
just complaining bad torrc. Fixing these situations can be fairly
easy, the question we should ask is if we should fix these.

TODO: can we let Tor generate a cookie to fix this situation?

1. investigate on why KDE Accessible will be open when kdesudo anon-connection-wizard

tor_status.py module will be in anon-connection-wizard package, instead of whonix-setup-wizard (which will be aborted?).

I encountered a bug when trying to fix the issue.

In T699#14098, @Patrick wrote:

iry (iry):

I am going to let anon-connection-wizard support Tor cookie file authentication to work around the problem.

Could you please share your opinion on this, Patrick?

It's not a workaround. This is the fix. :)

iry (iry):

I am going to let anon-connection-wizard support Tor cookie file authentication to work around the problem.

Could you please share your opinion on this, Patrick?

Current anon-connection-wizard will complain "no tor control connected!!!" and strangely open an application called kde accessible.

Hi, Patrick and JasonJAyalaP !

@iry

Wrong ticket.

If that sounds good, could you suggest that in the Debian ticket please?

iry (iry):

iry added a comment.

I have a concern that:

1. if we put 40_anon-connection-wizard-autogenerated.torrc in

/etc/torrc.d/ 2. the %include /etc/torrc.d line is in
/usr/share/tor/tor-service-defaults-torrc

Then if the user used anon-connection-wizard to generate a file with
a proxy config, let's say. And after a while, the proxy setting is no
longer needed/valid, there is no obvious way to find previous
settings. As a normal user, he/she may examine /etc/tor/torrc, but
there will be no proxy settings, which may cause a confusing and
frustrating debugging process.

I have fixed some bugs you mentioned in the todo list. And I encountered the following problem now:

Switch your import tor_status to the commented out line (from anon_ import tor status). This is how whonix-setup-wizard does it at least, and that should solve two problems (not finding the module, module placement error while building).

I did this, switching from import tor_status to from anon_connection_wizard import tor_status, however, I got the following error:

ImportError: cannot import name 'tor_status'

I also tried to run the whonix-setup-wizard cloned from the current Whonix repository and got the same error. Could you please tell me what I did wrong? Thank you very much!

I have a concern that:

1. if we put 40_anon-connection-wizard-autogenerated.torrc in /etc/torrc.d/
2. the %include /etc/torrc.d line is in /usr/share/tor/tor-service-defaults-torrc

It's not clear to me yet in which order configuration files will be parsed.

Daniel answered this: http://forums.kkkkkkkkkk63ava6.onion/t/torrc-d-is-comming/4041/10

In T699#13975, @JasonJAyalaP wrote:

I'd like to settle what /etc/tor/tor* looks like.
We have torrc, torrc orig, anondist, anondist-orig... I'm confused.

@Patrick can you refresh my memory about torrc.d? Is it in issue tracker hell?

@iry
TODOs:

1. Better error message when not running as sudo. Is it possible to make a dialog box pop up asking for root password, like many desktop apps?

Debian default (non-Whonix!):

I'd like to settle what /etc/tor/tor* looks like.
We have torrc, torrc orig, anondist, anondist-orig... I'm confused.

In T699#13927, @JasonJAyalaP wrote:

I pulled his changes, compiling now, then I install and run this new connection wizard and look for what? That each button has its intended effect?

Is there anything left to do?

Thank you so much for offering me feedback! I really appreciate your help!

There are complaints while making about not using standard python folders. I don't know if that's important.

I pulled his changes, compiling now, then I install and run this new connection wizard and look for what? That each button has its intended effect? Or something more formal?

Merged.

Thank you so mcuh for your feedback and instructions!