Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:34:26Zhttps://gitlab.torproject.org/legacy/trac/-/issues/23964Rebecca have learning.2020-06-13T17:34:26ZTracRebecca have learning.
**Trac**:
**Username**: Rebecca
**Trac**:
**Username**: RebeccaVidalia: 0.3.xNima FatemiNima Fatemihttps://gitlab.torproject.org/legacy/trac/-/issues/3195Vidalia in TBB gives no hint that there's a browser window coming2020-06-13T14:10:35ZRoger DingledineVidalia in TBB gives no hint that there's a browser window comingIn TBB, Vidalia will launch a browser once Tor is done bootstrapping. But while Tor is bootstrapping, the user has no hint that there might be a browser later.
One option would be for Vidalia to try to say that somewhere in its control ...In TBB, Vidalia will launch a browser once Tor is done bootstrapping. But while Tor is bootstrapping, the user has no hint that there might be a browser later.
One option would be for Vidalia to try to say that somewhere in its control panel interface.
Another option would be to launch the browser immediately (though perhaps after #3077 is done), and have it go to some local html page that explains what's going on, and then have Torbutton or something refresh the page once Tor tells Vidalia that Tor is ready. (If we go with this option, maybe this ticket shouldn't be in the Vidalia category.)Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/5277Rename "New Identity" to "New Circuit"2020-06-13T02:46:23ZMike PerryRename "New Identity" to "New Circuit"Vidalia 0.3.x's new UI should also change the New Identity button to say "New Circuit", as Torbutton's menu is now the place to get a truly clean identity.Vidalia 0.3.x's new UI should also change the New Identity button to say "New Circuit", as Torbutton's menu is now the place to get a truly clean identity.Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/3144Network panel : Improve search in the routers list2020-06-13T00:32:44ZTracNetwork panel : Improve search in the routers listAllow to find a router by typing first letters of its nickname.
When a router is selected by this way, allow to select previous or following router by pressing Key_Up or Key_Down.
**Trac**:
**Username**: tvataireAllow to find a router by typing first letters of its nickname.
When a router is selected by this way, allow to select previous or following router by pressing Key_Up or Key_Down.
**Trac**:
**Username**: tvataireVidalia: 0.3.xhttps://gitlab.torproject.org/legacy/trac/-/issues/3898If CookieAuth and PasswordAuth are both offered, and cookie fails, fall back ...2020-06-13T00:31:08ZRoger DingledineIf CookieAuth and PasswordAuth are both offered, and cookie fails, fall back to passwordThe Tor 0.2.2.x deb, from 0.2.2.29-beta on, enables CookieAuthentication by default:
https://gitweb.torproject.org/debian/tor.git/blob/debian-0.2.2:/debian/patches/06_add_compile_time_defaults.dpatch
So Vidalia users on Debian/Ubuntu wh...The Tor 0.2.2.x deb, from 0.2.2.29-beta on, enables CookieAuthentication by default:
https://gitweb.torproject.org/debian/tor.git/blob/debian-0.2.2:/debian/patches/06_add_compile_time_defaults.dpatch
So Vidalia users on Debian/Ubuntu who had set HashedControlPassword in their torrc are bitten by a Vidalia bug: if the controlport's ProtocolInfo line says cookie and hashedpassword are both supported, Vidalia tries cookie, and if it fails it gives up.
If cookie fails but hashedpassword is also offered, Vidalia should try that one next.
Ideally we'd either support this in the Vidalia 0.2.x timeframe, or step up the schedule to ship Vidalia 0.3.x alongside the Tor 0.2.2 debs in whatever debian/ubuntu releases are coming next.
(I wonder how this order-of-operations interacts with the later controlsocket support.)Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/2529Reasonable default and warning for Vidalia exit policy settings2020-06-13T00:18:36ZMoritz BartlReasonable default and warning for Vidalia exit policy settingsI think the way current Vidalia displays exit policy settings and applies them to the config is misleading.
In particular, one user on Twitter understandably made the following problematic assumptions:
1. The default is reasonable for m...I think the way current Vidalia displays exit policy settings and applies them to the config is misleading.
In particular, one user on Twitter understandably made the following problematic assumptions:
1. The default is reasonable for most users and
2. "Misc other services" in combination with the label that says "Tor blocks some outgoing mail and file sharing applications by default to reduce spam and other abuse" means that he does not to worry about DMCA complaints and the like.
My suggestion is as follows:
1. By default, leave all boxes on the "Exit Policies" tab unticked. The label below should say:
"By default, Tor will only pass encrypted traffic between other Tor nodes. Tor always blocks some outgoing mail and file sharing applications."
2. If a user ticks any box, a small warning sign will appear below the label together with a link: "Read about the dangers of letting traffic exit the Tor network from your relay here".
The link should first explain TCP ports in short, what the default services are that use these ports, and what it means to share one's connection with other Tor users.
3. The "Misc Other Services" should be renamed "All services". I know this is not technically correct, but the sentence below already states that some ports are blocked no matter what.
I think this is a 'defect' and should not be regarded as enhancement.Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/3168Vidalia 0.3.0: "Start Tor" button without effect2020-06-13T00:15:35ZfkVidalia 0.3.0: "Start Tor" button without effectAs already reported on or-talk, I'm unable to get Vidalia 0.3.0
to connect to the ControlPort of an already running Tor process.
With Vidalia 0.2.12 it works:
fk@r500 ~ $/usr/obj/usr/ports/net-mgmt/vidalia/work/vidalia-0.2.12/src/vidal...As already reported on or-talk, I'm unable to get Vidalia 0.3.0
to connect to the ControlPort of an already running Tor process.
With Vidalia 0.2.12 it works:
fk@r500 ~ $/usr/obj/usr/ports/net-mgmt/vidalia/work/vidalia-0.2.12/src/vidalia/vidalia --loglevel debug
May 13 14:23:04.497 [notice] Resetting UI translation to English default.
May 13 14:23:04.498 [info] Removing all currently installed UI translator objects.
May 13 14:23:04.647 [notice] Vidalia 0.2.12 using Qt 4.7.2
May 13 14:23:04.724 [notice] QtWarningMsg: Application asked to unregister timer 0x9000004 which is not registered in this thread. Fix application.
May 13 14:23:04.839 [info] Using Tor's GeoIP database for country-level relay mapping.
May 13 14:23:05.008 [notice] Tor status changed from 'Unset' to 'Stopped'.
May 13 14:23:06.980 [notice] Tor status changed from 'Stopped' to 'Starting'.
May 13 14:23:07.020 [notice] Tor status changed from 'Starting' to 'Started'.
May 13 14:23:07.022 [debug] QtDebugMsg: torcontrol: Control connection status changed from 'Unset' to 'Connecting'
May 13 14:23:07.023 [debug] QtDebugMsg: torcontrol: Connecting to Tor (Attempt 1 of 5)
May 13 14:23:07.025 [debug] QtDebugMsg: torcontrol: Starting control connection event loop.
May 13 14:23:07.026 [debug] QtDebugMsg: torcontrol: Control connection status changed from 'Connecting' to 'Connected'
May 13 14:23:07.030 [notice] Tor status changed from 'Started' to 'Authenticating'.
May 13 14:23:07.035 [debug] QtDebugMsg: torcontrol: Control Command: PROTOCOLINFO 1
May 13 14:23:07.037 [debug] QtDebugMsg: torcontrol: Control Reply: 250 PROTOCOLINFO 1
250 AUTH METHODS=NULL
250 VERSION Tor="0.2.3.1-alpha"
250 OK
[...]
With 0.3.0 it doesn't work. Vidalia starts with the
progress bar already at 18%, even though it's not
supposed to connect automatically and the "Start Tor"
button doesn't seem to do anything:
fk@r500 ~ $/usr/obj/usr/ports/net-mgmt/vidalia-devel/work/vidalia-0.3.0/src/vidalia/vidalia --loglevel debug
May 13 12:54:21.401 [notice] Resetting UI translation to English default.
May 13 12:54:21.402 [info] Removing all currently installed UI translator objects.
May 13 12:54:21.517 [notice] Vidalia 0.3.0 using Qt 4.7.2
May 13 12:54:21.670 [info] Using Tor's GeoIP database for country-level relay mapping.
May 13 12:54:21.698 [notice] QtWarningMsg: QSystemTrayIcon::setVisible: No Icon set
May 13 12:54:21.704 [notice] QtWarningMsg: Application asked to unregister timer 0x3600000b which is not registered in this thread. Fix application.
^CMay 13 12:55:30.490 [notice] Cleaning up before exiting.
May 13 12:55:30.496 [notice] Vidalia is exiting cleanly (return code 0).
The behaviour seems to be the same when trying to use
a Control Socket instead of a Control Port.
I'm using FreeBSD 9.0-CURRENT amd64. Tor is running jailed
Vidalia isn't. I don't think it matters here, though.
I'm not using a "SystemTray" application which Vidalia used
to require several years ago (otherwise one wouldn't be able
to start a Window), but not lately.
Given the "QtWarningMsg: QSystemTrayIcon::setVisible" message
that's only in the 0.3.0 output I'm mentioning it anyway.
I'll try to see if installing a "SystemTray" application
makes a difference.Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/9816Toggle Between Bandwidth for Relay [Vidalia]2018-07-03T22:32:19ZTracToggle Between Bandwidth for Relay [Vidalia]It would be a really nice feature to have a quick toggle for a relay for bandwidth. If someone is running a node on their home connection and they want to throttle it a bit more during waking hours or hours where they are utilizing their...It would be a really nice feature to have a quick toggle for a relay for bandwidth. If someone is running a node on their home connection and they want to throttle it a bit more during waking hours or hours where they are utilizing their connection more I think it would be an incredible feature. A calendar option would be a great feature. Integrating this into Vidalia is critical in my opinion, because there are users who are not comfortable editing a torrc or using anything that is not GUI based, and we do not want to be missing out on possible nodes. Thoughts?
**Trac**:
**Username**: lanceVidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/8057refactored vidalia alpha to compile against Qt5 SDK2018-07-03T22:32:19ZTracrefactored vidalia alpha to compile against Qt5 SDKI refactored the alpha branch so that it now can compile against both Qt4 and Qt5 on linux. I fixed up the cmake to properly find and use Qt5 as well as fixed up the code to address API changes between Qt4 and Qt5.
My changes are in th...I refactored the alpha branch so that it now can compile against both Qt4 and Qt5 on linux. I fixed up the cmake to properly find and use Qt5 as well as fixed up the code to address API changes between Qt4 and Qt5.
My changes are in the alpha branch here:
[https://bitbucket.org/wookie/vidalia]
**Trac**:
**Username**: dwhusebyVidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/6655Vidalia 0.3.x sometimes stalls at "Authenticating to Tor" stage2018-07-03T22:32:19ZintrigeriVidalia 0.3.x sometimes stalls at "Authenticating to Tor" stageI'm running 0.3.3~alpha-1 from Debian experimental to control a system-wide instance of Tor 0.2.3.20-rc-1. I'm using ControlSocket authentication.
Sometimes, when my NetworkManager post-up hook restarts Tor and then Vidalia, Vidalia sta...I'm running 0.3.3~alpha-1 from Debian experimental to control a system-wide instance of Tor 0.2.3.20-rc-1. I'm using ControlSocket authentication.
Sometimes, when my NetworkManager post-up hook restarts Tor and then Vidalia, Vidalia status window is stalled at "Authenticated to Tor". Often, I kill the stalled Vidalia, wait a bit, start a new one that works fine.
I initially thought it was because the hook was starting Vidalia too early, at a time when the Tor control socket was not ready yet.
However, I managed to reproduce this issue once _without_ restarting Tor, merely by killing my Vidalia and starting it soon after a dozen times. I have no clue what made the failing test special compared to the other ten or so successful tests.
I have seen a few similar tickets open, but most happen on Windows and/or TBB, or lacking enough information for me to decide if my problem is the same one, so I'll let you decide if it's a duplicate.
Thank you for working on Vidalia.Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/6287Socks and Proxy Server List on Vidalia2018-07-03T22:32:19ZnaifSocks and Proxy Server List on VidaliaDPI systems capable of detecting and blocking Tor does not always inspect Socks and HTTP Proxy traffic, by decapsulating it in order to apply the Tor detection logic.
So Socks and HTTP Proxy server can be an effective way to bypass Tor...DPI systems capable of detecting and blocking Tor does not always inspect Socks and HTTP Proxy traffic, by decapsulating it in order to apply the Tor detection logic.
So Socks and HTTP Proxy server can be an effective way to bypass Tor blocking in short term, as one of the arms for the never ending arm race.
By using a Socks or an HTTP proxy server with Vidalia it's possible to bypass several censorship systems not doing analysis of traffic inside SOCKS or HTTP proxy servers.
There are tons of sites providing free lists of open socks4, socks5 and http proxy server around the internet like:
http://tools.rosinstrument.com/raw_free_db.htm?t=3
However those proxy tend to be unreliable, a single proxy can be busy during a period or become useful some minutes later due to overload and other instabilities.
So it's very useful for usability reason to be able to load a list of several socks4, socks5, http proxy servers and try to use each of them in a random loop until one is working.
That way a user can look for his preferred source of open socks/proxy servers and load it into Vidalia increasing his chance to bypass direct Tor blocks.Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/5855Support safecookie auth2018-07-03T22:32:19ZTomas ToucedaSupport safecookie authVidalia needs to support safecookie auth, and for that we need to implement HMAC-SHA-256 inside it so we don't need OpenSSL (possibly just a simple copy paste from the tor code).Vidalia needs to support safecookie auth, and for that we need to implement HMAC-SHA-256 inside it so we don't need OpenSSL (possibly just a simple copy paste from the tor code).Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/5588Vidalia should check if Tor supports an option before applying2018-07-03T22:32:19ZTracVidalia should check if Tor supports an option before applyingIn Vidalia, config options are being applied without checking if the Tor version supports it preventing the user from using Tor.
Commit 8c67821 in Vidalia alpha tries to use a DisableNetwork option supported only from Tor 0.2.3.9-alpha ...In Vidalia, config options are being applied without checking if the Tor version supports it preventing the user from using Tor.
Commit 8c67821 in Vidalia alpha tries to use a DisableNetwork option supported only from Tor 0.2.3.9-alpha preventing it from starting Tor.
Vidalia should check using GETINFO config/names to see if it is supported by the installed Tor version. Else, it should inform the user that the option would be ignored and ask permission to continue.
**Trac**:
**Username**: ferozeVidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/5520Test the new bootstrap procedure in Vidalia alpha2018-07-03T22:32:19ZTomas ToucedaTest the new bootstrap procedure in Vidalia alphaVidalia 0.3.2-rc has a new implementation for the bootstrap procedure. It'd be nice to have it intensively tested.
Basically, the idea would be to take every stage of the bootstrap procedure and stress it out mainly with "tor dies" in e...Vidalia 0.3.2-rc has a new implementation for the bootstrap procedure. It'd be nice to have it intensively tested.
Basically, the idea would be to take every stage of the bootstrap procedure and stress it out mainly with "tor dies" in each of them. It also handles other kinds of errors but the timing makes it somehow difficult to test, so trying to make sure each of those erroneous situations are in control would be good.Vidalia: 0.3.xhttps://gitlab.torproject.org/legacy/trac/-/issues/4711Vidalia Proxy settings partly loss after toggle.2018-07-03T22:32:19ZTracVidalia Proxy settings partly loss after toggle.In Settings/Network:
While "I use a proxy to access the Internet" checked and Address/Port/Type filled with values previously.
Then uncheck "I use a proxy to access the Internet" and press OK.
Address and Type fields will empty and ju...In Settings/Network:
While "I use a proxy to access the Internet" checked and Address/Port/Type filled with values previously.
Then uncheck "I use a proxy to access the Internet" and press OK.
Address and Type fields will empty and just Port setting still there on next check of Settings/Network/"I use a proxy to access the Internet"
**Trac**:
**Username**: bogoVidalia: 0.3.xhttps://gitlab.torproject.org/legacy/trac/-/issues/3761Vidalia should allow users to add HidServAuth torrc lines2018-07-03T22:32:19ZRobert RansomVidalia should allow users to add HidServAuth torrc linesCurrently, users of Vidalia Bundles must edit their torrc files manually if they want to add HidServAuth options so they can access hidden services which require client authentication. There should be a way for users to add those option...Currently, users of Vidalia Bundles must edit their torrc files manually if they want to add HidServAuth options so they can access hidden services which require client authentication. There should be a way for users to add those options within the Vidalia GUI (without having to use the torrc editor).Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/3011Some ideas for Vidalia's network graph2018-07-03T22:32:19ZTracSome ideas for Vidalia's network graphI had some ideas regarding the Network Graph, because currently it it lacks some useful information.
So, first off is totals. Totals like, **_all data**_ (down and up) in MB/GB/TB, and the **_total speed**_ in kB/s or MB/s.
Another one...I had some ideas regarding the Network Graph, because currently it it lacks some useful information.
So, first off is totals. Totals like, **_all data**_ (down and up) in MB/GB/TB, and the **_total speed**_ in kB/s or MB/s.
Another one is the automatic scale that is adjusting to the maximum speed that was reached. This produces a problem: when you reach 800 kB/s, your scale will ajust to such a range the 10 or 20 kB/s graph is almost flat.
Another cool thing: history.
* Data send last [day/hour/minute]
* Data received last [day/hour/minute]
* Total data last [day/hour/minute]
* Average up speed [day/hour/minute]
* Average down speed [day/hour/minute]
Random idea I just thought of: give graph a raster and use a drop down box that adjusts the graph scrolling speed. One block is _[1 minute]_, _[30 seconds]_, _[5 seconds]_ or _[1 second]_.
If more explanation is needed, ask it!
**Trac**:
**Username**: anaccountVidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/2938Add a simple activity indicator to the system tray2018-07-03T22:32:19ZRobert HoganAdd a simple activity indicator to the system trayIt would be nice if I didn't have to open and inspect the network view to establish for a fact that an application I'm using is routing traffic through Tor.
At the moment I have to launch a request from the application, then tab over to...It would be nice if I didn't have to open and inspect the network view to establish for a fact that an application I'm using is routing traffic through Tor.
At the moment I have to launch a request from the application, then tab over to, or open, the Vidalia network view and make sure there are active streams there.
A small indicator displaying the count of active streams in the system tray would save me this trouble. I think it would also provide useful visual feedback for any user beginning an anonymous browsing session. If they don't see the activity indicator update they know there's a problem. When they first use Tor/Vidalia/Torbutton they will get some reassurance that their setup is properly configured.
At the moment users are blind, and it is very easy to spend some time using a misconfigured torbutton or application before discovering your error.
This is a rudimentary implementation of the idea:
https://github.com/mwenge/vidalia/commit/543e40c2b86e410b2954bfd51050bfe4cd288014Vidalia: 0.3.xhttps://gitlab.torproject.org/legacy/trac/-/issues/2740Schedule different torrc options (e.g. bandwidth) at different times2018-07-03T22:32:19ZTomas ToucedaSchedule different torrc options (e.g. bandwidth) at different timesMigrated from old trac:
"I would imagine that more people would end up sharing if there were some more customizable features
For example a limit of what times would be allocated to sharing and limits for different times of different da...Migrated from old trac:
"I would imagine that more people would end up sharing if there were some more customizable features
For example a limit of what times would be allocated to sharing and limits for different times of different days
I have an on peak, I would think about sharing 1 GB on that, and 75GB on my off peak
It is very simple and practical to implement"Vidalia: 0.3.xTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/2132Vidalia's password prompt is often unhelpful; generates support requests2014-05-18T12:32:01ZNick MathewsonVidalia's password prompt is often unhelpful; generates support requestsI'd say that at least 40% of the support requests we get for Vidalia are from people who have encountered the controller password prompt, and are asking themselves "What's this about a password?" And then we refer them to https://www.to...I'd say that at least 40% of the support requests we get for Vidalia are from people who have encountered the controller password prompt, and are asking themselves "What's this about a password?" And then we refer them to https://www.torproject.org/docs/faq#VidaliaPassword
It would be good if Vidalia were better able to detect the cases that put it into this state, and tell the user what's really going on. It would also be good if Vidalia could try to recover from this state whenever it can. When Vidalia can neither explain what went wrong nor fix it, it should at the very least give the user more guidance about what might have happened and what they should do, so that they can sort it out themselves without searching for the FAQ.
Apologies if this is a duplicate; I scanned the open vidalia bugs and didn't find it mentioned.Vidalia: 0.3.xTomas ToucedaTomas Touceda