| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
|
|
|
|
| |
Add some small help text blurbs for the new network settings page and the
bridge server option.
svn:r2055
|
| |
|
|
|
|
|
| |
Back out r2014 and add a comment why that little hack is in there.
svn:r2054
|
| |
|
|
|
|
|
|
| |
Fix a couple unnecessarily wide Help buttons on the server bandwidth and exit
policy tabs to be square.
svn:r2053
|
| |
|
|
|
|
|
|
| |
Fix a label in the server bandwidth settings tab so that it expands for long
translated text.
svn:r2052
|
| |
|
|
|
|
|
| |
Always use an exit policy of "reject *:*" when running a bridge server.
svn:r2051
|
| |
|
|
|
|
|
|
| |
Default to using port 443 for our ORPort on Windows. Leave the default at 9001
everywhere else.
svn:r2050
|
| |
|
|
|
|
|
|
| |
Whoops. I moved this code out into its own function, but forgot to replace it
with a call to that new function.
svn:r2049
|
| |
|
|
|
|
|
|
| |
My general modus operandi seems to be "1 commit for changing code, followed by
1 commit for fixing comment typos that arma finds."
svn:r2048
|
| |
|
|
|
|
|
|
| |
Make TorSettings inherit AbstractTorSettings and support changing the control
port and control port authentication settings while Tor is running.
svn:r2047
|
| |
|
|
|
|
|
| |
Fix a comment typo.
svn:r2046
|
| |
|
|
|
|
|
|
| |
Make the TorControl* parameter optional for AbstractTorSettings subclasses and
make its corresponding member variable private.
svn:r2045
|
| |
|
|
|
|
|
| |
Hello, commented line. I meant to remove you.
svn:r2044
|
| |
|
|
|
|
|
| |
Make VClickLabel right-to-left aware.
svn:r2043
|
| |
|
|
|
|
|
|
| |
Allow the control panel to be expanded horizontally to accommodate longer
translated widget labels.
svn:r2042
|
| |
|
|
|
|
|
|
|
|
| |
Disable the "Help censored users..." radio button if the user starts a Tor
that does not support bridges. Also, if the user tries to set up a bridge
server while Tor is not running, and then starts a Tor that does not support
bridges, warn them and suggest they upgrade or run a normal relay.
svn:r2041
|
| |
|
|
|
|
|
|
| |
Add a note to the server config page that bridges are only supported on Tor
0.2.0.3-alpha or newer.
svn:r2040
|
| |
|
|
|
|
|
|
| |
Don't try to "setconf PublishServerDescriptor bridge" if we're running a Tor
older than 0.2.0.3-alpha.
svn:r2039
|
| |
|
|
|
|
|
| |
Disable Privoxy's enable-edit-actions feature, too.
svn:r2038
|
| |
|
|
|
|
|
|
| |
Update our OS X bundle's Privoxy config and include the changes from my last
commit.
svn:r2037
|
| |
|
|
|
|
|
|
| |
Disable enable-remote-toggle and enable-remote-http-toggle in our bundle's
Privoxy config.
svn:r2036
|
| |
|
|
|
|
|
|
| |
'PublishServerDescriptor bridge' is the mojo to be a bridge server,
apparently.
svn:r2035
|
| |
|
|
|
|
|
| |
I need a 'make spellcheck-my-comments-before-arma-notices' build target.
svn:r2034
|
| |
|
|
|
|
|
|
|
| |
Add some UI to the Server config page for setting oneself as a bridge. Also
rearrange a skosh of code. I still need to make this use different default
values for bridge nodes versus regular servers.
svn:r2033
|
| |
|
|
|
|
|
|
|
| |
Add support for configuring whether or not to be a bridge. Also remove the
notion that being a server requires both an ORPort and a Nickname; you can be
a fine server with just an ORPort.
svn:r2032
|
| |
|
|
| |
svn:r2031
|
| |
|
|
|
|
|
|
| |
lupdate the translations. The strings in the network settings dialog are
probably pretty stable now.
svn:r2030
|
| |
|
|
|
|
|
|
|
| |
We still want the "My ISP is lame" checkbox to be checked if the user has
TunnelDirConns enabled but not UseBridges, since their Tor might know
TunnelDirConns but not UseBridges.
svn:r2029
|
| |
|
|
|
|
|
|
|
| |
Stupid hack to fix manpage installation on 'make install'. Once all you
autotools experts have stopped laughing at me and calling me names, you
can tell me what the right fix is.
svn:r2028
|
| |
|
|
|
|
|
|
|
| |
If the user is running a Tor that does not support bridges, disable the bridge
UI and show a label indicating that even though their Tor doesn't support
bridges, the little checkbox is still doing something.
svn:r2027
|
| |
|
|
|
|
|
|
| |
If we can't getconf a value, return the 'local' value instead of assuming
the default.
svn:r2026
|
| |
|
|
|
|
|
|
| |
Default to 80 and 443 as reachable ports, so the user has some cue as to what
goes in that little text box.
svn:r2024
|
| |
|
|
|
|
|
|
|
|
| |
Complain if the user checks the "I use a proxy to access the Internet"
checkbox but doesn't enter any proxy information, or if they check the "My
firewall only lets me connect to certain ports" checkbox but doesn't enter the
ports to which their firewall allows them to connect.
svn:r2023
|
| |
|
|
|
|
|
|
| |
Make the config dialog a little wider by default so all the buttons fit, even
when using Deutsche Vidalia.
svn:r2022
|
| |
|
|
|
|
|
| |
Fix a comment typo.
svn:r2021
|
| |
|
|
|
|
|
|
|
| |
Limit the 'Add Bridge' line edit box to 100 characters. Really, the longest
bridge entry should only be at most 79 characters, but we'll give users some
room to be 'creative' with their spacing.
svn:r2020
|
| |
|
|
|
|
|
|
| |
Call the addBridge() slot when the user presses return in the 'Add Bridge'
text box.
svn:r2019
|
| |
|
|
|
|
|
| |
Validate that a bridge the user enters is acceptably formatted.
svn:r2018
|
| |
|
|
|
|
|
|
| |
Phobos says we don't need to define these ourselves anymore, otherwise we get
compilation errors.
svn:r2017
|
| |
|
|
|
|
|
| |
Add a method for determining if a given string is a valid hexadecimal string.
svn:r2016
|
| |
|
|
|
|
|
|
| |
Only set bridge-related options on Tor >= 0.2.0.3-alpha and only if the user
has configured one or more bridges to use.
svn:r2015
|
| |
|
|
|
|
|
|
|
|
| |
Remove a hack to work around old Tors that would close a control connection
without sending a response after receiving a signal asking Tor to shut down.
This was fixed in Tor 0.1.2.1-alpha. The hack meant that we wouldn't get a
good error message if the signal failed.
svn:r2014
|
| |
|
|
|
|
|
|
|
|
|
| |
Fix a needed change I missed in r1993: since our TorProcess object is never
null now, we can't rely of its nullness to decide whether to send Tor a
halt signal or to use the QProcess API to kill the process. Now we always try
to send a signal first, if the socket is connected. If the control socket is
not connected or the halt signal fails, then call TorProcess::stop().
svn:r2013
|
| |
|
|
|
|
|
|
| |
I changed my mind on r2010: if the router is already on the map, just update
the coordinates, instead of completely removing and readding the router.
svn:r2011
|
| |
|
|
|
|
|
|
|
| |
If TorMapWidget::addRouter() is called for a router that is already on the
map, remove and free the existing instance before adding the router back with
the new location.
svn:r2010
|
| |
|
|
|
|
|
|
| |
Stop leaking 8 bytes for pretty much every circuit we plotted on the network
map. Found by arma and his trusty valgrind.
svn:r2009
|
| |
|
|
|
|
|
|
| |
Give the QTranslator we create on startup a parent, so we don't leak it on
exit.
svn:r2008
|
| |
|
|
|
|
|
|
|
|
| |
Make the main window the parent of all the other dialogs, like the config
dialog and the message log, so Qt can take care of cleaning everything up on
exit. We were also previously leaking the memory allocated to the
ConfigDialog on exit.
svn:r2007
|
| |
|
|
|
|
|
|
|
|
|
| |
Give arma not one, not two, but three (yes folks, three) ways of copying
bridge information to the clipboard. Users can select one or more bridges and
then either (1) Press Ctrl+C, (2) Right-click and select "Copy" from a context
menu, or (3) Click the shiny new Copy button next to the bridge list, to copy
their bridges to the clipboard.
svn:r2006
|
| |
|
|
|
|
|
| |
Use Vidalia::createShortcut() for creating per-window shortcuts.
svn:r2005
|
| |
|
|
|
|
|
|
|
| |
Add a method Vidalia::createShortcut() for creating a shortcut in the context
of some widget and binding that shortcut's activated() signal to a slot of
another widget.
svn:r2004
|