pax_global_header 0000666 0000000 0000000 00000000064 12056211037 0014507 g ustar 00root root 0000000 0000000 52 comment=2b34839bd5be6218b05c8cba4dbd0476df482ec7
vidalia-0.2.21/ 0000775 0000000 0000000 00000000000 12056211037 0013202 5 ustar 00root root 0000000 0000000 vidalia-0.2.21/.gitignore 0000664 0000000 0000000 00000003762 12056211037 0015202 0 ustar 00root root 0000000 0000000
# /
/CMakeCache.txt
/CMakeFiles
/*.cmake
/config.h
/Makefile
# /doc/
/doc/CMakeFiles
/doc/Doxyfile
/doc/Makefile
/doc/vidalia.1
/doc/*.cmake
# /pkg/
/pkg/CMakeFiles
/pkg/*.cmake
/pkg/Makefile
# /pkg/osx/
/pkg/osx/buildmpkg.sh
/pkg/osx/builddmg.sh
/pkg/osx/VidaliaDesc.plist
/pkg/osx/VidaliaInfo.plist
/pkg/osx/VidaliaBundleDesc.plist
/pkg/osx/VidaliaBundleInfo.plist
# /pkg/rpm/
/pkg/rpm/vidalia.spec
# /pkg/win32/
/pkg/win32/vidalia.nsi
/pkg/win32/vidalia-bundle.nsi
# /src/
/src/CMakeFiles
/src/Makefile
/src/*.cmake
# /src/common/
/src/common/CMakeFiles
/src/common/Makefile
/src/common/libcommon.a
/src/common/*.cmake
/src/common/moc_*.cxx
# /src/torcontrol/
/src/torcontrol/CMakeFiles
/src/torcontrol/Makefile
/src/torcontrol/*.cmake
/src/torcontrol/moc_*.cxx
/src/torcontrol/libtorcontrol.a
# /src/vidalia/
/src/vidalia/CMakeFiles
/src/vidalia/Makefile
/src/vidalia/vidalia.h
/src/vidalia/vidalia
/src/vidalia/Vidalia.app
/src/vidalia/vidalia.exe
/src/vidalia/*.cmake
/src/vidalia/*.obj
/src/vidalia/moc_*.cxx
/src/vidalia/ui_*.h
/src/vidalia/qrc_*.cxx
# /src/vidalia/i18n/
/src/vidalia/i18n/CMakeFiles
/src/vidalia/i18n/Makefile
/src/vidalia/i18n/*.cmake
/src/vidalia/i18n/*.qm
# /src/vidalia/res/
/src/vidalia/res/vidalia_win.rc
# /src/vidalia/res/128x128/
/src/vidalia/res/128x128/vidalia_win.rc
/src/vidalia/res/128x128/Thumbs.db
# /src/vidalia/res/16x16/
/src/vidalia/res/16x16/vidalia_win.rc
/src/vidalia/res/16x16/Thumbs.db
# /src/vidalia/res/22x22/
/src/vidalia/res/22x22/vidalia_win.rc
/src/vidalia/res/22x22/Thumbs.db
# /src/vidalia/res/32x32/
/src/vidalia/res/32x32/vidalia_win.rc
/src/vidalia/res/32x32/Thumbs.db
# /src/vidalia/res/48x48/
/src/vidalia/res/48x48/vidalia_win.rc
/src/vidalia/res/48x48/Thumbs.db
# /src/vidalia/res/flags/
/src/vidalia/res/flags/vidalia_win.rc
/src/vidalia/res/flags/Thumbs.db
# /src/vidalia/res/icons/
/src/vidalia/res/icons/vidalia_win.rc
/src/vidalia/res/icons/Thumbs.db
# /src/vidalia/res/map/
/src/vidalia/res/map/vidalia_win.rc
/src/vidalia/res/map/Thumbs.db
vidalia-0.2.21/CHANGELOG 0000664 0000000 0000000 00000207767 12056211037 0014437 0 ustar 00root root 0000000 0000000 0.2.21 30-Nov-2012
o Don't wait so long before attempting to reload the router list if the ns/all
command returned empty. Fixes bug 6483.
o Stop trying to load router information if torControl is not connected
anymore. Fixes bug 6482.
o Save ControlPortWriteToFile with a relative path instead of an absolute
one. Fixes bug 6568.
o Fix RouterDescriptor's bandwidth and uptime values when defined from the
consensus. Fixes bug 6601.
0.2.20 10-Jul-2012
o Append router status information if Tor is using microdescriptors.
o Display paths with their native separators. Resolves ticket 4337.
o Do not ignore the Show on Startup checkbox. Fixes bug 5351.
o Do not add relative root to DataDirectory if it is empty. Fixes
bug 6178.
0.2.19 30-May-2012
o Disable "Run Vidalia when my system starts" if the
BrowserExecutable config option is set. This will avoid issues with
TBB users starting Vidalia the wrong way.
o Automigrate TorExecutable, Torrc and DataDirectory config options
to the new relative path handling.
o Really get rid of the openssl dependency. The goal had been to
achieve that for 0.2.18, but not everything was actually removed.
o For static builds on windows, correctly link with zlib and
ws32_2.lib.
0.2.18 14-May-2012
o Use consensus bandwidth for routers when microdescriptors is
enabled. Fixes bug 3287.
o Notify users that a warning status event has appeared by flashing
the Message Log button. Fixes bug 3957.
o Fix a method that didn't return the specified type if another
control method was selected. Fixes bug 4065.
o Resume listing relays in the Network Map panel even when Tor only
offers microdescriptors (new in Tor 0.2.3.x). Fixes ticket 4203.
o Handle unrecognized Tor bootstrap phases. (Tor tells us a summary
description of each bootstrap phase as it occurs, so we can use
that string if needed.) Fixes bug 5109.
o Displays Korean, Catalan and Greek in their native scripts. Fix
bug 5110.
o Support adding comments in the same line as a config option inside
the torrc dialog. Fixes bug 5475.
o Remove Polipo and Torbutton from Vidalia's build scripts. Resolves
ticket 5769.
o Fix deadlock when the browser process failed to launch in OS X.
o Add ProfileDirectory, DefaultProfileDirectory, PluginsDirectory,
DefaultPluginsDirectory for better Browser configuration. Also set
the Vidalia binary location as the starting point for relative
paths.
o Enable Burmese, Croatian, Basque and Serbian translation.
o Remove the "Find bridges" button in order to avoid compromising
users that need to hide behind tor at all times. Fixes bug 5371.
o Add visual feedback from VClickLabel when in "pressed" state.
Resolves ticket 5766.
0.2.17 11-Feb-2012
o Improve the translation policy: do not remove translations that
are not under 75% done. This re enables Polish and Catalan.
0.2.16 11-Feb-2012
o Make the default data directory in windows be located in the Local
AppData instead of the Roaming one. Fixes bug 2319.
o Do not launch Firefox with every CIRCUIT_ESTABLISHED signal, do it
only if Firefox isn't open yet. Fixes bug 2943.
o Uses TAKEOWNERSHIP and __OwningControllerProcess to avoid leaving
tor running in background if Vidalia exits unexpectedly. Fixes bug
3463.
o Attempt to remove port.conf file before using it to avoid a race
condition between tor and Vidalia. Fixes bug 4048.
o Do not allow users to check the "My ISP blocks..." checkbox
without entering any bridges. Also updates the
documentation. Fixes bug 4290.
o Check that the authentication-cookie file length is exactly 32
bytes long. Fixes bug 4304.
o Explicitly disable ControlPort auto. Fixes bug 4379.
o Make the non exit relay option backward compatible with Vidalia <
0.2.14 so that it doesn't confuse users. Fixes bug 4642.
o Sets the preferred size for the GUI layout so it doesn't squeeze
widges when the size isn't big enough. Fixes bug 4656.
o Removes the option to have only HTTPProxy since it does not work
any more as it used to do with older tor versions. Users should
use HTTP/HTTPSProxy instead. Fixes bug 4724.
o Add a hidden configuration option called SkipVersionCheck so
systems like Tails can force Vidalia to skip checking tor's
version. Resolves ticket 4736.
o When Tor has cached enough information it bootstraps faster than
what takes Vidalia connect to it, so Vidalia does not see the
event to update the progress bar. Now Vidalia explicitly asks for
bootstrap-phase when it connects to Tor, and updates the progress
to what is actually happening instead of hanging in
"Authenticating to Tor". Fixes bug 4827.
o Fix size hints in the main window layout so that tilling window
managers display the window properly. Thanks to Mike Warren for
the fix. Fixes bug 4907.
o Vidalia only validates IPv4 bridge lines. IPv6 bridges are now
available, and there will be pluggable transport bridge lines. So
the validation is now delegated to Tor through SETCONF.
o Explicitly disable SocksPort auto by setting it to its default
(9050). Fixes bug 4598.
o Sets __ReloadTorrcOnSIGHUP to 0 if SAVECONF failed, which means
the user can't write the torrc file. Fixes bug 4833.
o Enable new translations that are >90% done. The new languages are:
Bulgarian, Czech, Hebrew, Greek, Indonesian, Korean,
Dutch. Resolves ticket 5051.
o Remove translations that aren't ready enough: Japanese, Thai,
Albanian, Vietnamese, Chinese (Taiwan), Polish, Catalan and
Burmese.
0.2.15 07-Oct-2011
o Draw the bandwidth graph curves based on the local maximum, not
the global maximum. Fixes bug 2188.
o Add an option for setting up a non-exit relay to the Sharing
configuration panel. This is meant to clarify what an exit policy
and an exit relay are. Resolves bug 2644.
o Display time statistics for bridges in UTC time, rather than local
time. Fixes bug 3342.
o Change the parameter for ordering the entries in the Basic Log
list from currentTime to currentDateTime to avoid missplacing
entries from different days.
o Check the tor version and that settings are sanitized before
trying to use the port autoconfiguration feature. Fixes bug 3843.
o Provide a way to hide Dock or System Tray icons in OSX. Resolves
ticket 2163.
o Make new processes appear at front when they are started (OSX
specific).
0.2.14 26-Aug-2011
o Make the AutoPort setting default to false, so that it doesn't
break backwards compatibility for people that aren't using Vidalia
inside Tor Browser Bundle.
0.2.13 10-Aug-2011
o Add a way to bootstrap Tor's torrc file (copy the torrc to a given
directory before Vidalia starts) so that packages such as
Bridge-by-default portable bundles for OSX don't violate the directory
structure of the operating system. Fixes bug 2821.
o Add the proper CA Certificates so that the "Find Bridges" button works
again. Fixes bug 2835.
o Update the useful links help page. Fixes bug 2809.
o Reintegrate Breakpad, and make it available in platforms other than
Windows. Resolves bug 2105.
o Fix bandwidth assigned to relays on the Network Map. A lot of relays are
displaying an erroneous bandwidth and since they are ordered by that
value in the Network Map, it leads to confusion. Vidalia now specifies
the bandwidth as the minimum of the three possible values (burst,
average and observed). Fixes bug 2744.
o Fix layouts in the configuration panel to make them look seamlessly
across all platforms.
o Add -no-remote parameter to Firefox so it allows another instance of
non-TBB Firefox. Fixes bug 2254.
o Add the possibility of changing the torrc path while Tor hasn't
started. Fixes bug 3109.
o Make the fact that bridges don't need a DirPort setting more clear by
removing the content of the field when disabling it. Fixes bug 3119.
o Improve command line parameter handling. Resolves bug 2965.
o Fix layout in BandwidthGraph to display labels correctly in every
language. Fixes bug 2500.
o Updates README.debs to reflect the change in the packaging now that
Vidalia uses Git. Fixes bug 3668.
o Add a way to use the autoconfiguration for ControlPort and SocksPort.
Tor can now autoconfigure Control and Socks Ports when the default ones
are in use. This makes it easier to run several different instances of
TBB at the same time. Resolves bug 3077.
o Provide the necessary fields (Control password, ControlPort) to let
TorButton NEWNYM. Vidalia provides these in env vars when it launches
the Firefox instance. Resolves bug 2659.
0.2.12 10-Apr-2011
o Vidalia's SVN repository has been migrated to Git. All branches but
master have been archived for later review, since SVN trunk had changed
significantly; they should be reviewed later to determine whether
they can and should still be merged. All \version $Id$ headers have been
removed since Git does not support $Id$.
o As part of the move, Vidalia's Trac is now at:
https://trac.torproject.org/
All Trac numbers in Vidalia 0.2.12 and beyond refer to the new Trac
entries. The old Trac is archived for posterity at:
https://trac-vidalia.torproject.org/projects/vidalia
o Add support for Tor's ControlSocket as an alternative to ControlPort. It
can be used for Linux maintainers to build a better default interaction
between Tor and Vidalia by just setting the right permissions and file
owner on the socket file for the connection. Using ControlSocket means
you don't need to worry about authentication methods with ControlPort.
Resolves bug 2091.
o Add a way to edit arbitrary torrc entries while Tor is running. Now
Vidalia users have more flexibility for configuring Tor. This change
doesn't replace editing torrc directly, because on some systems
(like Debian) Tor can't write to its torrc file. Resolves bug 2083.
o Remove Vidalia's direct dependency on OpenSSL. This dependency had
caused Vidalia to fail to run on FreeBSD (due to a bug in the FreeBSD
ports collection) and Fedora 14 (due to an incompatibility between
OpenSSL and Fedora's SELinux configuration). Resolves bug 2287 and
2611.
o Restore compatibility with Windows 2000. An update to the MiniUPnPc
library had introduced an unnecessary dependency on a system library
not included in Windows 2000. Fixes bug 2612.
o Fix how the advanced message log window displays message updates when
messages are coming in too quickly, for example when you're listening
to debug-level messages from Tor. Fixes bug 2093.
o Add a what's this? link to the bridge option to explain in a more verbose
fashion what being a bridge involves. Resolves bug 1995.
o Prompt users to restart Tor after changing the path to torrc. Fixes bug
2086.
o Disable the directory port configuration field when configuring a
bridge. A bridge does not need to operate a separate directory port,
and operating one can make a bridge easier to detect. Fixes bug 2431.
o When Vidalia asks Tor for a bridge's usage history before anyone has
used it, correctly report that no clients have used the bridge recently.
Previously, it would incorrectly warn that it was unable to retrieve the
bridge's usage history. Fixes bug 2186.
0.2.10 26-Aug-2010
o Drop remote GeoIP lookups. Instead, the default behavior now is to use
the country-level GeoIP database that ships with Tor to map an IP
address to a country code, and then map the country code to latitude
and longitude with a separate database built into Vidalia.
o Add a -DUSE_GEOIP build option to enable building with MaxMind's GeoIP
C library for using a local city-level or country-level database
instead of Tor's database. See README.geoip for details on use.
o Only update a stream's displayed target address in the network map if
no hostname was given in the stream's NEW status event. Fix suggested
by Robert Hogan. (Ticket #608)
o Update the menubar icon at the same time as the dock icon on OS X.
Previously, we had a blank icon in the menubar. (Ticket #610)
o Updated several translations.
0.2.9 20-May-2010
o Remove the GoDaddy CA certificate bundle since we changed the
certificate used to authenticate connections to
geoips.vidalia-project.net for downloading GeoIP information from a
commercial GoDaddy certificate to a free CACert certificate.
o Define -D_WIN32_WINNT=0x0501 on Windows builds so that MiniUPnPc will
build with the latest versions of MinGW.
o Modify miniupnpc.c from MiniUPnPc's source so that it will build on
Mac OS X 10.4.
o Work around Qt's new behavior for the QT_WA macro so that Vidalia will
work correctly again on Windows with Qt >= 4.6.
o Force CMake to include the *_RELEASE versions of Qt libraries when
building a .dmg on Mac OS X, so that it will work with CMake >= 2.8 as
well.
o Explicitly link zlib into src/common to avoid link errors on some
older versions of Mac OS X.
o Add Danish, Brazilian Portguese and Vietnamese translations.
0.2.8 11-Apr-2010
o Stop using our custom dock icon implementation on OS X and just use
QSystemTrayIcon everywhere. Fixes the build on Snow Leopard.
(Ticket #562)
o Update the bundled CA certificates to re-enable downloading bridges
from bridges.torproject.org via SSL.
o Include a pre-configured qt.conf file in the Mac OS X bundles that
disable Qt plugin loading from the default directories. Otherwise,
users who have Qt installed in a system-wide location would end up
loading the libraries twice and crashing.
o Include libgcc_s_dw2-1.dll in the Windows installers, since Qt 4.6 now
depends on that DLL. Including the .dll is currently hardcoded, so the
Windows installer must be built using Qt 4.6. (Ticket #555)
o Update the included version of miniupnpc to 1.4.20100407.
o Add Burmese and Thai UI translations.
0.2.7 25-Jan-2010
o Remove the explicit palette set for the configuration dialog that
prevented the dialog from inheriting colors from the user's current
system theme. (Ticket #485. Patch from mkirk.)
o Correct the path to the badge pixmap used in time skew warning
messages. (Ticket #537. Patch from mkirk.)
o Fix compilation on Debian GNU/kFreeBSD. Patch from dererk.
o Clean up a couple status event messages related to dangerous port
warnings.
o Change the vidalia_ru.nsh output encoding from KOI8-R to Windows-1251.
(Ticket #527)
o Add an option for building an OS X 10.4 compatible binary.
0.2.6 02-Nov-2009
o Remove the erroneous comma in the default vidalia.conf in the
Mac OS X drag-and-drop bundle, since we now dump whatever the
user types into a QString rather than parsing it into a
QStringList.
o Updated the Arabic, Russian and Slovenian translations.
0.2.5 14-Oct-2009
o Add support in the Network settings page for configuring the
Socks4Proxy and Socks5Proxy* options that were added in
Tor 0.2.2.1-alpha. Patch from Christopher Davis.
o Add a "Automatically distribute my bridge address" checkbox (enabled
by default) to the bridge relay settings options. (Ticket #524)
o Add ports 7000 and 7001 to the list of ports excluded by the IRC
category in the exit policy configuration tab. (Ticket #517)
o Add a context menu for highlighted event items in the "Basic" message
log view that allows the user to copy the selected item text to the
clipboard.
o Maybe fix a time conversion bug that could result in Vidalia
displaying the wrong uptime for a relay in the network map.
o Stop trying to enforce proper quoting and escaping of arguments to be
given to the proxy executable (e.g., Polipo). Now the user is on their
own for properly formatting the command line used to start the proxy
executable. (Ticket #523)
0.2.4 07-Sep-2009
o Split the message log into "Basic" and "Advanced" views. The
"Advanced" view contains standard log messages from Tor, while the new
experimental "Basic" view displays status events received from Tor.
(Ticket #265)
o Apply an application-global stylesheet on OS X that forces all tree
widgets in Vidalia to use the 12pt font recommended by Apple's human
interface guidelines.
o Add an OSX_FORCE_32BIT CMake option that can be used to force a 32-bit
build on Mac OS X versions that default to 64-bit builds (e.g., Snow
Leopard), if only 32-bit versions of the Qt libraries are available.
o Fix a bug introduced in 0.2.3 that prevented Vidalia from correctly
responding to ADDRMAP events from Tor. The result was that users would
sometimes see IP addresses in the connection list shown under the network
map rather than hostnames.
o Fix a bug in the default "bootstrap" vidalia.conf file included in the
OS X drag-and-drop bundles that pointed to a non-existent Polipo
configuration file, causing Polipo to fail on startup.
0.2.3 27-Aug-2009
o Create the data directory before trying to copy over the default
Vidalia configuration file from inside the application bundle on Mac
OS X. Affects only OS X drag-and-drop installer users without a
previous Vidalia installation.
o Change all Tor event handling to use Qt's signals and slots mechanism
instead of custom QEvent subclasses.
o Fix another bug that resulted in the "Who has used my bridge?" link
initially being visible when the user clicks "Setup Relaying" from
the control panel if they are running a non-bridge relay.
(Ticket #509, reported by "vrapp")
o Always hide the "Who has used my bridge?" link when Tor isn't running,
since clicking it won't return useful information until Tor actually
is running.
0.2.2 14-Aug-2009
o When the user clicks "Browse" in the Advanced settings page to locate
a new torrc, set the initial directory shown in the file dialog to the
current location of the user's torrc. (Ticket #505)
o Use 'ditto' to strip the architectures we don't want from the Qt
frameworks installed into the app bundle with the dist-osx,
dist-osx-bundle and dist-osx-split-bundle build targets.
o Fix a bug in the CMakeLists.txt files for ts2po and po2ts that caused
build errors on Panther for those two tools.
o Include rebuilt OpenSSL libraries in the Windows packages that are
built with the static (/MT) version of the Microsoft Visual C++
Runtime. Otherwise, we would require users to install the MSVC
Redistributable, which doesn't work for portable installations such as
the Tor Browser Bundle.
o Remove the NSIS file for the Vidalia installer since we now ship
MSI-based installers on Windows.
0.2.1 03-Aug-2009
o Add a "Find Bridges Now" button that will attempt to automatically
download a set of bridge addresses and add them to the list of bridges
in the Network settings page.
o Add support for building with Google's Breakpad crash reporting
library (currently disabled by default).
o Show or hide the "Who has used my bridge recently?" link along with
the other bridge-related widgets when the user toggles the relay mode
in the Network settings page. (Ticket #480)
o Tolerate bridge addresses that do not specify a port number, since Tor
now defaults to using port 443 in such cases.
o Add support for viewing the map as a full screen widget when built
with KDE Marble support.
o Compute the salted hash of the control password ourself when starting
Tor, rather than launching Tor once to hash the password, parsing the
output, and then again to actually start Tor.
o Add a signal handler that allows Vidalia to clean up and exit normally
when it catches a SIGINT or SIGTERM signal. (Ticket #481)
o If the user chooses to ignore further warnings for a particular port,
remove it from the WarnPlaintextPorts and RejectPlaintextPorts
settings immediately. Also remember their preferences and reapply them
later, even if Tor is unable to writes to its torrc.(Ticket #493)
o Don't display additional plaintext port warning message boxes until
the first visible message box is dismissed. (Ticket #493)
o Renamed the 'make win32-installer' CMake target to 'make dist-win32'
for consistency with our 'make dist-osx' target.
o Fix a couple bugs in the WiX-based Windows installer related to building
a Marble-enabled Vidalia installer.
o Write the list of source files containing translatable strings to a
.pro file and supply just the .pro file as an argument to lupdate, rather
than supplying all of the source file names themselves.
0.1.15 09-Jul-2009
o Bump the minimum required Qt version to 4.3.0.
o Remove USE_QSSLSOCKET as a build option. If your Qt doesn't support
OpenSSL, then you don't get GeoIP lookups.
o Fix the TorPostFlight portion of the OS X bundle installer so it
doesn't fail when installing Torbutton.
o Include libeay32.dll in the Windows installers.
0.1.14 29-Jun-2009
o Close the TorProcess more quickly after registering for log events, so
we avoid displaying duplicate log messages received over Tor's control
port and Tor's stdout log. (Ticket #484)
o Explicitly set CMAKE_OSX_SYSROOT to the 10.4 SDK rather than expecting
the packager to do so when building a Universal binary.
o Include Tor's geoip file in the Windows bundles.
0.1.13 25-May-2009
o Remove an old warning on the relay settings page that running a bridge
relay requires Tor 0.2.0.8-alpha or newer.
o Add a workaround for a bug that prevented Vidalia's tray icon from
getting added to the system notification area on Gnome when Vidalia was
run on system startup. Patch by Steve Tyree. (Ticket #247)
o Fix a bug that prevented the control panel from displaying when
running on the Enlightenment window manager. Patch by Steve Tyree.
o Rename the CMake variables used to store the location of Qt's lupdate
and lrelease executables. Recent versions of CMake decided to use the
same variable name, which was stomping on mine, resulting in the wrong
lupdate and lrelease executables being used.
o Use the TorProcess subclass of QProcess for launching Tor when hashing
a control password so we can take advantage of its PATH+=:/usr/sbin
trick on Debian there too.
o If a RouterDescriptor object is empty, don't try to display it in the
router descriptor details viewer. (Ticket #479)
o Wait until Vidalia has registered for log events via the control port
before ignoring Tor's output on stdout. Previously we would start
ignoring Tor's stdout after successfully authenticating, but before
registering for log events which, in some cases, could lead to
messages not appearing in the message log.
o Update many translations and remove others than are no longer
up-to-date enough to be useful.
0.2.0 19-Mar-2009
o Add support for changing UI languages without having to restart
Vidalia.
o Add preliminary support for using the KDE Marble widget for the
network map. It's currently a compile-time option and is disabled by
default.
o Add support for displaying Tor's plaintext port warnings. Also gives
the user the option to disable future warnings.
o Add an interface for displaying the geographic distribution of
clients who have recently used a bridge operator's relay.
o Add tooltips to tree items in the help browser's table of contents. Some
of the help topic labels are a bit long.
o Switch to a simpler About dialog and move the license information to a
separate HTML-formatted display.
o Switch to a simpler drag-and-drop installer in the OS X bundles.
o Switch to an MSI-based installer on Windows.
o Clear the list of default CA certificates used by QSslSocket before adding
the only one we care about. Suggested by coderman.
o Support building with Visual Studio again.
o Add a Debian package structure from dererk.
o Updated Albanian, Czech, Finnish, Polish, Portuguese, Romanian,
Swedish, Turkish and many other translations.
0.1.12 16-Mar-2009
o Fix a bug in the hidden service settings configuration class that
could lead to compile errors in Visual Studio and on IRIX.
o Fix a build error that occurred on IRIX when using the MIPSPro
compiler. Patch from Matthew Saunier.
o Remove two duplicated strings in the Spanish translation of Qt's
internal strings (qt_es.po). The duplicated strings caused build
errors when building with Qt 4.5. (Ticket #469)
o Remove the code that altered PublishServerDescriptor when becoming a
bridge, since Tor handles that itself now, and ensure that BridgeRelay
is reset when going from bridge to just-a-client mode.
o Remove an unnecessary #include from helpbrowser.cpp.
o Add an application icon based on Tor's logo to the vidalia.desktop
file.
0.1.11 16-Feb-2009
o Remove support for configuring Tor's User and Group options in the
Advanced settings page.
o Only set HttpsProxy if both the "I use a proxy..." checkbox and the
"Use this proxy for HTTPS also" checkboxes are checked. Otherwise,
unset it. (Ticket #440)
o Fix a use of an uninitialized variable that would occur when Tor was
already running when Vidalia started, and the "Start Tor when Vidalia
Starts" checkbox is checked. (Ticket #443)
o Switch to using 'getinfo address-mappings' instead of
'getinfo addr-mappings'. (Ticket #454)
o Backport a change that removes a verticalSpacing property from a .ui
file, so Vidalia 0.1.x will still build on Qt 4.2. (Ticket #442)
o Fix some memory leaks in the hidden service configuration dialog.
o Fix a CIRC event parsing bug that would occur when the CIRC event
contained a 0-hop circuit path and EXTENDED_EVENTS is enabled.
o Include patches from Steven J. Murdoch that enables the Tor Browser
Bundle to launch Firefox itself without relying on Portable Firefox.
0.1.10 02-Nov-2008
o Add a prettier dialog for prompting people for their control port password
that also includes a checkbox for whether the user wants Vidalia to remember
the entered password, a Help button, and a Reset button (Windows only).
o Fix a crash bug that occurred when the user clicks 'Clear' in the message
log toolbar followed by 'Save All'. (Ticket #434)
o Uncheck the Torbutton options by default in the Windows bundle installer
if Firefox is not installed. (Ticket #421)
o Add a Windows bundle installer page that warns the user that they should
install Firefox, if it looks like they haven't already done so. (Ticket
#421)
0.1.9 02-Sep-2008
o Create the control panel's menubar as a parentless QMenuBar, so it is
visible even if the control panel is not the topmost window. (Ticket #286)
o Add a context menu with a "copy" option to RouterDescriptorView? so
users can copy some text to the clipboard. (Ticket #291)
o Make the Tor status label and Vidalia tray icon tooltip display the same
text after a circuit is established. (Ticket #390)
o Correct the location of the simplified Chinese help files so they will
actually load again.
o Try to load a translation for the current language from Qt's translations
directory, so we can get Qt's internal widgets (e.g. QDialogButtonBox)
translated. (Ticket #375)
o Use "$\r$\n" in the MessageBox strings in the Windows installer
translations, so the newlines appear properly. (Ticket #411)
o Grab the Qt .dlls included in the Vidalia installer directly from the
configured Qt binary directory (as specified by ${QT_BINARY_DIR}).
o Add OPENSSL_BINARY_DIR and MINGW_BINARY_DIR cmake options that can be
used to specify where the Windows installer NSIS scripts should look
for those dlls, rather than requiring them to all be in a "bin" directory
under ${Vidalia_BINARY_DIR}.
o Make the location of the Tor, Privoxy, and Torbutton package files into
configurable CMake options so the bundle can be built without having to
shimmy all these files into some specific directory hierarchy. Makes the
bundle a bit less annoying to build.
o Use the architecture name (e.g. "universal" or "ppc") rather than the
OS X version name (e.g. "tiger" or "panther") when naming OS X packages.
o Update the INSTALL file to recommend out-of-source builds.
o Stop building the nsh2po and po2nsh conversion tools on non-Windows
platforms.
0.1.8 17-Aug-2008
o Make the position of the y-axis on the bandwidth graph variable based on
the width of the axis labels. This works better for languages like Farsi
where "KB/s" somehow becomes 19 characters. (Ticket #373)
o Support alphanumeric circuit and stream IDs, rather than assuming IDs will
always be numeric. Current Tors only use numeric circuit and stream IDs,
but they may some day. (Ticket #400)
o Include ssleay32.dll in the Windows packages so Vidalia won't crash when
it finds an incompatible version of ssleay32.dll in the user's $PATH.
(Ticket #401)
o If the message log is sorted by severity or lexiographically, or if the
user manually repositioned the vertical scroll bar, then retain the scroll
bar's previous position after adding a new message to the log.
o If the current message log layout is right-to-left (e.g. if the user's
translation is Farsi), then use a custom item delegate for the log message
column whose sole purpose is to keep Qt from screwing with the message
text. (Ticket #396)
o Reduce the default number of messages to retain in the message log to 50
messages. Most people never look at the window and the extra 200 messages
just needlessly eat memory.
o Restore the "zoom" and "close" icons in the router and circuit list
context menus. They were lost in the move to the Oxygen icon theme in
0.1.4.
o Make both the 'Ctrl+W' and 'Esc' shortcuts for closing any Vidalia window.
Previously, it was just 'Esc' on Windows and 'Ctrl+W' on all other
platforms.
o Make pressing "Return" mean the same thing as clicking 'OK' in the
config dialog, and make pressing 'Esc' mean the same thing as clicking
'Cancel'. (Ticket #327)
o Fix the icon used for the help browser's window icon.
0.1.7 02-Aug-2008
o Handle spaces in the Tor version number we get from 'getinfo version'
since Tor has included svn revision numbers in its response (e.g.
"0.2.0.30 (r12345)") for a while now.
o Include stdlib.h in the format conversion tools. Fixes the build on some
platforms.
o Rework the message log scrollbar logic so it's consistent again on
Qt 4.4.0. (Ticket #369)
o Remove the horizontal scroll bar behavior in the message log. It was
really annoying and unnecessary since long messages have tooltips anyway.
o Add "TZ=UTC" to the BrowserExecutable's environment variables when launched
via Vidalia.
o Rename the 'pt_BR' Windows installer translation to just 'pt' since there
is apparently nothing 'BR'-specific about it. (Ticket #394)
o Update Tor's URL in the Windows installer and translations.
o Add an nsh2po tool (not built by default) that can be used to extract
LangString entries from an NSIS file and generate a .po file. This was
used to help push our installer translations into Pootle.
o Add a po2nsh tool to convert the Windows installer .po files to NSIS .nsh
files at build time.
o Tell CMake to skip the pkg/ subdirectories that aren't likely to be needed
on the current build platform.
o Updated Czech, French, and German translations.
0.1.6 08-Jul-2008
o Fix a bug in our control socket communication introduced in 0.1.3 that
could cause excessive CPU usage or crashing on some platforms.
o Fix po2ts so that it uses the same encoding to read in a .po file that it
uses to write out the .ts file. This resulted in garbled characters when
viewing some translations on apparently all platforms except OS X.
o Use the correct field when trying to parse the severity value from the
'getinfo status/bootstrap-phase' response.
o Fix compilation of the ts2po and po2ts conversion tools on OS X Panther.
o Tweak the ts2po and po2ts dependencies so Vidalia can be built with Xcode
on OS X again.
o Update ts2po to use 'msgctxt' in .po files for specifying message
context, rather than overloading the "#:" line.
o Update po2ts to tolerate using either 'msgctxt' or an overload "#:" line
for specifying message context.
o If we're building with CMake 2.6, then force CMake 2.4 compatibility for
linker search path behavior. Fixes a CMake warning when building with
CMake 2.6. (Ticket #374)
o Explicitly link in ws2_32 when building with UPnP support on Windows.
(Ticket #374 as well)
o Add a Romanian GUI and installer translation.
o Updated Farsi, Finnish, French, German, and Swedish translations.
0.1.5 21-Jun-2008
o Add support for Tor 0.2.1.2-alpha's new 'status/bootstrap-phase' getinfo
option. Call it to update the progress bar to Tor's current bootstrapping
progress immediately after connecting to Tor.
o Convert to using GNU gettext .po files for our translations, rather than
Qt's .ts format. The .po files are converted to .ts (and then to .qm) at
build time. We switched to .po files so we can point pootle
(https://translation.torproject.org) directly at Vidalia's svn repository.
o Force a repaint() to try to ensure the progress bar and onion status icon
don't overlap briefly when starting Tor.
o Tweak the resize policy for the control panel so the vertical size is
fixed at minimal and sufficient, and the horizontal size is adjustable but
obeys the minimum size hint. (Ticket #363)
o Default to the language chosen by the user during install (Windows-only)
rather than the system language. (Ticket #246)
o Include the text of the LGPLv3 in the binary packages.
o Updated Finnish, French, German, Japanese, Spanish, and Swedish
translations.
0.1.4 13-Jun-2008
o Add a progress bar and status label for displaying Tor's startup progress
based on new Tor bootstrapping status events.
o Include UPnP support based on the MiniUPnPc library. Also added a UPnP
test dialog to help users determine if their router or firewall supports
UPnP. Initial patch for UPnP support from Steven J. Murdoch.
o Switch all of Vidalia's icons to the KDE Oxygen theme so that our icon set
has a a DFSG-compatible license.
o Fix a crash bug that occurred when opening the settings dialog when Tor
was not running. (Ticket #360)
o Respond to mouse wheel events on the network map by zooming in or out on
the map image. Patch from Vern Sun.
o Make external links in the help browser clickable, which will try to open
them in the user's default browser. The user is first warned that their
request might not be anonymous if their default browser is not configured
to use Tor.
o Apply some Tor trademark compliance updates to user-visible strings.
o Cut down the margin around the table of contents in the help browser. It
looked goofy with so much empty space.
o Update Finnish, Spanish, and Swedish translations.
0.1.3 25-May-2008
o Added a hidden service configuration UI designed and implemented by
Domenik Bork.
o Added a "Proxy Executable" configuration option and UI that allows
you to specify an HTTP proxy application that Vidalia will start and
stop along with Tor.
o Fix a bug in how Vidalia sent control commands to Tor that would
cause Vidalia to freeze when built against Qt 4.4.0. (Ticket #353)
o If we're running Tor >= 0.2.0.13-alpha, then check the descriptor
annotations for each descriptor before deciding to do a geoip lookup
on its IP address. If the annotations indicate it is a special purpose
descriptor (e.g., bridges), then don't do the lookup at all. (Ticket #326)
o Fix the OSX_FAT_BINARY build option so that it actually does produce a
Universal binary when enabled. (Ticket #342)
o Rename src/util to src/common, since libutil.a was apparently conflicting
with libUtil.dylib when compiling Vidalia on OS X Leopard.
o Switch to using 'getinfo ns/all' instead of 'getinfo network-status' to
get a list of available relays. 'getinfo network-status' was deprecated
long ago.
o Only display the running relays in the big list of relays to the left of
the network map. Listing a big pile of unavailable relays is not
particularly useful, and just clutters up the list.
o Add support for the 'usefeature verbose_names' control command that was
introduced way back in Tor 0.1.2.2-alpha.
o Correct the tab order on the custom bandwidth settings tab. (Ticket #351)
o Remove the 'Run Tor as a Service' checkbox. Lots of people seem to be
clicking it even though they don't really need to, and we end up leaving
them in a broken state after a reboot.
o Restore the Windows application icon that was inadvertently removed in
0.1.2. Reported by dr|z3d. (Ticket #358)
o Add a Turkish GUI translation from Yunus Kaba.
o Updated Finnish and Swedish translations.
0.1.2 24-Mar-2008
o Correctly load the CA certificate used to verify SSL connections to the
GeoIP server. This caused Vidalia >= 0.1.0 clients built against Qt >=
4.3.2 to be unable to retrieve updated GeoIP information. (Ticket #349)
o Fix compilation when UINT_MAX is not defined. (Ticket #350)
o Bridges are no longer required to have a DirPort set as of Tor
0.2.0.13-alpha, so stop forcing it on for bridges. At some point, we'll
likely start forcing DirPort to be disabled for bridges, and on by default
but optional for normal relays. (Ticket #337)
o Fix a typo in VidaliaMacros.cmake that would allow configuration to
continue even if windres.exe couldn't be found.
o Update the version of Torbutton included in the OS X bundle to
1.1.17-alpha, and actually include the bundle's uninstaller script.
o Updated Finnish and Swedish translations.
0.1.1 17-Mar-2008
o Use CMake to configure the version number that ends up getting displayed
in the About box.
o Update the RPM .spec file with the new CMake requirements. Patch from Oliver
Niesner.
o TunnelDirConns and PreferTunneledDirConns are now enabled by default as of
Tor 0.2.0.22-rc.
o Don't check the 'My ISP blocks connections to the Tor network' box simply
because TunnelDirConns is enabled. Checking the box still enables
encrypted directory connections on older Tors.
o Add a Japanese GUI translation from Nardog
o Updated Finnish and Swedish translations
0.1.0 01-Mar-2008
o Migrate to CMake as our build system, instead of the previous mix of
autoconf and qmake. See the updated INSTALL file for more information.
o Add an OpenSSL license exception so Vidalia can be linked against OpenSSL
and redistributed. Also include the text of the GPLv3, since our license
says "GPLv2 or later."
o Don't try to 'SETCONF HashedControlPassword' if we couldn't hash the
control password, otherwise we could end up disabling authentication.
(Ticket #305)
o If Vidalia is built against Qt >= 4.3 with SSL support, then do our GeoIP
lookups over an SSL connection.
o Work around a crash bug with a sorted QTreeWidget that occurs with Qt
4.3.3, and possibly later versions as well.
o Parse ReachableAddresses values properly when there are multiple ports
specified on a single line.
o RESETCONF the value of PublishServerDescriptor when the user switches from
being a relay to acting as only a client.
o Add support for Tor's STATUS_GENERAL, STATUS_CLIENT, and STATUS_SERVER
status events.
o Listen for the DANGEROUS_VERSION general status event and warn the user
if their version of Tor is no longer recommended.
o Listen for the CIRCUIT_ESTABLISHED client status event and only turn the
yellow onion status icon green after Tor has successfully established a
circuit.
o If the user's vidalia.conf contains an empty value for their Tor
executable, use the default for the user's platform.
o If the user is running a bridge relay with Tor 0.2.0.13-alpha or newer,
then set 'BridgeRelay 1' when configuring their bridge.
o Don't save a randomly generated control password to Vidalia's
configuration file. If Vidalia gets disconnected from Tor or crashes, we
will no longer be able to reconnect.
o Don't let users save an empty string for a Tor executable in the Settings
dialog.
o Apply the changes for settings pages in the same order in which the pages
appear in the Settings dialog. The only two pages for which this matters
are the 'Network' and 'Sharing' pages. (Ticket #336)
o Old Jabber clients apparently use port 5223 for encrypted connections. So,
include that port as part of the "Instant Messaging" exit policy checkbox.
(Ticket #333)
o Stop displaying flags next to the language names in the Appearance
settings page.
o Add a "How do I find a bridge?" link and corresponding help text to the
'Network' settings page.
o Add a 'BrowserExecutable' configuration option to launch a Web browser
when Tor has built a circuit, and exit Vidalia when the browser is closed.
Patch from Steven J. Murdoch .
o Add 'ProxyExecutable' and 'ProxyExecutableArguments' configuration options
to launch a proxy application with given parameters when Vidalia starts,
and close it when Vidalia exits.
Patches from Steven J. Murdoch .
o Respond to the Delete key in the network map by closing whatever circuits
or streams are currently selected. Suggested by Andrew Lewman.
o Rename the 'Relay' settings page to the 'Sharing' settings page.
o Add a vidalia.desktop desktop entry file that can be installed with
'make install'.
o Add an Albanian GUI translation from Frederik Nosi.
o Add a Hebrew GUI and Win32 installer translation.
o Updated Finnish, Norwegian, Polish, Russian, and Swedish translations.
0.0.16 22-Nov-2007
o Fix compilation on Mac OS X 10.3 (Panther).
o GETCONF RelayBandwidthRate and RelayBandwidthBurst properly on Tor >=
0.2.0.1-alpha. In 0.0.15, we were SETCONFing RelayBandwidthFoo when
appropriate, but always GETCONFing BandwidthFoo. Fixes Ticket #298.
o Display the correct default list of allowed ports in the Network settings
page, and don't try to save an empty list. Noticed by Roger Dingledine.
o Only remember the torrc and datadir values if Vidalia started Tor, or
if the user changed the displayed values.
o Fix some dumb logic in determing whether the Windows we're running on
supports window transparency.
o Use the correct icon for the "Close Stream" context menu action in the
circuit and stream list widget.
o Create the message log, network map, bandwidth graph, and settings dialogs
without parents, so they can be independently brought to the foreground on
Windows Vista.
o Update the default bandwidth rate and burst rate to 5MB and 10MB,
respectively, to match Tor's defaults.
o Make the "Use this proxy for HTTPS also" checkbox checked by default.
o Disable the labels that display the user's bridge relay information if the
user is not running a bridge, instead of just disabling the copy button.
o Modified the Mac OS X bundle installer to set Vidalia to start
automatically on login for the user that installed the bundle.
o Added an Arabic translation from Ahmad Gharbeia.
o Updated Finnish, German, Simplified Chinese, and Traditional Chinese
translations.
0.0.15 24-Oct-2007
o Add a new 'Network' settings page to the config dialog that lets users
configure an HTTP/HTTPS proxy, specify allowed ports if they are behind a
restrictive firewall or proxy, and set up bridges and tunneled dir conns.
o Add a 'Help Censored Users Connect to the Tor Network' option to the
'Server' settings page to help users set up their Tor as a brigde relay.
This option is only available for those running Tor 0.2.0.8-alpha or
newer.
o Stop hardcoding a font size of 10 in many places. This made the fonts on
Mac OS X look non-standard and inconsistent.
o Restructure the code that manages GETCONFing values from Tor and then
later SETCONFing any changed values to make it easier to add more pages
like the 'Network' and 'Server' settings pages in the future.
o If we prompt the user to enter a control password and they enter one,
don't keep trying to use our randomly generated password.
o Fix a bug in the network map that would cause the user to sometimes be
unable to select a circuit or server after clicking and dragging the mouse
in one of the lists. (Ticket #269)
o Stop leaking memory for pretty much every circuit we plotted on the network
map. Found by Roger Dingledine and his Valgrind.
o Stop leaking memory if TorMapWidget::addRouter() is called for a router
that is already on the map. Also found by Roger Dingledine and his
Valgrind.
o Stop leaking memory used by QTranslator and the configuration dialog on
exit.
o Default to using an ORPort of 443 when setting up a server on Windows.
9001 is still the default everywhere else.
o Fix a crash bug that could occur when Vidalia gets disconnected from Tor
while waiting for a response to a previous command. Bug reported by Roger
Dingledine. (Ticket #295)
o Create a single TorProcess object used to start and stop Tor, instead of
creating a new one each time and cleaning up after Tor exits. (Ticket
#294)
o Do the control connection asynchronously so we aren't trying to call
waitForConnected() in the control socket thread before it has an event loop
running.
o Don't start Tor or test for a running Tor with an open control port until
the main event loop is running.
o Older Tors write their state file even if all we're doing is
--hash-password. So if the user has configured a non-default data
directory, include that in the list of command line arguments when we run
Tor to hash the user's control password.
o Support changing Tor's control port and authentication settings without
having to restart Tor for the settings to take effect.
o Recognize the REMAP stream status in STREAM events.
o Allow the control panel window to expand horizontally and vertically to
fit longer translated text labels.
o Make VClickLabel right-to-left aware so the control panel buttons look
correct when using the Farsi translation.
o Fix our configure.in to produce a Makefile instead of an Xcode project on
OS X. This only affected users who got Qt 4.3 from Trolltech's .dmg
installers.
o Fix our configure.in to tell QMake the fully-expanded path to which our
man page should be installed.
o Fix our configure.in so we can use it to build under Cygwin or MinGW with
Qt >= 4.3.0.
o Move to a consistent use of the word "Relay" instead of "Server" or
"Router" in the interface.
o Convert the path separators in a configured data directory to whatever the
platform standard is.
o Remove the custom palette used in all Vidalia's windows that had been
around since 0.0.1.
o Attempt to standardize the GUI fonts to whatever the user's platform
thinks is best.
o Default to using Qt's Windows Vista style on Windows Vista. On other
Windowses or any non-Mac platform, default to the Cleanlooks style if
we're building with Qt >= 4.3.
o Add some information to the help browser about the new network settings
and bridge relay configuration, as well as the new authentication
settings in 0.0.14.
o When the user clicks the Help button in the Settings dialog, take them
directly to the help topic for whichever settings page they are currently
viewing.
o Added Torbutton 1.1.9.1-alpha to the Mac OS X bundles, thanks to
Andrew Lewman.
o Disable enable-edit-actions, enable-remote-toggle, and
enable-remote-http-toggle in the bundled Privoxy configuration. Suggested
by Greg Fleischer.
o Updated Finnish, French, German, Norwegian, Polish, and Russian
translations.
0.0.14 26-Aug-2007
o Add support for Tor's HashedControlPassword and CookieAuthentication
options. Password authentication is enabled by default.
o Add support for Tor's new PROTOCOLINFO control command.
o Support running on Windows NT 4.0 again.
o Check to see if "%PROGRAMFILES%\Vidalia Bundle\Tor\tor.exe" exists when
setting the default Tor executable on Win32. If it doesn't, fall back to
"%PROGRAMFILES%\Tor\tor.exe". (Ticket #262)
o Allow the people who think clicking 'New Identity' is the solution to
everything to be disappointed six times per minute, instead of once.
o Add the ability to configure Tor's data directory.
o Give users the option of not removing %APPDATA%\Tor and %APPDATA%\Vidalia
in the Win32 Vidalia and bundle installers.
o Add a Czech GUI and installer translation from el Mar.
o Updated Finnish and German translations.
0.0.13 02-Aug-2007
o Remove the control protocol version checking logic, since Tor will now
just hang up if the first command received isn't a valid AUTHENTICATE
command.
o Fix a bug where Vidalia would display an incorrect error message if the
user started Vidalia, stopped Tor, ran Tor manually, then clicked 'Start
Tor'. (Reported by arma)
o Maintain a list of address mappings, so we can try to replace IP addresses
in stream targets with host names when displaying them on the network map.
(Suggested by phobos)
o Stop including help documentation for each language, even if it is
untranslated. If there is no translated help documentation for a language,
simply load the documentation from the English version.
o Use RelayBandwidthBurst and RelayBandwidthRate on Tor >= 0.2.0.1-alpha.
o Remove from the server config page the 'Address' text box, the 'Get
Address' button, and 'Automatically Update' checkbox.
o Don't do balloon messages on Windows 2000; I'm told it doesn't work even
though QSystemTrayIcon::supportsMessages() says it should.
o Removed a duplicate check when determining what control event Vidalia
received from Tor.
o Check /usr/sbin/ for a Tor binary if one isn't found in $PATH.
o Fixed compilation on Mac OS X Panther.
o Support building with Qt 4.3 in our configure.in (no code changes
required).
o Change the "Start Tor" control panel button text to "Starting Tor" while
Tor is starting.
o Added a "Control Panel" item to the OS X dock icon's context menu.
o Added tooltips to the circuits and streams listed on the network map.
o Stop putting a torrc in %APPDATA%\Tor if the user is also installing Vidalia,
since they'll just get confused from having two torrc files.
o Added a Swedish GUI and installer translation from Amin Amini.
o Added an Italian installer translation from Alex Mazzariol.
o Update Finnish, French, German, Italian, Russian and Spanish translations.
0.0.12 01-Jun-2007
o Added a new "Control Panel" main window that appears when Vidalia first
starts. This dialog is for people who either aren't trained to look in
their system tray area for a Vidalia icon, or those who simply do not have
a system tray area.
o Added -logfile and -loglevel command-line options that can log useful
Vidalia debugging messages to a file or to stdout. Hopefully this will
help make tracking down future Vidalia bugs easier.
o Add a box to the Advanced settings page to change the IP address on which
we will try to connect to Tor's control port, instead of always assuming
127.0.0.1. (Ticket #81)
o Don't yell at the user if our SAVECONF fails after changing some
configuration settings; just remember the intended settings and reapply them
next time Tor runs.
o Restore a window to its previous state each time it is opened, not just
the first time after Vidalia is started.
o Only allow the 'New Identity' button to be clicked once every 60 seconds.
o Show the number of online servers in the status tip for the server list,
as well as the total number of servers.
o Expand filenames that use "~/", "%APPDATA%", or "%PROGRAMFILES%" in either
the path to Tor's executable or torrc.
o Fix the message log timestamp format to be "MMM dd hh:mm:ss.zzz", instead
of "MMM dd hh:mm:ss:zzz".
o Don't create the help browser window until we actually need it, so we
don't waste memory on a window the user might never use.
o Fix a minor bug that's been around since 0.0.1: actually remove objects
from the list of targets for an event, instead of from a copy of the list.
o Display command-line options information as a message box so even Win32
folks can see it, if they give Vidalia a bogus argument.
o Revert back to the single uninstaller strategy on Win32, so don't leave
program groups behind after uninstalling the bundle. (Ticket #237)
o Start Privoxy minimized if the user selects "Run installed components now"
after completing the Win32 installer.
o Don't skip past the Win32 installer results immediately, since there could
have been errors the user should see.
o Include a default.action file for Privoxy in the Win32 and OS X bundles
with the +limit-connect{1-} fix.
o Include some more helpful text in the Win32 installer welcome screen and
category descriptions.
o Fix the paths to *-spec.txt in the script that builds the OS X bundles.
o Include Tor_Uninstaller.applescript and uninstall_tor_bundle.sh in the OS
X bundle. (Ticket #230)
o Updated Dutch, Finnish, French, German, Norwegian, Polish and Spanish
translations.
0.0.11 07-Feb-2007
o Fix a race condition that could (and did) cause Vidalia to freeze.
o RESETCONF all server-related settings when the be-a-server checkbox gets
unchecked, not just ORPort and Nickname.
o Add support for zlib or gzip compressed GeoIP responses.
o Handle chunked transfer encodings properly in GeoIP responses.
o Be a little less eager to send GeoIP requests right away. Now we wait 10
seconds after adding an address to the queue, or a maximum of 30 seconds,
before sending the request.
o Tolerate entries in geoip-cache that have no timestamp. If an entry does
not have a timestamp, use the current date and time.
o Respond to double-clicks on the map. Double left-click zooms in towards
the mouse pointer and double right-click zooms out.
o If Vidalia is built with Qt >= 4.2, use the open and closed hand cursors
in ZImageView when panning the world map.
o Qt >= 4.2 handles the sorting in addTopLevelItem() in the server list. We
still do the sorted inserts ourselves in older Qts.
o Display circuits as a list of server nicknames (like we currently do), but
save the original circuit paths (possibly with key IDs for non-Named
servers) so we don't display the wrong server information when the user
selects that circuit.
o Fix a bug introduced in 0.0.10 that caused a server's little pinpoint on
the map to not be highlighted green when the server is selected in the
server list.
o Update the stream target address on every stream status event, not just
NEW stream events.
o Add an EU flag for the server list.
o Add a "Cancel" button to the message box that asks server operators if
they want to delay server shutdown or kill Tor right away. (Ticket #222)
o Add version information to our compiled Win32 vidalia.exe.
o Be more tolerant of Win32 people removing the Tor service out from under
Vidalia.
o Explicitly specify the tab order in the bandwidth graph.
o Fix a bug in parsing Tor's version string when it contains modifiers such
as '-alpha'.
o Make Circuit::hops() correctly return an empty QStringList for empty paths,
instead of a QStringList with one empty QString.
o Do a better job of detecting Qt 4.2 debug libs on OS X. There were a few
necessary non-Qt libs missing from LIBS when we did our AC_TRY_LINK.
o Add vidalia.spec to our configure.in, so the RPM spec file stays current.
o Add a Traditional Chinese installer and GUI translation from Cloud.
o Updated Dutch, Farsi, Polish, Russian, and Simplified Chinese translations.
0.0.10 25-Dec-2006
o Load NT service functions on demand so we can run on Windows 95/98/ME
again. (Ticket #211)
o Add a column to the list of servers in the network map window, with a
little flag icon for each server.
o If the network map window is not visible, queue all GeoIP requests until
either the window becomes visible again or the queue contains requests for
at least one-quarter of all known servers.
o If we get a valid geoip response telling us the geoip database doesn't
have a location for the requested IP address, cache that response for one
week so we don't keep sending requests that are likely to fail anyway.
o Use QSystemTrayIcon when available (except on Mac). If we are using
QSystemTrayIcon on systems that support balloon messages, use a balloon to
indicate when NEWNYM is successful. We still show a message box when NEWNYM
fails. (Ticket #183)
o Add a graph style dropdown box to the bandwidth graph settings, so you can
choose between a fancy alpha blended area graph and a faster, simpler line
graph.
o Add a button to continue starting Vidalia anyway, even if Vidalia thinks
there might be another Vidalia process already running. It's possible that a
previous Vidalia did not exit cleanly and another process ended up with
the old Vidalia's PID.
o Add a "Zoom to Circuit" option to the circuit context menu in the network
map's list of circuits.
o Add a context menu to the dock icon on OS X. (Ticket #135)
o If we're building with Qt >= 4.2.0, then use its new saveGeometry() and
restoreGeometry() functions to save and restore window size and position.
If we're still using an old Qt, make sure the window fits on screen when
we try to restore it. (Ticket #207)
o Fix a bug in how the server points were keyed on the network map that
could cause some circuits to not get drawn. (Ticket #175)
o Really close the read channel when we want to stop reading from the Tor
process's stdout. This would sometimes cause duplicate messages in the
message log if Vidalia was running on a non-English-speaking Windows.
o Be more correct about what we consider as valid latitudes and longitudes.
o Give a better error message if we fail to determine what version of Tor's
control protocol is being spoken.
o Clarify some labels in the message log settings. (Ticket #203)
o Settle on a convention of not ending tool tips or status tips with a
period.
o Start shipping a geoip-cache file in our Win32 installers so people have
some initial geographic information, instead of starting out entirely
empty-handed.
o Add a Farsi translation.
o Add a Spanish translation contributed by desolator.
o Add a Portuguese (Brazilian) translation contributed by Mabat Haram.
o Add a Simplified Chinese installer translation contributed by omg.
o Updates to Finnish, French, German, Italian, Norwegian, Polish,
Russian, and Simplified Chinese translations.
0.0.9 05-Nov-2006
o Added a new, more intuitive interface for setting a server's bandwidth
rate and exit policies.
o Improved our ./configure script so it will detect old or non-debug
versions of Qt and link accordingly.
o Added support for more easily building Qt as a Universal binary on OS X.
o Added a right-click option to circuits listed in the network map dialog to
close the circuit (Ticket #176).
o Added a right-click option to servers listed in the network map dialog to
zoom in on the server on the map (Ticket #176).
o Stop using a custom font and just use the platform default on all dialogs.
o Add "Close Window" shortcuts for Linux (Ctrl+W).
o Fixed a crash bug that would occur when saving messages in the message
log (Ticket #185).
o Fixed a bug that would cause messages with identical timestamps to not
get copied to the clipboard (Ticket #190).
o Ask if the user wants to delay shutting down their server when Vidalia
exits, to give clients time to find new circuits. We previously only did
this when the user stopped Tor, but wasn't exiting Vidalia.
o If Windows is restarting, then don't ask about delaying a server shut
down; just stop Tor and exit immediately so Windows doesn't yell at us.
o Detect if Tor was installed as an NT service prior to Vidalia, so we don't
accidentally remove it.
o Create a new torrc and specify a control port for the Tor NT service, so
it doesn't die when the user tries to start the service and we don't have
to tell the user to go add a line to their torrc.
o Fixed a bug that caused Vidalia to crash if it tried to read in a bogus
geoip-cache file from its data directory (Ticket #184).
o Refuse to cache information we did not ask for that we received in response
to a GeoIP request.
o Wait no more than ten seconds after queueing a GeoIP request before
sending it, so requests don't starve if we keep constantly getting new
descriptors.
o Ask Tor what its SocksPort and SocksAddress is before building our GeoIP
request, instead of always assuming Tor is listening on 127.0.0.1:9050.
o Explicitly specify the sort order for the message log and server list, so
things aren't backwards when linking with Qt 4.2.x.
o Add support for translating the Vidalia and Vidalia bundle installers.
o Start bundling Torbutton with the Vidalia bundle installer.
o Add a Norwegian (Bokmal) translation contributed by xiando.
o Updates to the Finnish, French, German, and Polish translations.
0.0.8 03-Oct-2006
o Vidalia will now attempt to connect to an existing Tor's ControlPort
before starting its own Tor process. If it finds a Tor with an open
ControlPort, Vidalia will "attach" to that Tor instead of starting a new
process.
o Vidalia now supports running Tor as an NT service on Windows.
o When Vidalia starts its own Tor process, it will now default to starting it
with a "-f ~/.vidalia/torrc", to avoid permissions conflicts when running
Tor as a user that does not have write access to the default torrc. The
torrc used when starting Tor is still configurable.
o Fix a bug that was causing unexpected behavior with many unrelated Windows
applications.
o Do a better job of determining if another Vidalia process is running on
Windows, to eliminate all the false positives reported.
o Major performance improvements related to loading the network map.
o Support receiving server identities in circ events, as well as names, so
Vidalia will work with Tor 0.1.2.2-alpha and later.
o Moved the "New Identity" button to the main popup menu for easier
access.
o Vidalia dialogs remember their last size and location when Vidalia exits
and restore their size and location the next time Vidalia runs.
o Vidalia windows now close in response to a Command-W on Mac OS X.
o Added a "Zoom To Fit" button to the network map, to zoom in on the active
circuits.
o Numerous minor aesthetic and usability improvements to many of Vidalia's
dialogs.
o Fix a bug that was causing signal conflict warnings on Debian.
o Fix a crash that would occur when exiting Vidalia after an attempt to
start Tor with a non-existent executable.
o Add a Bulgarian translation contributed by kutia0001.
o Add a Dutch translation contributed by Saedian.
o Add a Hungarian translation contributed by Tibor Fekete.
o Add a Polish translation contributed by ZeeWolf.
o Updates to the Finnish, French, and Russian translations.
0.0.7 07-Jul-2006
o Fix a bug that was causing Vidalia to freeze frequently for some people,
particularly when running at a verbose log level.
o Fix a bug that would cause Windows Vidalias to not want to start after
Vidalia had been killed via the Task Manager.
o Add a French translation contributed by Michel Burkhardt.
o In the network map, update the displayed uptime by looking at the difference
between now and the publication time, and add that difference to the published
uptime.
0.0.6 23-Jun-2006
o Fix the network map to properly remove circuits after they are closed.
o Fix our configure script to properly handle the --prefix option (patch by
Alexander Wirt).
o Check if Vidalia is already running when we start. If Vidalia is already
running, then warn and exit in the second instance.
o Strip all invalid characters from the server's nickname and make sure the
user can't enter any.
o Default to the Tor binary located in the user's $PATH, instead of trying
to guess directory locations.
o Add support for adjusting a server's BandwidthRate and BandwidthBurst
values.
o Store Vidalia's settings in a file, (rather than in the registry on
Windows), so Vidalia can be more portable. Note that settings aren't
"imported" from the registry, so 0.0.5 users will have to configure
their Vidalia settings again.
o Make the bandwidth graph just a normal window instead of a tool window, so
it can hide behind other Vidalia windows, if necessary.
o On OS X, ensure that the About, Configure, and Exit actions get merged
into the "Vidalia" menu in the default menubar when Vidalia is running in
a non-English language.
o Add an Italian translation contributed by Alex Mazzariol.
o Add a Russian translation contributed by ygrek.
o Add a manpage for Vidalia contributed by Alexander Wirt.
0.0.5 02-Jun-2006
o Make the "Always On Top" property of the bandwidth graph optional.
o Add a new dialog showing a list of routers that the user's Tor currently
knows about, as well as the user's current circuits and streams and
detailed information about individual routers. The circuits and router
geographic locations are plotted on a world map. Thanks to Christoph
Sieghart, Michael Zuercher, and Adam Tomjack for help with this feature.
o Stop automatically scrolling to the newest item added to the message log,
if the user is looking through their message history.
o Create a horizontal scrollbar on the message log when an excessively long
message is logged.
o Add support for the NEWNYM signal in the form of a "New Identity"
button, to force Tor to use only clean circuits for new application
requests.
o Add a Mac OS X bundle.
o Add a Finnish translation contributed by DJHasis.
o Add a German translation contributed by Christoph Sieghart.
o Fix a bug that caused people running servers to update their public IP
address too often if they had the "Automatically Update" option checked.
0.0.4 09-May-2006
o Add a fixed set of Windows .ico files from Dan Christensen. Our
contributed set in 0.0.3 apparently had a blank image in it that some old
Windowses would use instead of the icon that actually had an image.
o Add an option for servers to check periodically to see if their public IP
address has changed.
o Give servers the option to shut down after 30 seconds, to give clients
time to find new circuits, instead of just always killing Tor immediately.
o Improve GUI responsiveness when waiting for the Tor process to finish
starting up.
o Be smarter about guessing the default location of Tor in non-English
Windowses.
0.0.3 13-Apr-2006
o Fixed a server configuration bug that caused people to not really be a
middleman node, even though the checkbox told them they were.
o Fixed a bug in choosing a default language that caused help documents to
sometimes not appear.
o Fixed the Win32 bundle installer to not leave 2 files and a registry key
laying around after an uninstall. Also give users the option of launching
Vidalia when the solo installer is finished.
o Fixed a bug where Vidalia would ignore Windows when asked to shut down
because the system is restarting.
o Improved tray icon support on older Windowses. Also started using a new
set of icons created by Matt Hanson, based on our previous set by Corinna
Habets.
o Improved help document accessibility by adding "Help" buttons to many
dialogs and error message boxes.
0.0.2 02-Apr-2006
o Added an integrated help browser and documentation.
o Added exit policy configuration support for servers.
o Added support for language translations and language selection.
o Added a Simplified Chinese (zh_CN) translation from Wu Xiaoguong.
o Added support for changing Vidalia's interface style.
o Aesthetic improvements in many dialogs.
0.0.1 28-Feb-2006
o Initial testing release.
o Basic features include:
- Starting/stopping/monitoring Tor
- Bandwidth graph
- Message log
- Basic server configuration
vidalia-0.2.21/CMakeLists.txt 0000664 0000000 0000000 00000011335 12056211037 0015745 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
set(VER_MAJOR "0")
set(VER_MINOR "2")
set(VER_PATCH "21")
set(VERSION "${VER_MAJOR}.${VER_MINOR}.${VER_PATCH}")
message(STATUS "Configuring Vidalia ${VERSION}")
project(Vidalia)
## Specify the minimim required CMake version
cmake_minimum_required(VERSION 2.4.7)
if (COMMAND cmake_policy)
# Force CMake 2.4 compatibility for handling linker search paths
cmake_policy(SET CMP0003 OLD)
endif(COMMAND cmake_policy)
## We declare this option here, because it determines the minimum
## required Qt version
option(USE_MARBLE "Enable the KDE Marble-based map widget." OFF)
## Specify the minimum version of Qt required
set(QT_MIN_VERSION "4.3.0")
## Specify the Qt libraries used
include(FindQt4)
find_package(Qt4 REQUIRED)
set(QT_USE_QTNETWORK true)
set(QT_USE_QTXML true)
if (USE_MARBLE)
set(QT_USE_QTSVG true)
set(QT_USE_QTWEBKIT true)
set(QT_USE_QTSCRIPT true)
set(QT_USE_QTDBUS true)
endif(USE_MARBLE)
include(${QT_USE_FILE})
include(${CMAKE_SOURCE_DIR}/cmake/VidaliaMacros.cmake)
include(CheckIncludeFile)
include(CheckIncludeFileCXX)
include(CheckTypeSize)
include(CheckFunctionExists)
if (WIN32)
include(${CMAKE_SOURCE_DIR}/cmake/FindWiX.cmake)
endif(WIN32)
if(MSVC_IDE)
set(CMAKE_SUPPRESS_REGENERATION TRUE)
set(LIBRARY_OUTPUT_PATH ${CMAKE_BINARY_DIR}/bin)
set(EXECUTABLE_OUTPUT_PATH ${CMAKE_BINARY_DIR}/bin)
endif(MSVC_IDE)
## Define Vidalia-specific CMake options
if (APPLE)
option(OSX_TIGER_COMPAT "Build an OS X 10.4 Compatible Vidalia." OFF)
if (OSX_TIGER_COMPAT)
set(CMAKE_EXE_LINKER_FLAGS "-mmacosx-version-min=10.4"
CACHE STRING "Flags used by the linker." FORCE)
set(CMAKE_OSX_SYSROOT "/Developer/SDKs/MacOSX10.4u.sdk"
CACHE STRING "isysroot used for universal binary support" FORCE)
endif(OSX_TIGER_COMPAT)
option(OSX_FAT_BINARY "Build Vidalia as a Universal binary." OFF)
if (OSX_FAT_BINARY)
set(CMAKE_OSX_ARCHITECTURES "ppc;i386"
CACHE STRING "OS X build architectures" FORCE)
set(CMAKE_EXE_LINKER_FLAGS "-mmacosx-version-min=10.4"
CACHE STRING "Flags used by the linker." FORCE)
set(CMAKE_OSX_SYSROOT "/Developer/SDKs/MacOSX10.4u.sdk"
CACHE STRING "isysroot used for universal binary support" FORCE)
endif(OSX_FAT_BINARY)
option(OSX_FORCE_32BIT "Force a 32-bit build for compatibility." OFF)
if (OSX_FORCE_32BIT)
add_definitions(-m32)
set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -m32"
CACHE STRING "Flags used by the linker." FORCE)
endif(OSX_FORCE_32BIT)
endif(APPLE)
## Define if compiled with Windows 2k support
option(WIN2K "Enable Windows 2k support." OFF)
## UPnP support is currently optional (enabled by default)
option(USE_MINIUPNPC "Enable UPnP support using the MiniUPnPc library." ON)
## Crash reporting via Google Breakpad is optional (disabled by default)
option(USE_BREAKPAD "Enable Google Breakpad crash reporting." OFF)
if (USE_BREAKPAD)
include(${CMAKE_SOURCE_DIR}/cmake/FindBreakpad.cmake)
endif(USE_BREAKPAD)
## Automatic software update is optional (disabled by default)
if (WIN32)
option(USE_AUTOUPDATE "Enable automatic software update support." OFF)
endif(WIN32)
## Find the KDE Marble library
if (USE_MARBLE)
include(${CMAKE_SOURCE_DIR}/cmake/FindMarble.cmake)
endif(USE_MARBLE)
## Find the MaxMind GeoIP library
option(USE_GEOIP "Enable GeoIP lookups via a local MaxMind database" OFF)
if (USE_GEOIP)
include(${CMAKE_SOURCE_DIR}/cmake/FindGeoIP.cmake)
endif(USE_GEOIP)
## Check for system header files
check_include_file("limits.h" HAVE_LIMITS_H)
check_include_file("sys/limits.h" HAVE_SYS_LIMITS_H)
check_include_file("signal.h" HAVE_SIGNAL_H)
## Check for the sizes of various data types
check_type_size(int SIZEOF_INT)
## Check for the existence of some platform-specific functions
if (HAVE_SIGNAL_H)
set(CMAKE_REQUIRED_INCLUDES ${CMAKE_REQUIRED_INCLUDES} "signal.h")
check_function_exists(sigaction HAVE_SIGACTION)
check_function_exists(signal HAVE_SIGNAL)
endif(HAVE_SIGNAL_H)
## Write out a configuration file
configure_file(
${CMAKE_CURRENT_SOURCE_DIR}/config.h.in
${CMAKE_CURRENT_BINARY_DIR}/config.h
)
include_directories(${CMAKE_CURRENT_BINARY_DIR})
## Add the actual source directories
add_subdirectory(src)
add_subdirectory(doc)
add_subdirectory(pkg)
vidalia-0.2.21/CREDITS 0000664 0000000 0000000 00000006122 12056211037 0014223 0 ustar 00root root 0000000 0000000 Vidalia is currently developed by:
Matt Edman
Contributors:
Domenik Bork was a Google Summer of Code student during Summer 2008 and
added the hidden service configuration interface.
Ren Bucholz created some of the
onion images off of which Corinna's icons and some of our own images are
based.
Dan Christensen added additional image formats to
the .ico files to support more Windowses. He also created the graph style
icons in the bandwidth graph settings.
dr|z3d created the Vidalia logo design and image files and helped redesign
the Vidalia website.
Geoff Goodell supplied us with
nearly all of the flag icons that we use in the Appearance configuration
page and network map. He also created the router status icons we use in
the network map.
Corinna Habets created the images off which
our application icons are based.
Matt Hanson tweaked Corinna's images a bit
and created some .icos based off of them.
Justin Hipple co-founded the Vidalia project
and helped with lots of the initial development.
Andrew Lewman wrote the original Mac OS X bundle installer off which
Vidalia's is based, and also added Torbutton to the bundle.
This product includes GeoLite data created by MaxMind, available from
http://maxmind.com/
Steven J. Murdoch wrote the code
to launch a web browser when Tor has built a circuit and close Vidalia when
the browser has exited. He also implemented UPnP support using the MiniUPNPc
library.
Brandon Nase designed and built
the original vidalia-project.net website.
Christoph Sieghart (sigi) gave us some code that
converts world space coordinates (latitude,longitude) into image space
coordinates (x,y) which we used in the Net Viewer.
Michael Zuercher and Adam Tomjack of Zuerchertech LLC
gave us the ZImageView class which handles
drawing, scrolling and zooming the map image in the Network Viewer.
Translators:
Albanian Frederik Nosi
Arabic Ahmad Gharbeia
Bulgarian kutia0001
Czech el Mar
Dutch Ater Atrocitas
Farsi persepolis
Hossein
Finnish DJ Hasis
French Michel Burkhardt
eight118
Daniel Berthereau
German Christoph Sieghart
Steffen Dabbert
Hebrew Anonymous
Hungarian Tibor Fekete
Italian Alex Mazzariol
Japanese Nardog
Benessa Defend
Norwegian xiando
Micromus
Polish ZeeWolf
Portuguese Mabat Haram
Russian ygrek
Spanish dererk
desolator
Simplified Chinese Wu Xiaoguang
LinHongJun
Swedish Amin Amini
DJHasis
Traditional Chinese LinHongJun
Turkish Yunus Kaba
Omer Ishakoglu
vidalia-0.2.21/HACKING 0000664 0000000 0000000 00000021446 12056211037 0014200 0 ustar 00root root 0000000 0000000 $Id$
Vidalia Coding and Repository Specification
0. Introduction
This document is intended to loosely specify coding conventions followed in
Vidalia code, as well as conventions used in Vidalia's Subversion
repository.
1. Repository Organization
1.1. Subversion Location
Vidalia's repository supports anonymous checkout. You can grab the most
recent revision of Vidalia's source code via:
svn co https://svn.vidalia-project.net/svn/vidalia/trunk/ vidalia
1.2 Directory Layout
The following are the current directories found in Vidalia's SVN repository
and a general decription of their intended contents:
From https://svn.vidalia-project.net/svn/vidalia:
./tags:
Snapshots of all Vidalia releases will be contained in a sub-directory
of ./tags, named according to the Vidalia version specification.
For example, ./tags/vidalia-0.0.1/ would contain the 0.0.1 release of
Vidalia.
./trunk:
Contains the main branch of Vidalia's source code.
./trunk/doc:
Contains Vidalia's documentation, such as specifications and todo
lists.
./trunk/src:
All Vidalia source code will be contained under this directory.
./trunk/src/torcontrol:
Code in this directory implements Tor's control protocol. It also
handles things such as starting and stopping Tor and checking the
status of the Tor process.
./trunk/src/vidalia:
This directory contains code that implements the GUI components of
Vidalia. Whenever possible and sane, each component should be placed in
an appropriately-named subdirectory of ./trunk/src/vidalia.
./trunk/src/vidalia/res:
All GUI-related resource files, such as images, should go in this
directory. Images should be placed in sub-directories appropriate for
their image size. For example, 16x16 images would go in
./trunk/src/vidalia/res/16x16/
./trunk/src/common:
If a source file doesn't belong in the previous directories, it should
go here. This directory will containg various utility functions, such
as date or time parsing, custom string manipulation functions, etc. If
a particular utility has multiple source files, they should all be
placed in a subdirectory. For example, if there were several source
files that implemented various string manipulation functions, they
could go in ./trunk/src/common/string.
2. Coding Conventions
This section aims to provide a small overview of coding conventions used in
Vidalia, to keep the look of the code consistent between developers and
contributors. Since it would be impossible to specify all aspects of coding
here, common sense should be employed for things not specified below.
2.1. Naming Conventions
2.1.1. Source File Names
C++ classes should be divided in to a .h file, containing the
class declarations, and a .cpp file containg the class
implementation. Each .cpp file should implement only one public class.
Filenames containing a class should follow the same "CamelCase"
capitalization format as the class name itself.
Source files that do not implement a C++ class should be named logically and
in all lowercase letters. For example, threading-related code would go in
thread.cpp and thread.h.
2.1.2. Class Names
Class names should begin with a capital letter. If a name is a combination
of distinct words, each word should be capitalized. The purpose of the class
should be explained in Doxygen tags. Example:
/** A brief description of MyClass. */
/**
* Alternatively, here is a more detailed description of MyClass.
*/
class MyClass
{
};
Doxygen-style comments should be used above each method declaration in
the class.
2.1.3. Method Names
Method names should begin with a lower case letter. If a method name is a
combination of distinct words, each word should be capitalized. Methods
should have descriptions of their purpose. Example:
/* Description of what someMethod does. */
int
MyClass::someMethod(int foo)
{
}
Doxygen tags should be used for comments above the method definition
ONLY if the method's declaration in the class header file does not
already have a Doxygen-style comments.
Note that the method's return type is declared on a line by itself. Private
member function should NOT have an underscore prepended to their name.
2.1.4. Variable Names
Variable names should follow a convention similar to method names. Variable
names should be descriptive if their purpose is non-obvious.
Variables that are members of a class should have a leading underscore to
distinguish them from local variables in a method. Member variables should
also have a description of their purpose in Doxygen tags. For example:
/** A brief description of MyClass */
/**
* A more detailed description of MyClass.
*/
class MyClass
{
private:
int _myVariable; /**< Description of what _myVariable is */
};
2.1.5. Ordering of Method and Member Variable Declarations
Class member method and variable declarations should be arranged according
to decreasing order of visibility.
class MyClass : public QObject
{
Q_OBJECT
public:
/* Public enums */
/* Public methods */
public slots:
/* Public slots */
signals:
/* Signals emitted by this class */
protected:
/* Protected methods */
/* Protected member variables */
protected slots:
/* Protected slots */
private:
/* Private methods */
/* Private member variables */
private slots:
/* Private slots */
};
2.1.6. Widget Names
Every widget declared in a Qt Designer .ui file must have a short three or
four letter prefix that describes the widget's type.
Widget Type Prefix Example
------------------------------------------------------------
QCheckBox chk chkEnableFoo
QComboBox cmbo cmboNames
QDialogButtonBox - buttonBox
QFrame frm frmMain
QGroupBox grp grpAdvanced
QLabel lbl lblHeader
QLineEdit line lineAddress
QListView lst lstMessages
QProgressBar pbar pbarDownload
- progressBar
QPushButton btn btnClose
QRadioButton rdo rdoSomeOption
QSpinBox spn spnDial
QTableView tbl tblSpreadsheet
QTabWidget tab tabServerOptions
QToolButton btn btnExit
QTreeView tree treeFolders
2.2. Comments
Comments should be standard C style comments. For example:
int fooCounter; /* Comment about counting foo */
Multi-line comments should be formatted as:
/*
* This section of code is potentially confusing or ambiguous, so here is a
* long comment that takes up multiple lines.
*/
2.3. Indentation
All source code should follow these conventions:
1. Tabs should be 2 characters wide.
2. Your editor should be set to replace tabs with spaces.
3. Lines should be less than 80 characters wide whenever possible.
2.4. Bracing
2.4.1. Methods
Opening and closing braces for functions should be placed at column 1. For
example:
void
Foo::bar(void)
{
}
2.4.2. Loops
Braces for loops should be formatted as follows:
for (i = 0; i < 10; i++) {
/* Do something ten times */
}
2.4.3. if-else Statements
The `else' portion of an if-else statement, if present, should begin on the
same line as the closing brace of the `if' portion.
if (foo == bar) {
/* Do something */
} else {
/* My foo doesn't equal bar */
}
Braces may be omitted if there is only one line of code to be executed if
the evaluated condition is true. For example, the following is permitted:
if (foo == bar)
return;
2.5. Parentheses
There should NOT be a space between an opening parenthesis and the
first argument, nor between the end of the last argument and a closing
parenthesis.
int value = someObject.someMethod(foo, bar, baz);
2.6. Method Arguments
const-correctness should be enforced whenever possible. Objects passed as
arguments to a method should be passed by a const reference, as in the
following example:
void
SomeClass::someMethod(const OtherClass &oc)
{
/* Do something with oc */
}
2.7. Other
Source files should end with a single blank line.
vidalia-0.2.21/INSTALL 0000664 0000000 0000000 00000021700 12056211037 0014233 0 ustar 00root root 0000000 0000000
Instructions for Building and Installing Vidalia from Source
Before building and running Vidalia, you will need to have the following
packages installed:
* Qt >= 4.3 http://qt.nokia.com/downloads
* Tor >= 0.2.0.34 https://www.torproject.org/download.html
* CMake >= 2.4.0 http://www.cmake.org/HTML/Download.html
Linux/BSD/Unix
--------------
1. To configure and compile Vidalia, you can run the following sequence of
commands:
mkdir build && cd build
cmake ..
make
2. When the previous command finishes, Vidalia's binary will be
placed in the build/src/vidalia/ directory.
3. Optionally, you can run `make install` to install Vidalia into
your /usr/local/bin/ directory.
Mac OS X
--------
CMake on Mac OS X gives you the option of compiling Vidalia from the command
line using standard Unix Makefiles, or generating an Xcode project if you
prefer building from an IDE.
1. To build Vidalia from the command line, you can run:
mkdir build && cd build
cmake ..
make
Alternatively, you can have CMake generate an Xcode project for Vidalia
by running:
mkdir xcode && cd xcode
cmake -G Xcode ..
2. If you built from the command line, Vidalia's binary will be in an
application bundle located at build/src/vidalia/Vidalia.app. You can copy
Vidalia.app to your Applications folder, if you prefer.
If you're building from a CMake-generated Xcode project, you can simply
click "Build & Go" in Xcode to build and run Vidalia. Or, you can run
'xcodebuild' if you prefer building from the command line.
Windows with MinGW
-------------------
1. Make sure the following directories are in your PATH environment
variable:
* CMake (e.g., "C:\Program Files\CMake 2.4\bin")
* MinGW (e.g., "C:\MinGW\bin")
* Qt (e.g., "C:\Qt\4.3.2\bin")
2. Configure Vidalia and generate Makefiles by running:
mkdir build && cd build
cmake -G "MinGW Makefiles" ..
There should be no spaces in the path to your build directory. Otherwise,
Vidalia will fail to build.
3. Compile Vidalia by running:
mingw32-make
If CMake fails to find your Qt installation, you can explicitly tell CMake
where to find Qt as in the following example:
cmake -DQT_QMAKE_EXECUTABLE="C:\Qt\4.3.2\bin\qmake.exe" ..
You would replace "C:\Qt\4.3.2\bin" in the previous command with the actual
path to your Qt installation's qmake.exe binary.
If you are trying to build Vidalia for Windows 2000 and earlier, you should
download Windows SDK, copy wspiapi.h header to MinGW include directory and
build vidalia running:
cmake -DWIN2K ..
Note: the header as it is in the SDK needs a "_inline" to be replaced to
"__inline" for it to build properly.
Windows with Visual Studio
--------------------------
Starting with Qt 4.3.2, the open source editions of Qt/Win include support for
Visual Studio. Previously, Visual Studio support was limited to commercial
editions of Qt unless you patched Qt's source.
To build Vidalia under Visual Studio, you will first need to obtain Qt's
source code and compile it with Visual Studio support. The following
directions show how to compile Qt with Visual Studio 2005 support, but a
similar process can be followed for other versions of VS.
1. Download and install Visual C++ 2005 Express
http://www.microsoft.com/express/2005/download/default.aspx
2. Download and install the Windows Platform SDK and configure Visual C++ with
the location of the Platform SDK's executable, include, and library
directories.
http://msdn2.microsoft.com/en-us/express/aa700755.aspx
It is important to also install the "Microsoft Web Workshop (IE) SDK", even
though that seems irrelevant.
3. Download the Qt/Windows open source edition source code and extract it to a
directory with no spaces (e.g., C:\Qt\4.3.3).
http://qt.nokia.com/downloads/windows-cpp
4. Edit the Visual Studio 2005 command prompt environment variables to
include the platform SDK files, by opening
C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars32.bat
and adding
C:\Program Files\Microsoft Platform SDK for Windows Servers 2003 R2\Include
to the INCLUDE variable and
C:\Program Files\Microsoft Platform SDK for Windows Servers 2003 R2\Lib
to the LIB variable. Modify the path to the platform SDK files as
appropriate, depending on where you installed Visual Studio and the
Platform SDK in Steps 1 and 2.
5. Open the Visual Studio 2005 Command Prompt and 'cd' to the location of
your extracted Qt source code (e.g., C:\Qt\4.3.3).
6. Configure Qt with support for your version of Visual Studio. For example,
to configure Qt with support for Visual Studio 2005, you would run:
configure.exe -debug-and-release -static -fast -platform win32-msvc2005
See Qt's README file for more available platform options.
7. Compile Qt by running:
nmake.exe
(NOTE: This step will take several hours and lots of hard drive space.)
Once you have Qt compiled with Visual Studio support, you can use CMake to
generate a Visual Studio project file by running
mkdir build && cd build
cmake -G "Visual Studio 8 2005" ..
or whatever your particular version of Visual Studio happens to be.
'cmake --help' lists other available generators.
Windows with NMake
-------------------
To compile Vidalia from the command line using NMake, you will first need to
follow the steps under the 'Windows with Visual Studio' section for compiling
Qt with Visual Studio support.
If you want to build Vidalia from the command line, you can have CMake
generate NMake makefiles by running:
mkdir build && cd build
cmake -G "NMake Makefiles" ..
You can then compile Vidalia from the command line by simply running:
nmake
Available Configuration Options
-------------------------------
You can customize your Vidalia build by supplying arguments and values to the
`cmake` commands above. Each of the configuration options can be specified on
the command line and follows the format "-D :=
-DUSE_MINIUPNPC=0
Disable UPnP support in Vidalia.
-DOSX_FAT_BINARY=1
Build Vidalia as a Universal binary.
-DOSX_TIGER_COMPAT=1
Build Vidalia compatible with OS X Tiger (10.4).
-DOSX_FORCE_32BIT=1
Forces a 32-bit build. This is useful on platforms that default to 64-bit
(e.g. Snow Leopard), but only have 32-bit versions of the Qt libraries
available.
-DQT_QMAKE_EXECUTABLE=/path/to/qmake
Specifies the location of Qt's 'qmake' binary.
-DCMAKE_INSTALL_PREFIX=/usr/local
Specifies the install prefix used for `make install`.
-DCMAKE_BUILD_TYPE=
Available build types include: "release", "debug", "minsizerel"
-DUSE_MARBLE=1
Replace the flat map with a 3-D sphere using the Marble libraries.
-DWIX_BINARY_DIR=C:\Path\To\WiX\
Specifies the location of your WiX executables, such as candle.exe and
light.exe (optional, Windows-only).
-DWIN2K
Builds Vidalia using the inlines defined in wspiapi.h header for Windows
2000 and earlier support.
For example, to configure CMake to look for Qt in "/usr/local/Qt-4.3.2/bin",
you would run:
cmake -DQT_QMAKE_EXECUTABLE=/usr/local/Qt-4.3.2/bin/qmake ..
Don't forget the dot(s) at the end!
CMake also supports other generators besides Makefiles on certain platforms.
See 'cmake --help' or 'man cmake' (on non-Windows platforms) for more
information about supported generators and configuration options.
Additional Build Targets
-------------------------
Vidalia contains a number of additional CMake build targets to assist in
building code documentation and platform-specific packages. The targets are:
'dist' Creates a Vidalia source code tarball.
'dist-osx' Creates a Vidalia-only Mac OS X .dmg.
'dist-osx-bundle' Creates a Vidalia bundle .dmg. See
pkg/osx/build-bundle.txt for additional
information on the CMake options necessary to create
a proper OS X bundle.
'dist-osx-split-bundle' Creates a "split" Mac OS X bundle. See
pkg/osx/build-bundle.txt for additional
information on the CMake options necessary to create
a proper OS X bundle.
'dist-win32' Creates a Windows .msi package. You will also
need to define -DWIX_BINARY_DIR=
in order to use this build target.
'doxygen' Creates the Doxygen-generated code
documentation for Vidalia's source. You must
have Doxygen installed for this target to
function.
vidalia-0.2.21/LICENSE 0000664 0000000 0000000 00000030065 12056211037 0014213 0 ustar 00root root 0000000 0000000 =======
LICENSE
=======
Copyright (c) 2006-2010, Matt Edman, Justin Hipple
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License (GPL) as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version. The full text of versions 2 and 3 of
the GPL can be found respectively in the files LICENSE-GPLV2 and
LICENSE-GPLV3.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
===================================================================
Vidalia incorporates icons from KDE's Oxygen icon theme. It is
licensed as follows:
Copyright (C) 2007 David Vignoni
Copyright (C) 2007 Johann Ollivier Lapeyre
Copyright (C) 2007 Kenneth Wimer
Copyright (C) 2007 Nuno Fernades Pinheiro
Copyright (C) 2007 Riccardo Iaconelli
Copyright (C) 2007 David Miller
and others
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
License as published by the Free Software Foundation; either
version 3 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Library General Public License for more details.
You should have received a copy of the GNU Library General Public
License along with this library. If not, see .
===================================================================
Tor is distributed under this license:
Copyright (c) 2001-2004, Roger Dingledine
Copyright (c) 2004-2007, Roger Dingledine, Nick Mathewson
Copyright (c) 2007-2009, The Tor Project, Inc.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.
* Neither the names of the copyright owners nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
src/common/strlcat.c and src/common/strlcpy.c by Todd C. Miller are licensed
under the following license:
* Copyright (c) 1998 Todd C. Miller
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. The name of the author may not be used to endorse or promote products
* derived from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
* INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
* AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
* THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
* OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
* OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
* ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
If you got Tor as a static binary with OpenSSL included, then you should know:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)"
===============================================================================
The function append_string() in Vidalia's src/vidalia/CrashReporter.cpp is
also derived from the strlcat() implementation by Todd C. Miller. It is
licensed under the following license:
* Copyright (c) 1998 Todd C. Miller
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. The name of the author may not be used to endorse or promote products
* derived from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
* INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
* AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
* THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
* OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
* OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
* ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
===============================================================================
Some of the help documentation text used in Vidalia is derived from the TorFAQ
Wiki . It is licensed
under the MIT license as follows:
Copyright (c) 2003-2007 Roger Dingledine
Copyright (c) 2004-2005 Nick Mathewson
Copyright (c) 2004 Douglas F. Calvert
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
===============================================================================
This product includes GeoIP data created by MaxMind, available from
http://maxmind.com. It is licensed as follows:
OPEN DATA LICENSE (GeoLite Country and GeoLite City databases)
Copyright (c) 2007 MaxMind LLC. All Rights Reserved.
All advertising materials and documentation mentioning features or use of
this database must display the following acknowledgment:
"This product includes GeoLite data created by MaxMind, available from
http://maxmind.com/"
Redistribution and use with or without modification, are permitted provided
that the following conditions are met:
1. Redistributions must retain the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
2. All advertising materials and documentation mentioning features or use of
this database must display the following acknowledgement:
"This product includes GeoLite data created by MaxMind, available from
http://maxmind.com/"
3. "MaxMind" may not be used to endorse or promote products derived from this
database without specific prior written permission.
THIS DATABASE IS PROVIDED BY MAXMIND.COM ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL MAXMIND.COM BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
DATABASE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
===============================================================================
Vidalia uses the MiniUPnPc library for UPnP support. It is licensed as
follows:
Copyright (c) 2005-2007, Thomas BERNARD
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials
provided with the distribution.
* Neither the names of the copyright owners nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
vidalia-0.2.21/LICENSE-GPLV2 0000664 0000000 0000000 00000043133 12056211037 0015043 0 ustar 00root root 0000000 0000000 GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
Copyright (C)
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
vidalia-0.2.21/LICENSE-GPLV3 0000664 0000000 0000000 00000104513 12056211037 0015044 0 ustar 00root root 0000000 0000000 GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
Copyright (C)
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
Copyright (C)
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
.
vidalia-0.2.21/LICENSE-LGPLV3 0000664 0000000 0000000 00000016727 12056211037 0015171 0 ustar 00root root 0000000 0000000 GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein, "this License" refers to version 3 of the GNU Lesser
General Public License, and the "GNU GPL" refers to version 3 of the GNU
General Public License.
"The Library" refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.
An "Application" is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode
of using an interface provided by the Library.
A "Combined Work" is a work produced by combining or linking an
Application with the Library. The particular version of the Library
with which the Combined Work was made is also called the "Linked
Version".
The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.
The "Corresponding Application Code" for a Combined Work means the
object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License
without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a
facility refers to a function or data to be supplied by an Application
that uses the facility (other than as an argument passed when the
facility is invoked), then you may convey a copy of the modified
version:
a) under this License, provided that you make a good faith effort to
ensure that, in the event an Application does not supply the
function or data, the facility still operates, and performs
whatever part of its purpose remains meaningful, or
b) under the GNU GPL, with none of the additional permissions of
this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from
a header file that is part of the Library. You may convey such object
code under terms of your choice, provided that, if the incorporated
material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following:
a) Give prominent notice with each copy of the object code that the
Library is used in it and that the Library and its use are
covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this license
document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that,
taken together, effectively do not restrict modification of the
portions of the Library contained in the Combined Work and reverse
engineering for debugging such modifications, if you also do each of
the following:
a) Give prominent notice with each copy of the Combined Work that
the Library is used in it and that the Library and its use are
covered by this License.
b) Accompany the Combined Work with a copy of the GNU GPL and this license
document.
c) For a Combined Work that displays copyright notices during
execution, include the copyright notice for the Library among
these notices, as well as a reference directing the user to the
copies of the GNU GPL and this license document.
d) Do one of the following:
0) Convey the Minimal Corresponding Source under the terms of this
License, and the Corresponding Application Code in a form
suitable for, and under terms that permit, the user to
recombine or relink the Application with a modified version of
the Linked Version to produce a modified Combined Work, in the
manner specified by section 6 of the GNU GPL for conveying
Corresponding Source.
1) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (a) uses at run time
a copy of the Library already present on the user's computer
system, and (b) will operate properly with a modified version
of the Library that is interface-compatible with the Linked
Version.
e) Provide Installation Information, but only if you would otherwise
be required to provide such information under section 6 of the
GNU GPL, and only to the extent that such information is
necessary to install and execute a modified version of the
Combined Work produced by recombining or relinking the
Application with a modified version of the Linked Version. (If
you use option 4d0, the Installation Information must accompany
the Minimal Corresponding Source and Corresponding Application
Code. If you use option 4d1, you must provide the Installation
Information in the manner specified by section 6 of the GNU GPL
for conveying Corresponding Source.)
5. Combined Libraries.
You may place library facilities that are a work based on the
Library side by side in a single library together with other library
facilities that are not Applications and are not covered by this
License, and convey such a combined library under terms of your
choice, if you do both of the following:
a) Accompany the combined library with a copy of the same work based
on the Library, uncombined with any other library facilities,
conveyed under the terms of this License.
b) Give prominent notice with the combined library that part of it
is a work based on the Library, and explaining where to find the
accompanying uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions
of the GNU Lesser General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the
Library as you received it specifies that a certain numbered version
of the GNU Lesser General Public License "or any later version"
applies to it, you have the option of following the terms and
conditions either of that published version or of any later version
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the
Library.
vidalia-0.2.21/README 0000664 0000000 0000000 00000001547 12056211037 0014071 0 ustar 00root root 0000000 0000000 ================================
Overview
================================
Vidalia is a cross-platform controller GUI for Tor, built using the Qt
framework. Using Vidalia, you can start and stop Tor, view the status of Tor
at a glance, and monitor Tor's bandwidth usage. Vidalia also makes it easy to
contribute to the Tor network by helping you set up and manage your own Tor
server.
Vidalia runs on most platforms supported by Qt 4.3 or later, including
Windows, Mac OS X, and Linux or other Unix variants using the X11 window
system.
Vidalia is written by Matt Edman and Justin Hipple.
See the LICENSE file for licensing information.
================================
Installation (Mac OS X)
================================
Installation is simple. Drag the Vidalia icon to Applications.
In Finder, browse to Applications and then double-click the Vidalia
icon.
vidalia-0.2.21/README.breakpad 0000664 0000000 0000000 00000010047 12056211037 0015634 0 ustar 00root root 0000000 0000000
Building Vidalia with Breakpad-based Crash Reporting Support
Windows
--------
Pre-requisites:
* Subversion
* CMake 2.4 or later (CMake >= 2.6 preferred)
* Microsoft Visual C++ Professional 2005 or later (VC++ >= 2008 preferred)
NOTE: Google Breakpad requires Microsoft's ATL, so users of Visual Studio
"Express" editions may need to install that separately (if even
supported).
1. Download and build Qt with Visual Studio support
1.1. Download the latest Qt source code for Windows from Qt's website:
http://get.qtsoftware.com/qt/source/
1.2. Extract the .zip file to a directory
1.3. Open a Visual Studio command prompt
1.4. 'cd' to the location of your extract Qt source
1.5. We want to enable building .pdb files for the release versions of the
Qt DLLs, since Breakpad derives its symbol information from the .pdb
files. To do so, unfortunately we have to edit the qmake.conf "mkspec"
for the compiler we're using. For example, if you're using Visual
Studio 2008, you would open the file
$QTDIR\mkspecs\win32-msvc2008\qmake.conf
(where $QTDIR is the location of your Qt source code) and add "-Zi" to
QMAKE_CFLAGS_RELEASE. The resulting line would look like:
QMAKE_CFLAGS_RELEASE = -Zi -O2 -MD -GL
You also need to add "/DEBUG /OPT:REF /OPT:ICF" to the list of linker
flags in QMAKE_LFLAGS_RELEASE. The resulting line should look like the
following:
QMAKE_LFLAGS_RELEASE = /DEBUG /OPT:REF /OPT:ICF /INCREMENTAL:NO /LTCG
Different Visual Studio mkspecs may look slightly different and have
different sets of default flags. Save your changes to qmake.conf after
you're done.
1.6. Configure the Qt source for a Visual Studio build, along with whatever
other options you want (e.g., OpenSSL support). As an example, I used
the following command to configure my Qt:
$ configure.exe -platform win32-msvc2008 \
-opensource -debug-and-release \
-fast -no-qt3support \
-nomake demos -nomake examples \
-openssl -I E:\OpenSSL\9.8k\include \
-L E:\OpenSSL\9.8k\lib\VC
1.7. After configure.exe is finished running, simply run nmake.exe to build
Qt. The entire process may take several hours depending on the options
used and the speed of your machine.
2. Download and build the latest Breakpad source from Subversion
2.1. Fetch the latest Google Breakpad source code from Subversion
$ svn cp http://google-breakpad.googlecode.com/svn/trunk/ breakpad
2.2. Open breakpad\src\client\windows\breakpad_client.sln
2.3. Right-click on the "crash_generation" project and select 'Properties'
2.4. Go to "Configuration Properties" -> "C/C++" -> "Language" and disable
"Treat wchar_t as Built-in Type".
2.5. Repeat 2.2 and 2.3 for the "crash_report_sender" and "exception_handler"
projects as well.
2.6. Right-click on the top-level solution and select "Build Solution" or
hit F7 to build the entire solution.
3. Build Vidalia with Breakpad support enabled
3.1. Fetch the latest 'breakpad' branch from Vidalia's Subversion repository.
$ svn co https://svn.vidalia-project.net/svn/vidalia/branches/breakpad vidalia-breakpad
3.2. Use CMake to generate a Visual Studio .sln file for Vidalia with
Breakpad support enabled.
$ mkdir build-vs
$ cd build-vs
$ cmake.exe -DUSE_BREAKPAD=1 \
-DBREAKPAD_INCLUDE_DIR=E:\breakpad\src \
-DBREAKPAD_LIBRARY_DIR=E:\Breakpad\src\client\windows\Debug ..
You will need to adjust the paths above to point to the location of
the Breakpad source directory and binaries you built in Step 2.
3.3. Open the solution file build-vs\Vidalia.sln with Visual Studio.
3.4. Right-click on the top-level solution and select "Build Solution", or
hit F7 to build the entire solution.
vidalia-0.2.21/README.geoip 0000664 0000000 0000000 00000003556 12056211037 0015175 0 ustar 00root root 0000000 0000000
Building Vidalia with MaxMind GeoIP Support
-------------------------------------------
Vidalia now contains support for using a local city- or country-level
database from MaxMind.
http://www.maxmind.com/app/ip-location
The following steps build Vidalia with MaxMind GeoIP support.
1. Install the MaxMind GeoIP C library. If your operating system does not
provide packages for the library (typically called libGeoIP or similar),
then you can download, build and install the latest version from here:
http://www.maxmind.com/app/c
2. Configure Vidalia with GeoIP support.
cd vidalia (or wherever your Vidalia source tree lives)
mkdir build && cd build
cmake -DUSE_GEOIP=1 \
-DGEOIP_INCLUDE_DIR= \
-DGEOIP_LIBRARY_DIR= ..
Here is an example of what the previous command might look like, if you
don't have the MaxMind GeoIP library installed somewhere in the normal
search path:
cmake -DUSE_GEOIP=1 \
-DGEOIP_INCLUDE_DIR=/home/someuser/GeoIP-1.4.6/libGeoIP/ \
-DGEOIP_LIBRARY_DIR=/home/someuser/GeoIP-1.4.6/libGeoIP/
If the GeoIP library and headers are in the normal locations on OS X and
Linux (e.g., /usr/local/lib and /usr/local/include), you can most likely
omit -DGEOIP_INCLUDE_DIR and -DGEOIP_LIBRARY_DIR from the command above.
3. Build Vidalia
See the INSTALL file included with Vidalia for details.
4. Edit your Vidalia.conf to enable using a local database via the
UseLocalGeoIpDatabase and LocalGeoIpDatabase options. For example:
[General]
UseLocalGeoIpDatabase=true
LocalGeoIpDatabase=/home/someuser/Library/Vidalia/GeoLiteCity.dat
You can then start or restart Vidalia to pick up your changes and start
using a local GeoIP database. See this URL for the latest binary version
of MaxMind's city-level GeoIP database:
http://www.maxmind.com/app/geolitecity
vidalia-0.2.21/README.marble 0000664 0000000 0000000 00000004004 12056211037 0015321 0 ustar 00root root 0000000 0000000
Building Vidalia with KDE Marble Support
----------------------------------------
Vidalia recently added experimental support for replacing the existing 2D
network map widget with the KDE Marble 3D globe widget. It is currently a
compile-time option and is disabled by default.
The following steps build Vidalia with the Marble widget.
1. Download the patched version of Marble.
svn co https://svn.vidalia-project.net/svn/marble/trunk marble
Hopefully these patches will soon be merged into Marble's trunk. For now, we
still have to build with the Vidalia-specific patched Marble.
2. Build the patched Marble.
OS X:
cd ~/marble
mkdir build && cd build
cmake -DCMAKE_INSTALL_PREFIX=. -DQTONLY=1 ..
make && make install
If you are building a Universal binary, you will need to make the following
changes to ~/marble/CMakeLists.txt before building Marble:
- #SET( CMAKE_OSX_ARCHITECTURES ppc;i386 ) #Comment out if not universal binary
- SET( CMAKE_OSX_ARCHITECTURES i386 ) #Comment out if universal binary
+ SET( CMAKE_OSX_ARCHITECTURES ppc;i386 ) #Comment out if not universal binary
+ #SET( CMAKE_OSX_ARCHITECTURES i386 ) #Comment out if universal binary
Everywhere else:
cd marble
mkdir build && cd build
cmake -DQTONLY=1 ..
make && make install
3. Configure Vidalia with Marble support.
OS X & Windows:
cd vidalia (or wherever your Vidalia source tree lives)
mkdir build && cd build
cmake -DUSE_MARBLE=1 \
-DMARBLE_INCLUDE_DIR=~/marble/src/lib \
-DMARBLE_DATA_DIR=~/marble/data \
-DMARBLE_LIBRARY_DIR=~/marble/build/src/lib \
-DMARBLE_PLUGIN_DIR=~/marble/build/src/plugins ..
Everywhere else:
cd vidalia (or wherever your Vidalia source tree lives)
mkdir build && cd build
cmake -DUSE_MARBLE=1 ..
You will need to adjust each of the paths above according to where you checked
out and installed Marble in Steps 1 and 2.
4. Build Vidalia
See the INSTALL file included with Vidalia for details.
vidalia-0.2.21/cmake/ 0000775 0000000 0000000 00000000000 12056211037 0014262 5 ustar 00root root 0000000 0000000 vidalia-0.2.21/cmake/FindBreakpad.cmake 0000664 0000000 0000000 00000003203 12056211037 0017574 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
## Tries to find the required Google Breakpad libraries. Once done this will
## define the variable BREAKPAD_LIBRARIES.
message(STATUS "Looking for Google Breakpad libraries")
if (WIN32)
if (MSVC)
find_library(BREAKPAD_EXCEPTION_HANDLER_LIB
NAMES exception_handler
PATHS ${BREAKPAD_LIBRARY_DIR}
)
if (NOT BREAKPAD_EXCEPTION_HANDLER_LIB)
message(FATAL_ERROR
"Could not find Breakpad exception handler library")
endif(NOT BREAKPAD_EXCEPTION_HANDLER_LIB)
find_library(BREAKPAD_CRASH_GENERATION_LIB
NAMES crash_generation
PATHS ${BREAKPAD_LIBRARY_DIR}
)
if (NOT BREAKPAD_CRASH_GENERATION_LIB)
message(FATAL_ERROR
"Could not find Breakpad crash generation library")
endif(NOT BREAKPAD_CRASH_GENERATION_LIB)
set(BREAKPAD_LIBRARIES
${BREAKPAD_EXCEPTION_HANDLER_LIB}
${BREAKPAD_CRASH_GENERATION_LIB}
)
message(STATUS "Looking for Google Breakpad libraries - found")
else(MSVC)
message(FATAL_ERROR
"Breakpad support on Windows currently requires Visual Studio.")
endif(MSVC)
endif(WIN32)
vidalia-0.2.21/cmake/FindGeoIP.cmake 0000664 0000000 0000000 00000003110 12056211037 0017023 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
## Tries to find the required MaxMind GeoIPlibraries. Once done this will
## define the variable GEOIP_LIBRARIES.
message(STATUS "Looking for MaxMind GeoIP header files")
set(CMAKE_INCLUDE_PATH "${CMAKE_INCLUDE_PATH} ${GEOIP_INCLUDE_DIR}")
check_include_file("GeoIP.h" HAVE_GEOIP_H)
check_include_file("GeoIPCity.h" HAVE_GEOIPCITY_H)
if (HAVE_GEOIP_H AND HAVE_GEOIPCITY_H)
message(STATUS "Looking for MaxMind GeoIP header files - found")
else(HAVE_GEOIP_H AND HAVE_GEOIPCITY_H)
message(FATAL_ERROR "Could not find one or more MaxMind GeoIP header files. If the MaxMind GeoIP library is installed, you can run CMake again and specify its location with -DGEOIP_INCLUDE_DIR=")
endif(HAVE_GEOIP_H AND HAVE_GEOIPCITY_H)
message(STATUS "Looking for MaxMind GeoIP libraries")
find_library(GEOIP_LIB
NAMES GeoIP geoip
PATHS ${GEOIP_LIBRARY_DIR}
)
if (GEOIP_LIB)
message(STATUS "Looking for MaxMind GeoIP libraries - found")
set(GEOIP_LIBRARIES ${GEOIP_LIB})
else(GEOIP_LIB)
message(FATAL_ERROR "Could not find MaxMind GeoIP library")
endif(GEOIP_LIB)
vidalia-0.2.21/cmake/FindMarble.cmake 0000664 0000000 0000000 00000011011 12056211037 0017261 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
## This file incorporates work from the KDE Marble project, and is covered by
## the following copyright and permission notice:
##
## Redistribution and use in source and binary forms, with or without
## modification, are permitted provided that the following conditions are
## met:
##
## * Redistributions of source code must retain the above copyright notice,
## this list of conditions and the following disclaimer.
##
## * Redistributions in binary form must reproduce the above copyright
## notice, this list of conditions and the following disclaimer in the
## documentation and/or other materials provided with the distribution.
##
## * Neither the names of the copyright owners nor the names of its
## contributors may be used to endorse or promote products derived from
## this software without specific prior written permission.
##
## THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
## IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
## THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
## PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
## CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
## EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
## PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
## PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
## LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
## NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
## SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
##
message(STATUS "Looking for Marble header files")
find_path(MARBLE_INCLUDE_DIR
NAMES MarbleWidget.h
PATH_SUFFIXES marble
)
if (MARBLE_INCLUDE_DIR)
message(STATUS "Looking for Marble header files - found")
else(MARBLE_INCLUDE_DIR)
message(FATAL_ERROR "Could not find Marble header files. If Marble is installed, you can run CMake again and specify its location with -DMARBLE_INCLUDE_DIR=")
endif(MARBLE_INCLUDE_DIR)
message(STATUS "Looking for Marble libraries")
find_library(MARBLEWIDGET_LIBRARY
NAMES marblewidget.7 marblewidget
PATHS ${MARBLE_LIBRARY_DIR}
)
if (MARBLEWIDGET_LIBRARY)
message(STATUS "Looking for Marble libraries - found")
set(MARBLE_LIBRARIES ${MARBLEWIDGET_LIBRARY})
get_filename_component(MARBLE_LIBRARY_DIR ${MARBLEWIDGET_LIBRARY} PATH)
else(MARBLEWIDGET_LIBRARY)
message(FATAL_ERROR "Could not find Marble libraries. If Marble is installed, you can run CMake again and specify its location with -DMARBLE_LIBRARY_DIR=")
endif(MARBLEWIDGET_LIBRARY)
if (APPLE OR WIN32)
message(STATUS "Looking for Marble data files")
find_path(MARBLE_DATA_DIR
NAMES srtm.dgml
PATH_SUFFIXES maps/earth/srtm
)
if (MARBLE_DATA_DIR)
message(STATUS "Looking for Marble data files - ${MARBLE_DATA_DIR}")
else (MARBLE_DATA_DIR)
message(FATAL_ERROR "Could not find Marble libraries. If Marble is installed, you can run CMake again and specify its location with -DMARBLE_DATA_DIR=")
endif(MARBLE_DATA_DIR)
message(STATUS "Looking for Marble plugin widgets")
find_library(MARBLE_OVERVIEWMAP_PLUGIN
NAMES MarbleOverviewMap
PATHS ${MARBLE_PLUGIN_DIR}
PATH_SUFFIXES render/overviewmap
)
if (MARBLE_OVERVIEWMAP_PLUGIN)
message(STATUS "Looking for Marble plugin widgets - found overview map plugin")
set(MARBLE_PLUGINS ${MARBLE_PLUGINS}
${MARBLE_OVERVIEWMAP_PLUGIN}
)
endif(MARBLE_OVERVIEWMAP_PLUGIN)
find_library(MARBLE_STARS_PLUGIN
NAMES MarbleStarsPlugin
PATHS ${MARBLE_PLUGIN_DIR}
PATH_SUFFIXES render/stars
)
if (MARBLE_STARS_PLUGIN)
message(STATUS "Looking for Marble plugin widgets - found stars plugin")
set(MARBLE_PLUGINS ${MARBLE_PLUGINS}
${MARBLE_STARS_PLUGIN}
)
endif(MARBLE_STARS_PLUGIN)
if (NOT MARBLE_PLUGINS)
message(STATUS "Looking for Marble plugin widgets - none found")
endif(NOT MARBLE_PLUGINS)
endif(APPLE OR WIN32)
vidalia-0.2.21/cmake/FindWiX.cmake 0000664 0000000 0000000 00000002454 12056211037 0016601 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
message(STATUS "Looking for WiX")
## Search for candle.exe
find_program(WIX_CANDLE_EXECUTABLE NAMES candle
PATHS ${WIX_BINARY_DIR}
)
## Search for light.exe
find_program(WIX_LIGHT_EXECUTABLE NAMES light
PATHS ${WIX_BINARY_DIR}
)
if (WIX_CANDLE_EXECUTABLE AND WIX_LIGHT_EXECUTABLE)
message(STATUS "Looking for WiX - found")
## Set the WiX binary directory variable, but only if it wasn't already
## explicitly defined
if (NOT WIX_BINARY_DIR)
get_filename_component(WIX_BINARY_DIR ${WIX_LIGHT_EXECUTABLE} ABSOLUTE)
get_filename_component(WIX_BINARY_DIR ${WIX_BINARY_DIR} PATH)
endif(NOT WIX_BINARY_DIR)
else (WIX_CANDLE_EXECUTABLE AND WIX_LIGHT_EXECUTABLE)
message(STATUS "Looking for WiX - not found.")
endif(WIX_CANDLE_EXECUTABLE AND WIX_LIGHT_EXECUTABLE)
vidalia-0.2.21/cmake/ParseArgumentsMacro.cmake 0000664 0000000 0000000 00000002171 12056211037 0021207 0 ustar 00root root 0000000 0000000 ##
## From http://www.cmake.org/Wiki/CMakeMacroParseArguments
##
MACRO(PARSE_ARGUMENTS prefix arg_names option_names)
SET(DEFAULT_ARGS)
FOREACH(arg_name ${arg_names})
SET(${prefix}_${arg_name})
ENDFOREACH(arg_name)
FOREACH(option ${option_names})
SET(${prefix}_${option} FALSE)
ENDFOREACH(option)
SET(current_arg_name DEFAULT_ARGS)
SET(current_arg_list)
FOREACH(arg ${ARGN})
SET(larg_names ${arg_names})
LIST(FIND larg_names "${arg}" is_arg_name)
IF (is_arg_name GREATER -1)
SET(${prefix}_${current_arg_name} ${current_arg_list})
SET(current_arg_name ${arg})
SET(current_arg_list)
ELSE (is_arg_name GREATER -1)
SET(loption_names ${option_names})
LIST(FIND loption_names "${arg}" is_option)
IF (is_option GREATER -1)
SET(${prefix}_${arg} TRUE)
ELSE (is_option GREATER -1)
SET(current_arg_list ${current_arg_list} ${arg})
ENDIF (is_option GREATER -1)
ENDIF (is_arg_name GREATER -1)
ENDFOREACH(arg)
SET(${prefix}_${current_arg_name} ${current_arg_list})
ENDMACRO(PARSE_ARGUMENTS)
vidalia-0.2.21/cmake/VidaliaMacros.cmake 0000664 0000000 0000000 00000026161 12056211037 0020010 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
## Search for lrelease
find_program(VIDALIA_LRELEASE_EXECUTABLE NAMES lrelease-qt4 lrelease
PATHS ${QT_BINARY_DIR} NO_DEFAULT_PATH
)
if (NOT VIDALIA_LRELEASE_EXECUTABLE)
message(FATAL_ERROR
"Vidalia could not find lrelease. Please make sure Qt >= ${QT_MIN_VERSION} is installed."
)
endif(NOT VIDALIA_LRELEASE_EXECUTABLE)
## Search for lupdate
find_program(VIDALIA_LUPDATE_EXECUTABLE NAMES lupdate-qt4 lupdate
PATHS ${QT_BINARY_DIR} NO_DEFAULT_PATH
)
if (NOT VIDALIA_LUPDATE_EXECUTABLE)
message(FATAL_ERROR
"Vidalia could not find lupdate. Please make sure Qt >= ${QT_MIN_VERSION} is installed."
)
endif(NOT VIDALIA_LUPDATE_EXECUTABLE)
## We need windres.exe when building on Win32 to compile the .rc file
if (WIN32 AND NOT MSVC)
find_program(WIN32_WINDRES_EXECUTABLE NAMES windres.exe ${QT_BINARY_DIR})
if (NOT WIN32_WINDRES_EXECUTABLE)
message(FATAL_ERROR
"Vidalia could not find windres. Please make sure MinGW is installed and its bin directory is in your PATH environment variable."
)
endif(NOT WIN32_WINDRES_EXECUTABLE)
endif(WIN32 AND NOT MSVC)
## Adds custom commands to the specified target that will update each of the
## supplied .po files
macro(VIDALIA_UPDATE_PO TARGET)
## Gather a list of all the files that might contain translated strings
file(GLOB_RECURSE translate_SRCS ${Vidalia_SOURCE_DIR}/*.cpp)
file(GLOB_RECURSE translate_HDRS ${Vidalia_SOURCE_DIR}/*.h)
file(GLOB_RECURSE translate_UIS ${Vidalia_SOURCE_DIR}/*.ui)
set(translate_SRCS ${translate_SRCS} ${translate_HDRS} ${translate_UIS})
string(REPLACE ";" " " translate_SRCS "${translate_SRCS}")
foreach (it ${ARGN})
get_filename_component(po ${it} ABSOLUTE)
get_filename_component(podir ${it} PATH)
get_filename_component(outfile ${it} NAME_WE)
set(ts ${CMAKE_CURRENT_BINARY_DIR}/${outfile}.ts)
set(pro ${CMAKE_CURRENT_BINARY_DIR}/${outfile}.pro)
file(WRITE ${pro} "SOURCES = ${translate_SRCS}")
add_custom_command(TARGET ${TARGET}
# Convert the current .po files to .ts
COMMAND ${VIDALIA_PO2TS_EXECUTABLE}
ARGS -q -i ${po} -o ${ts}
# Update the .ts files
COMMAND ${VIDALIA_LUPDATE_EXECUTABLE}
ARGS -silent -noobsolete ${pro} -ts ${ts}
# Convert the updated .ts files back to .po
COMMAND ${VIDALIA_TS2PO_EXECUTABLE}
ARGS -q -i ${ts} -o ${po}
DEPENDS ${VIDALIA_TS2PO_EXECUTABLE} ${VIDALIA_PO2TS_EXECUTABLE}
COMMENT "Updating translation ${it}"
)
endforeach(it)
add_dependencies(${TARGET} ts2po)
add_dependencies(${TARGET} po2ts)
endmacro(VIDALIA_UPDATE_PO)
## Wraps the supplied .po files with commands to convert them to Qt's .qm
## format
macro(VIDALIA_ADD_PO outfiles)
foreach (it ${ARGN})
get_filename_component(po ${it} ABSOLUTE)
get_filename_component(outfile ${it} NAME_WE)
## Create the .po -> .ts conversion step
set(ts ${CMAKE_CURRENT_BINARY_DIR}/${outfile}.ts)
set(qm ${CMAKE_CURRENT_BINARY_DIR}/${outfile}.qm)
add_custom_command(OUTPUT ${qm}
COMMAND ${VIDALIA_PO2TS_EXECUTABLE}
ARGS -q -i ${po} -o ${ts}
COMMAND ${VIDALIA_LRELEASE_EXECUTABLE}
ARGS -compress -silent -nounfinished ${ts} -qm ${qm}
MAIN_DEPENDENCY ${po}
DEPENDS ${VIDALIA_PO2TS_EXECUTABLE}
COMMENT "Generating ${outfile}.qm"
)
set(${outfiles} ${${outfiles}} ${qm})
endforeach(it)
endmacro(VIDALIA_ADD_PO)
## Wraps the input .po file specified by PO in a custom command to convert it
## NSIS's language table format in a .nsh file. The language table is
## specified by NSIS_LANGUAGE. The absolute path to the .nsh file will be
## added to OUTFILES.
macro(VIDALIA_ADD_NSH OUTFILES PO NSIS_LANGUAGE CHARSET)
get_filename_component(po ${PO} ABSOLUTE)
get_filename_component(outfile ${PO} NAME_WE)
## Create the .po -> .nsh conversion step
set(nsh ${CMAKE_CURRENT_BINARY_DIR}/${outfile}.nsh)
add_custom_command(OUTPUT ${nsh}
COMMAND ${VIDALIA_PO2NSH_EXECUTABLE}
ARGS -q -i ${po} -f utf-8 -o ${nsh} -t ${CHARSET} -l ${NSIS_LANGUAGE}
MAIN_DEPENDENCY ${po}
DEPENDS ${VIDALIA_PO2NSH_EXECUTABLE}
COMMENT "Generating ${outfile}.nsh"
)
set(${OUTFILES} ${${OUTFILES}} ${nsh})
endmacro(VIDALIA_ADD_NSH)
## Wraps the input .po file specified by PO in a custom command to convert it
## to WiX's localization XML document in a .wxl file. The culture name is
## specified by CULTURE and codepage by CHARSET.
## Note that CHARSET is not currently used to set codepage of String elements
## but this may be necessary if Wix is not smart enough to do this right.
macro(VIDALIA_ADD_WXL OUTFILES PO CULTURE CHARSET)
get_filename_component(po ${PO} ABSOLUTE)
get_filename_component(outfile ${PO} NAME_WE)
## Create the .po -> .wxl conversion step
set(wxl ${CMAKE_CURRENT_BINARY_DIR}/${outfile}.wxl)
add_custom_command(OUTPUT ${wxl}
COMMAND ${VIDALIA_PO2WXL_EXECUTABLE}
ARGS -q -n ${CULTURE} -i ${po} -o ${wxl}
MAIN_DEPENDENCY ${po}
DEPENDS ${VIDALIA_PO2WXL_EXECUTABLE}
COMMENT "Generating ${outfile}.wxl"
)
set(${OUTFILES} ${${OUTFILES}} ${wxl})
endmacro(VIDALIA_ADD_WXL)
## Queries the specified TOR_EXECUTABLE for its version string using the
## --version argument, parses its output and sets TOR_VERSION to the result.
## If no version could be determined, ${TOR_VERSION} will be undefined.
macro(VIDALIA_GET_TOR_VERSION TOR_VERSION TOR_EXECUTABLE)
get_filename_component(TOR_EXE_PATH ${TOR_EXECUTABLE} ABSOLUTE)
if (UNIX)
execute_process(
COMMAND ${TOR_EXE_PATH} --version
COMMAND tail -n 1
COMMAND awk "{print $3}"
COMMAND sed -e s/\\.$//
OUTPUT_VARIABLE ${TOR_VERSION}
)
else(UNIX)
message(FATAL_ERROR
"The vidalia_get_tor_version macro is not implemented for your platform")
endif(UNIX)
if (DEFINED ${TOR_VERSION})
string(STRIP ${${TOR_VERSION}} ${TOR_VERSION})
endif(DEFINED ${TOR_VERSION})
endmacro(VIDALIA_GET_TOR_VERSION)
if (APPLE)
include(${Vidalia_SOURCE_DIR}/cmake/ParseArgumentsMacro.cmake)
## Calls the install_name_tool utility to change the dependent shared
## library or framework install name to the corresponding library or
## framework that was previously installed in the .app bundle using
## VIDALIA_INSTALL_QT4_FRAMEWORK or VIDALIA_INSTALL_DYLIB when the given
## build target is executed.
macro(VIDALIA_INSTALL_NAME_TOOL)
parse_arguments(INSTALL_NAME_TOOL "TARGET;LIBRARIES;FRAMEWORKS" "" ${ARGN})
foreach(bin ${INSTALL_NAME_TOOL_DEFAULT_ARGS})
foreach(it ${INSTALL_NAME_TOOL_FRAMEWORKS})
add_custom_command(TARGET ${INSTALL_NAME_TOOL_TARGET}
COMMAND install_name_tool -change
${it} @executable_path/../Frameworks/${it} ${bin}
)
endforeach(it)
foreach(it ${INSTALL_NAME_TOOL_LIBRARIES})
get_filename_component(libname ${it} NAME)
add_custom_command(TARGET ${INSTALL_NAME_TOOL_TARGET}
COMMAND install_name_tool -change
${it} @executable_path/lib/${libname} ${bin}
)
endforeach(it)
endforeach(bin)
endmacro(VIDALIA_INSTALL_NAME_TOOL)
## Copies the specified Qt4 framework into the .app bundle, updates its
## shared library identification name, and changes any dependent Qt4
## framework or shared library names to reference a framework previously
## installed in the .app bundle using VIDALIA_INSTALL_QT4_FRAMEWORK.
macro(VIDALIA_INSTALL_QT4_FRAMEWORK)
parse_arguments(INSTALL_QT4_FRAMEWORK
"NAME;TARGET;LIBRARY;APP_BUNDLE;DEPENDS_FRAMEWORKS;DEPENDS_LIBRARIES" ""
${ARGN}
)
set(ditto_ARGS "--rsrc")
foreach (it ${CMAKE_OSX_ARCHITECTURES})
set(ditto_ARGS ${ditto_ARGS} --arch ${it})
endforeach(it)
set(framework "${INSTALL_QT4_FRAMEWORK_NAME}.framework/Versions/4")
set(outdir "${INSTALL_QT4_FRAMEWORK_APP_BUNDLE}/Contents/Frameworks/${framework}")
get_filename_component(libname "${INSTALL_QT4_FRAMEWORK_LIBRARY}" NAME)
add_custom_command(TARGET ${INSTALL_QT4_FRAMEWORK_TARGET}
COMMAND ${CMAKE_COMMAND} -E make_directory ${outdir}
COMMAND ditto ${ditto_ARGS}
${INSTALL_QT4_FRAMEWORK_LIBRARY} ${outdir}/
COMMAND install_name_tool -id
@executable_path/../Frameworks/${framework}/${libname} ${outdir}/${libname}
)
vidalia_install_name_tool(${outdir}/${libname}
TARGET ${INSTALL_QT4_FRAMEWORK_TARGET}
LIBRARIES ${INSTALL_QT4_FRAMEWORK_DEPENDS_LIBRARIES}
FRAMEWORKS ${INSTALL_QT4_FRAMEWORK_DEPENDS_FRAMEWORKS}
)
set(${INSTALL_QT4_FRAMEWORK_DEFAULT_ARGS} ${framework}/${libname})
endmacro(VIDALIA_INSTALL_QT4_FRAMEWORK)
## Copies the specified .dylib into the .app bundle, updates its shared
## library identification name, and changes any dependent framework or
## shared library names to reference a framework or shared library
## previously installed in the .app bundle.
macro(VIDALIA_INSTALL_DYLIB)
parse_arguments(INSTALL_DYLIB
"TARGET;LIBRARY;APP_BUNDLE;DEPENDS_FRAMEWORKS;DEPENDS_LIBRARIES" ""
${ARGN}
)
set(ditto_ARGS "--rsrc")
foreach (it ${CMAKE_OSX_ARCHITECTURES})
set(ditto_ARGS ${ditto_ARGS} --arch ${it})
endforeach(it)
set(outdir "${INSTALL_DYLIB_APP_BUNDLE}/Contents/MacOS/lib/")
get_filename_component(libname "${INSTALL_DYLIB_LIBRARY}" NAME)
add_custom_command(TARGET ${INSTALL_DYLIB_TARGET}
COMMAND ${CMAKE_COMMAND} -E make_directory ${outdir}
COMMAND ditto ${ditto_ARGS}
${INSTALL_DYLIB_LIBRARY} ${outdir}/
COMMAND install_name_tool -id @executable_path/lib/${libname}
)
vidalia_install_name_tool(${outir}/${libname}
TARGET ${INSTALL_DYLIB_TARGET}
LIBRARIES ${INSTALL_DYLIB_DEPENDS_LIBRARIES}
FRAMEWORKS ${INSTALL_DYLIB_DEPENDS_FRAMEWORKS}
)
set(${INSTALL_DYLIB_DEFAULT_ARGS} "${libname}")
endmacro(VIDALIA_INSTALL_DYLIB)
endif(APPLE)
if (WIN32)
## Wraps the supplied .rc files in windres commands if we're building
## with MinGW. Otherwise, it just adds the .rc files directly to the
## list of output files.
macro(WIN32_ADD_RC outfiles)
foreach(it ${ARGN})
if (NOT MSVC)
get_filename_component(it ${it} ABSOLUTE)
get_filename_component(outfile ${it} NAME_WE)
get_filename_component(rc_path ${it} PATH)
set(outfile
${CMAKE_CURRENT_BINARY_DIR}/${outfile}_res${CMAKE_CXX_OUTPUT_EXTENSION}
)
add_custom_command(OUTPUT ${outfile}
COMMAND ${WIN32_WINDRES_EXECUTABLE}
ARGS -i ${it} -o ${outfile} --include-dir=${rc_path}
MAIN_DEPENDENCY ${it}
)
set(${outfiles} ${${outfiles}} ${outfile})
else (NOT MSVC)
set(${outfiles} ${${outfiles}} ${it})
endif(NOT MSVC)
endforeach(it)
endmacro(WIN32_ADD_RC)
endif(WIN32)
vidalia-0.2.21/config.h.in 0000664 0000000 0000000 00000001776 12056211037 0015240 0 ustar 00root root 0000000 0000000 /*
** $Id$
**
** This file is part of Vidalia, and is subject to the license terms in the
** LICENSE file, found in the top level directory of this distribution. If
** you did not receive the LICENSE file with this file, you may obtain it
** from the Vidalia source package distributed by the Vidalia Project at
** http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
** including this file, may be copied, modified, propagated, or distributed
** except according to the terms described in the LICENSE file.
**
*/
#ifndef _CONFIG_H
#define _CONFIG_H
#define VIDALIA_VERSION "@VERSION@"
#cmakedefine HAVE_LIMITS_H
#cmakedefine HAVE_SYS_LIMITS_H
#cmakedefine HAVE_SIGNAL_H
#cmakedefine HAVE_SIGACTION
#cmakedefine HAVE_SIGNAL
#cmakedefine HAVE_GEOIP_H
#cmakedefine HAVE_GEOIPCITY_H
#cmakedefine SIZEOF_INT @SIZEOF_INT@
#cmakedefine USE_MINIUPNPC
#cmakedefine USE_AUTOUPDATE
#cmakedefine USE_MARBLE
#cmakedefine USE_BREAKPAD
#cmakedefine USE_GEOIP
#cmakedefine WIN2K
#endif
vidalia-0.2.21/contrib/ 0000775 0000000 0000000 00000000000 12056211037 0014642 5 ustar 00root root 0000000 0000000 vidalia-0.2.21/contrib/geoip 0000775 0000000 0000000 00000005523 12056211037 0015700 0 ustar 00root root 0000000 0000000 #!/usr/bin/perl -w
#
# Vidalia is distributed under the following license:
#
# Copyright (C) 2006, Matt Edman, Justin Hipple
# Modified slightly by Sasha Romanosky
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
# 02110-1301, USA.
#
# The GeoIP Perl Library is licensed under the GPL. For details
# see the COPYING file.
#################################################################
use strict;
use Geo::IP;
my $VERSION = "05-06";
my $GEODATA = "/home/vidalia/geodata/GeoLiteCity-$VERSION.dat";
my $GI = Geo::IP->open($GEODATA, GEOIP_STANDARD);
my $uri = "";
my %fields = ();
my @params = ();
###############################################################
print "Content-type: text/plain\n\n";
# Parse the URI parameters
my $method = $ENV{"REQUEST_METHOD"};
if ($method eq "POST") {
my $query = "";
read(STDIN, $query, $ENV{'CONTENT_LENGTH'});
# Request came in the form of a POST
@params = split /&/, $query;
} elsif ($method eq "GET") {
# Method is a GET request
if ($ENV{"REQUEST_URI"} && $ENV{"REQUEST_URI"} =~/\?/) {
($uri = $ENV{"REQUEST_URI"}) =~ s/.*\?//g;
}
@params = split /&/, $uri;
} else {
# It wasn't a GET or POST, so we'd better bail.
print "Bad Request\n";
exit 0;
}
# Parse the parameters and values
foreach (@params) {
my ($key, $val) = split /=/, $_;
$fields{$key} = $val;
}
# first build addr list
unless ($fields{"ip"}) {
# Get Geo info for requesting host
printGeoInfo($ENV{"REMOTE_ADDR"});
}
else {
# Resolve each IP in the request
my @addrs = split /,/, $fields{"ip"};
foreach (@addrs) {
my $addr = substr($_, 0, 15); # chop at max length of an IP address
if ($addr =~ /\d+\.\d+\.\d+\.\d+/) { # only select good IPs
printGeoInfo($addr);
}
else {
print "Bad IP\n";
}
}
}
# print the Geo info
sub printGeoInfo {
my $addr = shift;
print "$addr,";
my $r = $GI->record_by_addr($addr);
if ($r) {
print join(",", $r->city,
$r->region,
$r->country_code,
$r->latitude,
$r->longitude);
}
else {
print "UNKNOWN";
}
print "\n";
}
#QED
vidalia-0.2.21/contrib/geoip.py 0000775 0000000 0000000 00000006703 12056211037 0016330 0 ustar 00root root 0000000 0000000 #!/usr/bin/python
##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
from mod_python import apache
from mod_python import util
import GeoIP
import os
def escape_output(f):
if ' ' in f:
f.replace("\\", "\\\\")
f.replace("\"", "\\\"")
return ("\"%s\"" % f)
return f
def is_valid_geoip_record(r):
if r == None:
return False
if not r.has_key('latitude') or r['latitude'] == None:
return False
if not r.has_key('longitude') or r['longitude'] == None:
return False
return True
# Get the form fields
def handler(req):
form = util.FieldStorage(req)
# Get the specified output format and verify it is a valid format. If
# none is specified, default to the old "short" output format.
format = form.getfirst("format", "short").lower()
if format not in ("short", "long"):
format = "short"
# Get a list of all IP addresses in this request. If none is specified,
# display the GeoIP information for the client's address.
iplist = []
if form.has_key("ip"):
for ip in form.getlist("ip"):
iplist.extend(ip.split(","))
else:
iplist.append(req.connection.remote_ip)
# Open the GeoIP database
gi = GeoIP.open("/var/lib/geoip/GeoLiteCity.dat", GeoIP.GEOIP_MEMORY_CACHE)
# Display the output according to the specified format
req.content_type = 'text/plain'
if format == "long":
for ip in iplist:
r = gi.record_by_addr(ip)
if is_valid_geoip_record(r):
fields = []
fields.append("IP=%s" % ip)
fields.append("LAT=%f" % r['latitude'])
fields.append("LON=%f" % r['longitude'])
if r.has_key('city') and r['city'] != None:
fields.append("CITY=%s" % escape_output(r['city']))
if r.has_key('region_name') and r['region_name'] != None:
fields.append("REGION=%s" % escape_output(r['region_name']))
if r.has_key('country_name') and r['country_name'] != None:
fields.append("COUNTRY=%s" % escape_output(r['country_name']))
if r.has_key('country_code') and r['country_code'] != None:
fields.append("CC=%s" % escape_output(r['country_code']))
r = gi.range_by_ip(ip)
if len(r) == 2:
fields.append("FROM=%s" % r[0])
fields.append("TO=%s" % r[1])
response = " ".join(fields)
req.write(response + "\n")
elif format == "short":
for ip in iplist:
r = gi.record_by_addr(ip)
if is_valid_geoip_record(r):
city = region = cc = ""
if r.has_key('city') and r['city'] != None:
city = r['city'].replace(",", " ")
if r.has_key('region') and r['region'] != None:
region = r['region']
if r.has_key('country_code') and r['country_code'] != None:
cc = r['country_code']
response = "%s,%s,%s,%s,%f,%f" % (ip, city, region, cc,
r['latitude'],r['longitude'])
req.write(response + "\n")
else:
req.write(ip + ",UNKNOWN" + "\n")
return apache.OK
vidalia-0.2.21/debian/ 0000775 0000000 0000000 00000000000 12056211037 0014424 5 ustar 00root root 0000000 0000000 vidalia-0.2.21/debian/README.debs 0000664 0000000 0000000 00000002505 12056211037 0016222 0 ustar 00root root 0000000 0000000 ================================
Debian and Ubuntu packages
================================
Binary packages
--------------------------------
Debian and Ubuntu packages are now available in the Tor Debian/Ubuntu
repository. Instructions for adding the repository to your
/etc/apt/sources.list and installing Vidalia can be found here:
https://www.torproject.org/docs/debian-vidalia.html.en
Building your own
--------------------------------
If you would like to build your own packages, you can get the current
Debian source by cloning the Git repository.
If you want to use git-buildpackage:
gbp-clone http://git.debian.org/git/collab-maint/vidalia.git
then use git-buildpackage to build packages.
Else, just clone the repository "normally":
git clone http://git.debian.org/git/collab-maint/vidalia.git
then build packages as normal.
Instructions
--------------------------------
For information about building Debian and Ubuntu packages, please consult
the following documentation:
1. https://wiki.debian.org/DebianPackagingHandbook
2. http://www.debian.org/doc/maint-guide/ch-build.en.html
3. https://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html
4. https://wiki.ubuntu.com/PackagingGuide/Complete
5. https://wiki.ubuntu.com/PbuilderHowto
6. http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
vidalia-0.2.21/doc/ 0000775 0000000 0000000 00000000000 12056211037 0013747 5 ustar 00root root 0000000 0000000 vidalia-0.2.21/doc/CMakeLists.txt 0000664 0000000 0000000 00000001755 12056211037 0016517 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
configure_file(
${CMAKE_CURRENT_SOURCE_DIR}/vidalia.1.in
${CMAKE_CURRENT_SOURCE_DIR}/vidalia.1
)
set(DOXYGEN_INPUT_DIR ${Vidalia_SOURCE_DIR})
set(DOXYGEN_OUTPUT_DIR ${CMAKE_CURRENT_BINARY_DIR})
configure_file(
${CMAKE_CURRENT_SOURCE_DIR}/Doxyfile.in
${CMAKE_CURRENT_BINARY_DIR}/Doxyfile
)
include(FindDoxygen)
if (DOXYGEN_FOUND)
add_custom_target(doxygen
COMMAND ${DOXYGEN_EXECUTABLE} ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile
)
endif(DOXYGEN_FOUND)
vidalia-0.2.21/doc/Doxyfile.in 0000664 0000000 0000000 00000021250 12056211037 0016062 0 ustar 00root root 0000000 0000000 # Doxyfile 1.4.6
#---------------------------------------------------------------------------
# Project related configuration options
#---------------------------------------------------------------------------
PROJECT_NAME = Vidalia
PROJECT_NUMBER = @VERSION@
OUTPUT_DIRECTORY = @DOXYGEN_OUTPUT_DIR@
CREATE_SUBDIRS = NO
OUTPUT_LANGUAGE = English
USE_WINDOWS_ENCODING = NO
BRIEF_MEMBER_DESC = YES
REPEAT_BRIEF = YES
ABBREVIATE_BRIEF = "The $name class" \
"The $name widget" \
"The $name file" \
is \
provides \
specifies \
contains \
represents \
a \
an \
the
ALWAYS_DETAILED_SEC = NO
INLINE_INHERITED_MEMB = NO
FULL_PATH_NAMES = NO
STRIP_FROM_PATH =
STRIP_FROM_INC_PATH =
SHORT_NAMES = NO
JAVADOC_AUTOBRIEF = NO
MULTILINE_CPP_IS_BRIEF = NO
DETAILS_AT_TOP = NO
INHERIT_DOCS = YES
SEPARATE_MEMBER_PAGES = NO
TAB_SIZE = 8
ALIASES =
OPTIMIZE_OUTPUT_FOR_C = NO
OPTIMIZE_OUTPUT_JAVA = NO
BUILTIN_STL_SUPPORT = NO
DISTRIBUTE_GROUP_DOC = NO
SUBGROUPING = YES
#---------------------------------------------------------------------------
# Build related configuration options
#---------------------------------------------------------------------------
EXTRACT_ALL = YES
EXTRACT_PRIVATE = YES
EXTRACT_STATIC = YES
EXTRACT_LOCAL_CLASSES = YES
EXTRACT_LOCAL_METHODS = NO
HIDE_UNDOC_MEMBERS = NO
HIDE_UNDOC_CLASSES = NO
HIDE_FRIEND_COMPOUNDS = NO
HIDE_IN_BODY_DOCS = NO
INTERNAL_DOCS = NO
CASE_SENSE_NAMES = NO
HIDE_SCOPE_NAMES = NO
SHOW_INCLUDE_FILES = YES
INLINE_INFO = YES
SORT_MEMBER_DOCS = YES
SORT_BRIEF_DOCS = NO
SORT_BY_SCOPE_NAME = NO
GENERATE_TODOLIST = YES
GENERATE_TESTLIST = YES
GENERATE_BUGLIST = YES
GENERATE_DEPRECATEDLIST= YES
ENABLED_SECTIONS =
MAX_INITIALIZER_LINES = 30
SHOW_USED_FILES = YES
SHOW_DIRECTORIES = YES
FILE_VERSION_FILTER =
#---------------------------------------------------------------------------
# configuration options related to warning and progress messages
#---------------------------------------------------------------------------
QUIET = NO
WARNINGS = YES
WARN_IF_UNDOCUMENTED = YES
WARN_IF_DOC_ERROR = YES
WARN_NO_PARAMDOC = NO
WARN_FORMAT = "$file:$line: $text"
WARN_LOGFILE =
#---------------------------------------------------------------------------
# configuration options related to the input files
#---------------------------------------------------------------------------
INPUT = @DOXYGEN_INPUT_DIR@
FILE_PATTERNS = *.cpp \
*.h
RECURSIVE = YES
EXCLUDE =
EXCLUDE_SYMLINKS = NO
EXCLUDE_PATTERNS = moc_* \
qrc_* \
ui_*
EXAMPLE_PATH =
EXAMPLE_PATTERNS = *
EXAMPLE_RECURSIVE = NO
IMAGE_PATH =
INPUT_FILTER =
FILTER_PATTERNS =
FILTER_SOURCE_FILES = NO
#---------------------------------------------------------------------------
# configuration options related to source browsing
#---------------------------------------------------------------------------
SOURCE_BROWSER = YES
INLINE_SOURCES = NO
STRIP_CODE_COMMENTS = NO
REFERENCED_BY_RELATION = YES
REFERENCES_RELATION = YES
USE_HTAGS = NO
VERBATIM_HEADERS = YES
#---------------------------------------------------------------------------
# configuration options related to the alphabetical class index
#---------------------------------------------------------------------------
ALPHABETICAL_INDEX = YES
COLS_IN_ALPHA_INDEX = 5
IGNORE_PREFIX =
#---------------------------------------------------------------------------
# configuration options related to the HTML output
#---------------------------------------------------------------------------
GENERATE_HTML = YES
HTML_OUTPUT = html
HTML_FILE_EXTENSION = .html
HTML_HEADER =
HTML_FOOTER =
HTML_STYLESHEET =
HTML_ALIGN_MEMBERS = YES
GENERATE_HTMLHELP = NO
CHM_FILE =
HHC_LOCATION =
GENERATE_CHI = NO
BINARY_TOC = NO
TOC_EXPAND = NO
DISABLE_INDEX = NO
ENUM_VALUES_PER_LINE = 4
GENERATE_TREEVIEW = NO
TREEVIEW_WIDTH = 250
#---------------------------------------------------------------------------
# configuration options related to the LaTeX output
#---------------------------------------------------------------------------
GENERATE_LATEX = NO
LATEX_OUTPUT = latex
LATEX_CMD_NAME = latex
MAKEINDEX_CMD_NAME = makeindex
COMPACT_LATEX = NO
PAPER_TYPE = a4wide
EXTRA_PACKAGES =
LATEX_HEADER =
PDF_HYPERLINKS = NO
USE_PDFLATEX = NO
LATEX_BATCHMODE = NO
LATEX_HIDE_INDICES = NO
#---------------------------------------------------------------------------
# configuration options related to the RTF output
#---------------------------------------------------------------------------
GENERATE_RTF = NO
RTF_OUTPUT = rtf
COMPACT_RTF = NO
RTF_HYPERLINKS = NO
RTF_STYLESHEET_FILE =
RTF_EXTENSIONS_FILE =
#---------------------------------------------------------------------------
# configuration options related to the man page output
#---------------------------------------------------------------------------
GENERATE_MAN = NO
MAN_OUTPUT = man
MAN_EXTENSION = .3
MAN_LINKS = NO
#---------------------------------------------------------------------------
# configuration options related to the XML output
#---------------------------------------------------------------------------
GENERATE_XML = NO
XML_OUTPUT = xml
XML_SCHEMA =
XML_DTD =
XML_PROGRAMLISTING = YES
#---------------------------------------------------------------------------
# configuration options for the AutoGen Definitions output
#---------------------------------------------------------------------------
GENERATE_AUTOGEN_DEF = NO
#---------------------------------------------------------------------------
# configuration options related to the Perl module output
#---------------------------------------------------------------------------
GENERATE_PERLMOD = NO
PERLMOD_LATEX = NO
PERLMOD_PRETTY = YES
PERLMOD_MAKEVAR_PREFIX =
#---------------------------------------------------------------------------
# Configuration options related to the preprocessor
#---------------------------------------------------------------------------
ENABLE_PREPROCESSING = YES
MACRO_EXPANSION = NO
EXPAND_ONLY_PREDEF = NO
SEARCH_INCLUDES = YES
INCLUDE_PATH =
INCLUDE_FILE_PATTERNS =
PREDEFINED =
EXPAND_AS_DEFINED =
SKIP_FUNCTION_MACROS = YES
#---------------------------------------------------------------------------
# Configuration::additions related to external references
#---------------------------------------------------------------------------
TAGFILES =
GENERATE_TAGFILE =
ALLEXTERNALS = NO
EXTERNAL_GROUPS = YES
PERL_PATH = /usr/bin/perl
#---------------------------------------------------------------------------
# Configuration options related to the dot tool
#---------------------------------------------------------------------------
CLASS_DIAGRAMS = YES
HIDE_UNDOC_RELATIONS = YES
HAVE_DOT = NO
CLASS_GRAPH = YES
COLLABORATION_GRAPH = YES
GROUP_GRAPHS = YES
UML_LOOK = YES
TEMPLATE_RELATIONS = NO
INCLUDE_GRAPH = YES
INCLUDED_BY_GRAPH = YES
CALL_GRAPH = NO
GRAPHICAL_HIERARCHY = YES
DIRECTORY_GRAPH = YES
DOT_IMAGE_FORMAT = png
DOT_PATH =
DOTFILE_DIRS =
MAX_DOT_GRAPH_WIDTH = 1024
MAX_DOT_GRAPH_HEIGHT = 1024
MAX_DOT_GRAPH_DEPTH = 1000
DOT_TRANSPARENT = NO
DOT_MULTI_TARGETS = NO
GENERATE_LEGEND = YES
DOT_CLEANUP = YES
#---------------------------------------------------------------------------
# Configuration::additions related to the search engine
#---------------------------------------------------------------------------
SEARCHENGINE = NO
vidalia-0.2.21/doc/feature-spec.txt 0000664 0000000 0000000 00000027554 12056211037 0017110 0 ustar 00root root 0000000 0000000 $Id$
Vidalia Feature Specification
0. Introduction
The purpose of this document is to give an overview of Vidalia's design goals,
as well as a general description of what features must be present in Vidalia.
In addition, this document contains descriptions of features which we have
considered, but which Vidalia does not currently implement either for
technical reasons or because there simply isn't any demand for a feature.
1. Design Overview
Vidalia aims for a "minimalist" interface, meaning that its use should be
unobtrusive wihle the user is doing other tasks on her machine, while still
providing adequate information about the status of their Tor process.
Vidalia also does not aim to support every configuration option offered by
Tor. Tor's configuration file (the user's 'torrc' file) supports a plethora of
configuration options, allowing the user extensive customization over the
behavior of their Tor process; however, not all users need or want to
configure every aspect of Tor. Additionally, it has been the author's
experience that few users actually understand all of Tor's configuration
options nor do they understand the implications of changing those
configuration options (e.g., changing the set of default authoritative
directory servers or allowing only nodes from a specified country).
Vidalia should be able to run Tor with a standard set of default arguments
that allow the user to run Tor without doing any complex initial
configuration. Also, Vidalia users should be able to use and configure Tor
without having to understand details of Tor's inner-workings.
2. Required Features
Items described in this section represent features or functionality that MUST
be present in Vidalia. These features are considered necessary for
providing a useful Tor controller.
2.1. Tor Process Management
Vidalia must support starting and stopping Tor at the user's request, without
the user having to repeatedly specify the location of their Tor executable. In
addition, Vidalia must be able to monitor the status of the Tor process and
alert the user should Tor exit unexpectedly.
Information about the status of Tor should be reflected in an icon on the
user's screen in an area appropriate for their operating system (e.g., the
system tray on Windows or the menu bar on Mac OS X). Hovering over the icon
should give the user a brief description of what the currently displayed icon
indicates (e.g., "Tor is stopped"). Any status indicators the user did not
explicitly ask for, such as a notification balloon on Windows, should be able
to be disabled at the user's discretion.
2.2. Tor Log Messages
Tor has the ability to notify a controller about what it's doing by asking for
a configurable set of log message severity levels. These messages should be
displayed for the user in a single dialog, able to be hidden at the user's
request while continuing to accept log messages from Tor in the background.
Vidalia must also allow the user to configure the severity of messages in
which he is interested.
NOTE: It is entirely possible that the user's Tor process could terminate
before the controller has the ability to connect to Tor's control port,
meaning the user has no way of knowing why their Tor process exited
unexpectedly. In such case, Vidalia must provide an alternative way to view
Tor's output, such as capturing messages logged to stdout.
2.3. Tor Configuration
Vidalia must provide a screen (or set of screens) through which the user can
configure their Tor. As mentioned in Section 1, Vidalia does not need to
support every possible configuratino option, but rather should allow the user
to configure the most often modified options. Configuration options that are
not often changed or have security implications should be placed on an
"Advanced" configuration screen.
With each configuration option displayed, Vidalia must provide a way for the
user to read a text description of what the configuration option represents
and how changing that option affects their Tor process.
2.4. Bandwidth Monitoring
Users are often interested in the rate at which they are currently sending and
receiving through the Tor network. Vidalia must provide a graph of the user's
current transfer rates, based on the amount of data sent and received roughly
each second as reported by Tor via the control protocol.
The bandwidth graph must have an intuitive default appearance and
interpretation, but should also be configurable should the user not like the
defaults. The bandwidth graph must also be able to be resized and "docked"
in a region of the user's screen.
2.5. Current Circuit Information
Vidalia must provide a screen allowing the user to see a list of their
currently opened circuits, including a list of Tor routers which are in each
circuit. The user must be able to select one of the routers in a circuit and
view detailed information about that router, as parsed from its server
descriptor. Such information should include the router's nickname as chosen by
the router operator, the router operator's contact information, that router's
exit policy, etc.
Vidalia should allow the user to see which streams are currently attached to
which circuits. Vidalia may also provide information about the geographic
location of the exit node for each circuit, since outbound connections from
that circuit will appear to originate in the country of that circuit's exit
node.
Vidalia may also give users the ability to destroy a specific circuit should
the user decide that the nodes in that circuit are not providing adequate
performance.
2.6. Tor Network Status
Vidalia must provide a way to view a list of routers currently in the Tor
network and information about each router, such as its nickname, exit policy,
uptime, or bandwidth. In essence, this is a compacted and more intuitive view
of Tor's directory.
Users should be able to search the list of current routers for a specific
nickname or for a router that allows exiting to a specified port. In addition,
users should be able to order the list of available routers by statistics such
as uptime and bandwidth.
2.7. Server Management
2.7.1. Server Setup
The Tor network depends on volunteers to run the Tor routers in the network.
To further encourage users to run a router (server), server setup must be
simple. A small form that prompts the user for necessary information, such as
a nickname for the user's server or contact information, should be displayed.
After completing the form and confirming the entered information, the user's
Tor process should automatically be configured to run as a server with the
information just entered.
2.7.2. Exit Policy Configuration
Many server operators prefer to limit the types of traffic that they will
relay for the Tor network. Since traffic from an exit node appears to
originate from that machine's IP address, server operators may want to try to
cut down on traffic that could get them in trouble, such as file-sharing
traffic. Tor supports this through an ``exit policy'' at each router, which
defines IPs and ports that the operator may either accept or reject. Server
operators may also opt to be a ``middleman node'', who doesn't allow traffic
to exit the Tor network from their node but is willing to relay traffic
between other Tor routers.
Vidalia must make configuring an exit policy easy and intuitive. Vidalia may
also display helpful information for the user, such as what ports are commonly
associated with what sorts of network traffic.
2.7.3. Rate-limiting Configuration
In addition to exit policies, Tor also allows server operators to specify how
much of their bandwidth they are willing to devote to relaying Tor traffic;
however, users may want to devote varying amounts of bandwidth depending on
the time of day. As an example, a server operator may be willing to devote all
of his available bandwidth to the Tor network at night while he is sleeping,
but only a small fraction of it during the day when he is using his machine
for his own activities.
Vidalia must allow server operators to easily schedule rate-limiting depending
on the current date and time. Vidalia could also allow the user to configure
``rate-limiting profiles''. Examples of a profile may include ``weekday''
which would all Tor to use all available bandwidth while the user is at work
and during the evening, ``weekend'' which is similar to ``weekday'' except the
user keeps most of his bandwidth to himself during the day, or ``vacation''
which devotes all bandwidth to Tor all the time.
2.8. Signals
On non-Windows machines, Tor performs a certain action when it receives a
signal. For instance, Tor will reload its torrc if it receives a SIGHUP.
Unfortunately, Windows users are unable to send Tor such signals.
Vidalia must allow the user to simulate sending signals to Tor by using the
SIGNAL feature of the control protocol. Vidalia should also include
descriptions informing the user what each signal does and what it is used for.
3. Desired Features
Features in this section are currently considered useful, but whose design has
yet to be fully considered and planned. These features would be nice to have
in Vidalia, but whose absence would not seriously adversely affect the
usability or utility of Vidalia.
3.1. Graphical display of current circuits
The user should be able to see a map of the world with indicators pointing to
the rough geographic location of each router in the Tor network. Circuits will
be represented by drawing a link between router indicators on the map.
Hovering over an indicator on the map will display information about the
router, as was mentioned in Section 2.5.
The primary difficulty with this feature is finding a free, accurate database
used to map an IP address to a latitude and longitude. Another difficulty with
this is how to represent situations where multiple routers are run at the same
geographic location. For example, there are currently three routers being run
at MIT; the user should be able to easily distinguish between the three.
3.2. Circuit latency information
Users are often interested in how their current circuit is performing, so they
may be interested to see the additional delay added by routing their traffic
through the Tor network. One could imagine an implementation as follows:
Vidalia creates a circuit using the same sequence of nodes in the circuit
whose performance we wish to measure. Vidalia then connects to itself
through that circuit and sends small chunks of data to itself, measuring the
delay between the time the chunk of data is sent and the time it is
received. Vidalia is essentially "pinging" itself through a circuit.
A technical problem with the above approach is that, if the user has a
firewall configured, it must accept connections from the exit node of the
circuit being measured otherwise Vidalia would be unable to connect back to
itself. Also, an adversary who can observe the user would see that a Tor
exit node is connecting back to the user and sending these "pings", yielding
the identity of this user's exit node.
4. Questionable Features
Features in this section may or may not be useful. We might consider
implementing them pending a number of users who desire such features.
4.1. Support for running Vidalia on a separate machine than Tor
Tor gives users the ability to run their Tor process on a server on a LAN
and then point their browser's proxy settings to that server from other
machines on the LAN. In such cases, users of the machines on the LAN not
running Tor would still want to know about the status of the Tor process on
the server but Vidalia would be unable to monitor the process on a remote
machine.
A possible solution for this would be to have an "agent" running on the server
that monitored the state of the Tor process. Vidalia would then connect to
this agent and ask the agent for the state of its Tor process. Vidalia could
also tell the agent to start and stop Tor, forward control messages, etc.
This is probably not worth the effort unless we hear an uproar from users
demanding this feature.
vidalia-0.2.21/doc/geoip-spec.txt 0000664 0000000 0000000 00000015737 12056211037 0016560 0 ustar 00root root 0000000 0000000 $Id$
0. Introduction.
Vidalia tracks geographic coordinates of the IP addresses for Tor
servers, so it can display them in its Network Map window. This
document describes the actual lookup and caching mechanism, and also
lays out some of the security questions and future directions.
1. Fetching and caching.
When we learn one or more new descriptors, we check to see if we have
a cached mapping for each IP address to some geographic location. An
example mapping is:
206.124.149.146,Bellevue,WA,US,47.6051,-122.1134
If we don't have a cached answer, we send an HTTP request to a perl
script located on our geographic information server, asking about one
or more IP addresses.
As of Vidalia 0.1.0, if Vidalia is built against Qt 4.3 or later with
OpenSSL support, the requests are done over an SSL connection and sent to
https://geoip.vidalia-project.net:1443/cgi-bin/geoip
The server has a CACert-issued certificate and CACert's root certificate
is included in Vidalia's signed packages. Prior to Vidalia 0.1.0, or
when Vidalia is built against a Qt without OpenSSL support, requests
are unauthenticated and unencrypted. The requests are sent to
http://geoip.vidalia-project.net/cgi-bin/geoip
which is currently hardcoded into Vidalia's source code.
Request logs are not kept on the geographic information servers.
Each server maintains a GeoLite City database from MaxMind which
allows lookup of geographic location information for a given IP
address. Database lookups are done using a Perl database API, also
provided by MaxMind. More information on the GeoLite City database
can be found at http://www.maxmind.com/app/geolitecity.
Requests can be formatted as either HTTP GET or POST requests. A GET
request for geographic information is applicable for small requests
consisting of only a few IP addresses. An example of a GET request
for geographic information for a single IP address (128.213.11.48)
is:
http://geoip.vidalia-project.net/cgi-bin/geoip?ip=128.213.11.48
which returns the following information:
128.213.11.48,Troy,NY,US,42.7495,-73.5951
Geographic information is formatted in the body of an HTTP response as
IPAddress,City,State,Country,Latitude,Longitude
Multiple IP addresses in a single GET request are separated by commas.
For example:
geoip?ip=128.213.11.48,18.244.0.188,128.2.220.167
which would return the following information in the body of a standard
HTTP response:
128.213.11.48,Troy,NY,US,42.7495,-73.5951
18.244.0.188,Cambridge,MA,US,42.3646,-71.1028
128.2.220.167,Pittsburgh,PA,US,40.4439,-79.9562
Requests can also be formatted as HTTP POST requests, suitable for
requesting geographic information for a large number of IP addresses.
The request is formatted in a similar manner as for an HTTP GET request,
but with the list of IP addresses placed in the body of the request.
POST /cgi-bin/geoip HTTP/1.0
Host: geoip.vidalia-project.net
Content-Length: 42
ip=128.213.11.48,18.244.0.188,128.2.220.167
Vidalia always uses HTTP POST requests to request geographic location
information.
The order of results returned IS NOT guaranteed to be the same as
the order of IP addresses given in the original request. If the
geographic information database does not contain any information for
an IP address given in a request, the string "UNKNOWN" follows that
IP address in the response, separated by a comma
(e.g., "1.2.3.4,UNKNOWN").
If no IP addresses are provided in a request, geographic information
for the IP address of the requester is returned. Vidalia currently
does not use this feature.
We cache geographic information in an unsorted text file called
"~/.vidalia/geoip-cache" (on Windows, the cache file is stored in
%APPDATA%\Vidalia\geoip-cache) along with an optional Unix
timestamp, such as:
206.124.149.146,Bellevue,WA,US,47.6051,-122.1134:1159123625
If no timestamp is associated with a particular cache entry, the
current date and time will be used. We load the cache file on
startup, discard all entries that are over a month old, and write
a new version. After that the cache file is append-only.
The requests are done over Tor, as ordinary socks requests to the
local Tor client. Vidalia will query the local Tor client for its
socks listening address and port via Tor's controller interface.
Once Vidalia queues a request for geographic information, we wait
MIN_RESOLVE_QUEUE_DELAY (currently 10 seconds) after the last
queued request, but no longer than MAX_RESOLVE_QUEUE_DELAY
(currently 30 seconds) after the first queued request, before actually
launching the connection. This way we lump them together and send
one larger request instead of several little ones. If Vidalia's network
map window is not currently visible, the requests are queued until
either the queue contains requests for at least 1/4 of all known
servers, or the network map window becomes visible again.
If we don't get an answer, we don't retry -- if we don't have
geographic information for a server, it simply doesn't get mapped.
2. Security and anonymity questions.
First, can the operator of the above URLs track popularity and
spreading of servers? Yes. Does this buy him anything? I'm not sure.
3. Future directions.
3.1. Tor servers could include geoip data in network statuses.
Rather than having separate geoip services that Vidalia maintains,
we could instead integrate the geoip data into the Tor network
status documents. The Tor directory authorities would learn this
information and the users would learn it through their ordinary
directory downloads.
This would make life easier for Vidalia, but it would also increase
the bandwidth overhead of network-status downloads -- rather than
caching the geoip information, users would fetch it at every update.
3.2. Map networks, not individual IP addresses.
We should stop mapping individual IP addresses. For servers that have
dynamic IP addresses, we end up with something like
68.179.33.128,Toronto,ON,CA,43.6667,-79.4168:1155698575
68.179.33.129,Toronto,ON,CA,43.6667,-79.4168:1155696448
68.179.33.131,Toronto,ON,CA,43.6667,-79.4168:1157209955
Instead we should just cache
68.179.33.0/24,Toronto,ON,CA,43.6667,-79.4168:1155698575
Ideally we would have a database, similar to our current GeoLite City
database, that can provide network prefix information given an IP
address. In the absence of such a database, simply matching on /24
might be easiest and sufficient.
3.3. What else is geoip information for?
What other uses do we have for this information? Is it only useful
for drawing maps of the Tor network?
Once we start letting users control their circuits based on geographic
data, the security questions in Section 2 become more challenging.
vidalia-0.2.21/doc/status-events-ui.txt 0000664 0000000 0000000 00000024105 12056211037 0017752 0 ustar 00root root 0000000 0000000
Adding an Interface for Tor Status Events
1. Introduction & Motivation
This document is intended to describe the addition of an interface to display
summaries of Tor status events in Vidalia. The status event interface is
intended to supplant the existing message log interface. The messages that
appear in the message log are often useful for developers helping users
determine why their Tor is not functioning as expected, but the messages
themselves are usually too confusing for average users.
The goal of the status event interface is to provide two functions. First, it
should promptly notify users when their Tor process is not working properly
(e.g., unable to fetch any directory information). Currently, relevant error
messages from Tor are simply appended to the message log without any
indication to the user that there is something in the log they should look at.
Second, in the case of a warning or error status event, the status event
interface should help the user understand what the problem is and make
specific suggestions for the user to correct the problem.
2. Overview
2.1. Main Interface
The main Vidalia UI will be a single window with multiple tabs or toolbar
buttons at the top. The first tab will always be a "Home" tab. The Home tab
displays general information on Tor, such as whether or not Tor is running,
Tor version information (if Tor is running), whether Vidalia is also running a
proxy application (e.g., Polipo), and information on whether the user is
currently running a Tor relay.
Below the general information is where the status event information will be
located. Status events will be added as a series of items to a QListBox. Each
item in the list box has a 48x48 icon indicating the type of status event.
Available types are STATUS_GENERAL, STATUS_CLIENT and STATUS_SERVER. If the
event has a WARN or ERR, a "badge" will be added to the lower-right corner of
the status event icon. WARN events will have a "yellow triangle with a black
exclamation point" badge. ERR events will have a "red circle with white X"
badge added to the status event icon.
To the right of the icon (or to the left, if the current translation is a RTL
language), will be two to three lines of text. The first line will be in a
bold typeface and will contain a short, one sentence summary of the event. For
example, "Your Tor server is inaccessible" could be the summary sentence for
REACHABILITY_FAILED events.
Below the summary line is up to two lines of descriptive text. In the event of
WARN or ERR status events, the descriptive text gives the user possible
suggestions as to what caused the status event and how they can fix it. If the
descriptive text does not fit in two lines, the part of the message that does
not fit will be replaced with an ellipses ("..."). Clicking on the status
event once will expand the QListBox item vertically allowing the item's full
descriptive text to be seen. Hovering over an item will also display the full
text in a tooltip.
On the far right (or, again, far left in the case of RTL languages), will be a
clickable gray "X". Users can click on the "X" to remove the associated event
from the QListBox. Some events may be removed from the list automatically,
since they can be superseded by another event. As an example, consider an item
representing a REACHABILITY_FAILED status event indicating to the user that
their Tor relay is not reachable from outside their network. If Tor
subsequently emits a REACHABILITY_SUCCEEDED status event, the
REACHABILITY_FAILED event is no longer relevant or accurate and may be removed
from the list. In any case, the list of status events will automatically be
cleared each time Tor is restarted.
The list of status events can also be filtered by the user in order to display
only WARN and/or ERR events. The filtering is accomplished via three clickable
QAction buttons near the status event list. Each button is labeled with the
same badge icon that is used to denote status event severity on the list
item's icon.
2.2. Tray Icon Notifications
As mentioned earlier, currently important warning or error messages are simply
appended to the user's message log without any indication to the user that
they should go look at the log. Consequently, we will use badges on the tray
or dock icon to indicate to the user that there are status event messages they
should look at more closely.
In the case of ERR or WARN status events, a message "balloon" or "bubble" may
also be displayed if the user's window manager permits it. While icon badges
are common on OS X dock icons, dock icons do not support message balloons.
Instead, we will make the dock icon bounce in order to get the user's
attention, which is a common notification mechanism on OS X.
3. Displayed Status Events
Tor currently exposes many status events via its control interface. Like log
messages, however, not all of them are of interest to the user. In this
section, we describe the particular set of status events that will be handled
and displayed to the user in the status event summary interface. Note that
some status events, such as BOOTSTRAP and DANGEROUS_VERSION events are already
handled by Vidalia and displayed to the user via other means, such as a
progress bar or a message boxes, respectively.
3.1. DIR_ALL_UNREACHABLE
Tor sends this events when it is unable to connect to any of the known
directory servers, likely because the user's local network is down. Vidalia
should suggest to the user that they verify their computer is connected to the
Internet.
3.3. ENOUGH_DIR_INFO
This event indicates that Tor has enough directory information to begin
building circuits, but hasn't built one yet. This event can be superseded by a
subsequent CIRCUIT_ESTABLISHED event.
3.4. NOT_ENOUGH_DIR_INFO
Tor sends this event when it believes it does not have sufficient directory
information to build circuits.
3.5. CIRCUIT_ESTABLISHED
This event indicates that Tor has successfully retrieved enough directory
information and has constructed a circuit. No further user action needs to be
taken, but a status event message should still be added indicating to the user
that their Tor client is functioning properly. Additionally, Vidalia currently
changes its tray or dock to green when this event is received.
3.6. CHECKING_REACHABILITY
"ORADDRESS=IP:port"
"DIRADDRESS=IP:port"
This status event will indicate to the user that Tor is checking to see if
their Tor relay is accessible from outside their network. No further action
needs to be taken unless a REACHABILITY_FAILED status event is subsequently
received.
3.7. REACHABILITY_FAILED
"ORADDRESS=IP:port"
"DIRADDRESS=IP:port"
When Vidalia receives a REACHABILITY_FAILED status event, it will notify the
user and suggest ways to make their relay reachable by Tor clients. Most often
this means they have a NAT or firewall that needs the user's ORPort and
possibly DirPort opened. Vidalia could offer to use its UPnP functionality to
attempt to configure the user's network for them.
3.8. REACHABILITY_SUCCEEDED
"ORADDRESS=IP:port"
"DIRADDRESS=IP:port
This event should indicate to the user that their relay was found to be
reachable. No further user action needs to be taken.
3.9. GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
"DIRAUTH=addr:port"
Tor will send these event after the user's Tor relay has successfully uploaded
its server descriptor to at least one of the directory authorities. This
typically means that the user's relay is functioning properly. No further user
action needs to be taken.
3.10. BAD_SERVER_DESCRIPTOR
"DIRAUTH=addr:port"
"REASON=string"
When Vidalia receives this event, it should notify the user. The most likely
reason for this problem is the user's clock is not set correctly. The status
event text should suggest to the user that they should verify their system's
clock is accurate.
3.11. BUG
"REASON=STRING"
Tor sends this status event when an internal check has indicated that there is
likely a Tor software bug. The descriptive text will suggest to the user how
and where to report the bug, as well as what information to include in the bug
report. It may also be useful to generate additional information
automatically, such as the user's operating system version, Tor software
version, etc. The user can then just copy-paste that information into the bug
report.
It is possible that a bug can be triggered repeatedly, so Vidalia will make
sure that only one status event for a particular bug will be displayed. Bug
status events will be compared based on the string provided in the event's
REASON field.
3.12. CLOCK_SKEW
SKEW="+" / "-" SECONDS
MIN_SKEW="+" / "-" SECONDS.
SOURCE="DIRSERV:IP:Port" / "NETWORKSTATUS:IP:PORT" / "CONSENSUS"
If the user's clock skew is high relative to the directory authorities,
Vidalia should notify the user and suggest that they check the accuracy of
their system clock. If the skew is low, then this event should be ignored and
no further action needs to be taken.
4. Unhandled Status Events
The status events described in the previous section are a subset of the status
events Tor currently is capable of reporting. Further, it is quite likely that
Tor will add status events after a particular Vidalia version is released.
Since all status events follow a similar, well-defined interface, it is
possible for Vidalia to still parse these and display them to the user in some
generic format; however, this is not likely to be useful to the user. Recall
that the purpose of adding the status event interface is to be able to provide
specific and directed suggestions to users about how to fix a particular
problem that occurs with their Tor process. If Vidalia just blindly displays
some status events without adding any details on the problem or how to fix it,
the interface is not likely to be any more useful than the existing message
log interface.
As a result, the default behavior should be for Vidalia to simply discard
status events that it does not recognize. We may want to consider adding a
"verbose" option that does display all status events for the user. It's not
clear that this would be benefical to the user, though.
vidalia-0.2.21/doc/version-spec.txt 0000664 0000000 0000000 00000002032 12056211037 0017122 0 ustar 00root root 0000000 0000000 $Id$
Vidalia Version Specification
Vidalia releases will follow the following versioning convention:
Version ::= ..[-svn]
MAJOR ::= Integer >= 0
MINOR ::= Integer >= 0
MICRO ::= Integer >= 0
MICRO will start at 1 and increase monotonically until a stable release, at
which point MINOR will be inremented MICRO will be set to 0 for a stable
release and reset to 1 for the subsequent testing release.
MAJOR will be incremented following several MINOR stable releases in which
extensive functionality has been added or modified. Developers will use
their discretion in determining MAJOR releases.
The -svn flag will be used to denote the latest snapshot in the Subversion
repository. It will be removed for an official release. For example,
0.0.2-svn would become 0.0.2 when it is officially released.
An example of a possible sequence of versions is as follows:
0.0.1
0.0.2
0.0.3
0.1.0 <-- Stable
0.1.1
0.1.2
0.1.3
1.0.0 <-- Stable
vidalia-0.2.21/doc/vidalia.1.in 0000664 0000000 0000000 00000003222 12056211037 0016046 0 ustar 00root root 0000000 0000000 .TH VIDALIA "1" "June 2006" "@VERSION@"
.SH NAME
vidalia \- Controller GUI for tor
.SH SYNOPSIS
.B vidalia
.RI [ options ]
.br
.SH DESCRIPTION
Vidalia allows you to start and stop Tor, view the status of Tor at a
glance, and monitor Tor's bandwidth usage. Vidalia also makes it easy to
contribute to the Tor network by helping you setup a Tor server, if you wish.
To find more information about what Tor is and how to use it, see the Tor
homepage: https://www.torproject.org/
.SH OPTIONS
\fB\-help\fR
Displays this usage message and exits.
.TP
\fB\-reset\fR
Resets ALL stored Vidalia settings.
.TP
\fB\-datadir \fI\fR
Sets Vidalia's datadir to \fI\fR
.TP
\fB\-pidfile \fI\fR
Sets Vidalia's pidfile to \fI\fR
.TP
\fB\-logfile \fI\fR
Sets the name and location of Vidalia's log file. If this option is specified
without a \fIloglevel\fR, the default level of 'notice' will be used.
.TP
\fB\-loglevel \fI[debug|info|notice|warn|error]\fR
Sets the verbosity of Vidalia's logging. If this option is specified without a
\fIlogfile\fR, the log messages will be printed to stdout.
.TP
\fB\-style \fI\fR
Sets Vidalia's interface style. [Windows|Motif|CDE|Plastique]
.TP
\fB\-lang \fI\fR
Sets Vidalia's language. Run Vidalia with the \fI-help\fR option to see a list
of available language codes.
.SH SEE ALSO
.BR tor (1)
.BR http://www.torproject.org/projects/vidalia.html
.SH AUTHORS
Matt Edman
.br
Justin Hipple
This manpage was written by Alexander Wirt for the
Debian Distribution (but may be used by others).
vidalia-0.2.21/pkg/ 0000775 0000000 0000000 00000000000 12056211037 0013763 5 ustar 00root root 0000000 0000000 vidalia-0.2.21/pkg/CMakeLists.txt 0000664 0000000 0000000 00000002551 12056211037 0016526 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
if (APPLE)
add_subdirectory(osx)
endif(APPLE)
if (UNIX)
add_subdirectory(rpm)
endif(UNIX)
if (WIN32)
add_subdirectory(win32)
endif(WIN32)
configure_file(
${CMAKE_CURRENT_SOURCE_DIR}/package.sh
${CMAKE_CURRENT_BINARY_DIR}/package.sh
COPYONLY
)
set(basename "vidalia-${VERSION}")
set(tarname "${basename}.tar.gz")
add_custom_target(dist
COMMAND svn export
${Vidalia_SOURCE_DIR} ${CMAKE_CURRENT_BINARY_DIR}/${basename}
COMMAND ${CMAKE_COMMAND} -E chdir ${CMAKE_CURRENT_BINARY_DIR}
tar czf ${tarname} ${basename}/
COMMAND ${CMAKE_COMMAND} -E copy
${CMAKE_CURRENT_BINARY_DIR}/${tarname} ${Vidalia_BINARY_DIR}
COMMAND ${CMAKE_COMMAND} -E remove -f
${CMAKE_CURRENT_BINARY_DIR}/${tarname}
COMMAND ${CMAKE_COMMAND} -E remove_directory
${CMAKE_CURRENT_BINARY_DIR}/${basename}
COMMENT "Creating ${tarname}"
)
vidalia-0.2.21/pkg/build-geoip-cache.sh 0000775 0000000 0000000 00000002231 12056211037 0017561 0 ustar 00root root 0000000 0000000 #!/bin/sh
##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
DIRURL="http://tor.noreply.org/tor/status/all"
GEOIPURL="http://geoip.vidalia-project.net/cgi-bin/geoip"
CACHEFILE="geoip-cache"
if [ "$1" == "-notimestamp" -o "$1" == "--notimestamp" ]; then
timestamp=""
else
timestamp=":$(date +%s)"
fi
# Fetch a list of server IP addresses
ipaddrs=$(wget -q -O - "$DIRURL" | awk '$1 == "r" { print $7 }' | sort | uniq | tr "\n" ",")
# Get GeoIP information for each IP address
geoips=$(wget -q -O - --post-data="ip=$ipaddrs" "$GEOIPURL")
# Cache the GeoIP information with timestamps
IFS=$'\n'
rm -f $CACHEFILE
for geoip in $geoips; do
echo "$geoip""$timestamp" >> "$CACHEFILE"
done
vidalia-0.2.21/pkg/geoip-cache 0000664 0000000 0000000 00000167115 12056211037 0016065 0 ustar 00root root 0000000 0000000 1.106.108.74,UNKNOWN
1.33.51.172,UNKNOWN
1.40.197.194,UNKNOWN
100.0.2.29,UNKNOWN
12.206.244.188,Philadelphia,PA,US,39.9524,-75.1653
12.30.222.65,Lindon,UT,US,40.3220,-111.7467
121.206.24.169,UNKNOWN
121.232.39.81,Beijing,22,CN,39.9289,116.3883
121.30.139.29,Taiyuan,24,CN,37.8694,112.5603
122.162.162.135,UNKNOWN
123.115.176.85,UNKNOWN
123.115.2.82,UNKNOWN
123.116.128.122,UNKNOWN
123.116.196.92,UNKNOWN
124.120.235.93,Bangkok,40,TH,13.7500,100.5167
125.115.10.204,Beijing,22,CN,39.9289,116.3883
125.116.21.148,Beijing,22,CN,39.9289,116.3883
125.120.196.26,Beijing,22,CN,39.9289,116.3883
125.201.84.208,Tokyo,40,JP,35.6850,139.7514
125.226.37.243,Taipei,03,TW,25.0392,121.5250
125.229.115.35,Taipei,03,TW,25.0392,121.5250
125.64.92.16,Beijing,22,CN,39.9289,116.3883
128.12.146.126,Stanford,CA,US,37.4178,-122.1720
128.12.71.22,Stanford,CA,US,37.4178,-122.1720
128.12.84.16,Stanford,CA,US,37.4178,-122.1720
128.12.91.111,Stanford,CA,US,37.4178,-122.1720
128.135.121.104,Chicago,IL,US,41.7804,-87.6027
128.138.207.48,Boulder,CO,US,40.0878,-105.3736
128.2.141.33,Pittsburgh,PA,US,40.4439,-79.9562
128.31.0.34,Cambridge,MA,US,42.3646,-71.1028
128.39.141.245,Stavanger,14,NO,58.9667,5.7500
128.83.114.63,Austin,TX,US,30.2961,-97.7369
129.187.150.131,Muenchen,02,DE,48.1500,11.5833
129.2.168.220,Alexandria,VA,US,38.7909,-77.0947
129.241.146.124,Trondheim,16,NO,63.4167,10.4167
129.93.140.190,Lincoln,NE,US,40.8211,-96.7118
130.126.141.153,Urbana,IL,US,40.1095,-88.2123
130.133.110.134,Berlin,16,DE,52.5167,13.4000
130.89.160.179,Enschede,15,NL,52.2167,6.9000
130.89.161.226,Enschede,15,NL,52.2167,6.9000
131.114.79.140,Centro,20,IT,45.6833,13.0667
131.155.109.174,Eindhoven,06,NL,51.4500,5.4667
131.155.141.98,Eindhoven,06,NL,51.4500,5.4667
131.155.71.110,Eindhoven,06,NL,51.4500,5.4667
131.246.89.15,Kaiserslautern,08,DE,49.4500,7.7500
134.100.194.4,Hamburg,04,DE,53.5500,10.0000
134.102.204.241,Bremen,03,DE,53.0833,8.8000
134.130.57.18,Aachen,07,DE,50.7708,6.1053
134.169.156.140,Braunschweig,06,DE,52.2667,10.5333
134.169.164.172,Braunschweig,06,DE,52.2667,10.5333
134.53.24.52,Oxford,OH,US,39.4792,-84.7130
134.93.142.188,Mainz,08,DE,50.0000,8.2711
134.93.142.48,Mainz,08,DE,50.0000,8.2711
137.226.13.2,Aachen,07,DE,50.7708,6.1053
137.226.181.149,Aachen,07,DE,50.7708,6.1053
138.26.117.12,Birmingham,AL,US,33.5446,-86.9292
140.112.23.186,Taipei,03,TW,25.0392,121.5250
140.112.247.53,Taipei,03,TW,25.0392,121.5250
140.113.94.101,Taipei,03,TW,25.0392,121.5250
140.129.68.124,Taipei,03,TW,25.0392,121.5250
140.142.38.109,Seattle,WA,US,47.6606,-122.2919
140.180.163.6,Princeton,NJ,US,40.3756,-74.6597
140.247.60.64,Cambridge,MA,US,42.3800,-71.1329
141.149.128.197,Buffalo,NY,US,42.9096,-78.8291
141.31.15.96,Stuttgart,01,DE,48.7667,9.1833
143.89.220.238,Hong Kong,00,HK,22.2833,114.1500
145.18.230.38,Amsterdam,07,NL,52.3500,4.9167
145.97.228.167,Utrecht,09,NL,52.0833,5.1333
147.102.1.42,Athens,35,GR,37.9833,23.7332
147.251.52.140,Brno,78,CZ,49.2000,16.6333
147.32.120.36,Prague,52,CZ,50.0833,14.4667
148.204.7.193,Mexico,09,MX,19.4342,-99.1386
149.9.0.27,Washington,DC,US,38.9144,-77.0763
149.9.0.57,Washington,DC,US,38.9144,-77.0763
149.9.0.58,Washington,DC,US,38.9144,-77.0763
149.9.0.59,Washington,DC,US,38.9144,-77.0763
150.140.191.108,Patras,38,GR,38.2444,21.7344
150.214.190.58,Sevilla,51,ES,37.3772,-5.9869
151.118.168.120,Littleton,CO,US,39.5975,-105.0141
151.37.69.211,Strada,05,IT,44.3000,11.0333
151.73.160.23,Milano,09,IT,45.4667,9.2000
151.76.155.181,Milano,09,IT,45.4667,9.2000
152.13.233.17,Greensboro,NC,US,36.0661,-79.8068
154.20.36.9,Edmonton,AB,CA,53.5500,-113.5000
156.17.2.222,Wroclaw,72,PL,51.1000,17.0333
156.56.105.20,Bloomington,IN,US,39.2499,-86.4555
159.148.138.159,Riga,25,LV,56.9500,24.1000
159.149.105.57,Milano,09,IT,45.4667,9.2000
159.149.155.89,Milano,09,IT,45.4667,9.2000
159.149.71.27,Milano,09,IT,45.4667,9.2000
160.75.15.46,Istanbul,34,TR,41.0186,28.9647
161.53.160.104,Zagreb,21,HR,45.8000,16.0000
163.13.112.191,Taipei,03,TW,25.0392,121.5250
163.20.168.168,Taipei,03,TW,25.0392,121.5250
163.26.225.249,Taipei,03,TW,25.0392,121.5250
166.111.249.39,,,CN,35.0000,105.0000
166.70.207.2,Salt Lake City,UT,US,40.7561,-111.8837
166.70.99.91,Salt Lake City,UT,US,40.7242,-111.8787
168.103.69.43,Denver,CO,US,39.7437,-104.9793
168.150.251.36,Davis,CA,US,38.4829,-121.6398
168.150.251.39,Davis,CA,US,38.4829,-121.6398
171.64.40.65,Stanford,CA,US,37.4178,-122.1720
172.134.101.74,,,US,38.0000,-97.0000
172.178.107.80,,,US,38.0000,-97.0000
172.181.95.60,,,US,38.0000,-97.0000
172.201.41.232,,,US,38.0000,-97.0000
18.100.0.68,Cambridge,MA,US,42.3646,-71.1028
18.152.2.242,Cambridge,MA,US,42.3646,-71.1028
18.187.1.68,Cambridge,MA,US,42.3646,-71.1028
18.243.0.74,Cambridge,MA,US,42.3646,-71.1028
18.243.2.53,Cambridge,MA,US,42.3646,-71.1028
18.244.3.24,Cambridge,MA,US,42.3646,-71.1028
18.246.1.160,Cambridge,MA,US,42.3646,-71.1028
18.26.0.25,Cambridge,MA,US,42.3646,-71.1028
18.42.0.124,Cambridge,MA,US,42.3646,-71.1028
18.85.1.13,Cambridge,MA,US,42.3646,-71.1028
189.129.3.104,Mexico,09,MX,19.4342,-99.1386
189.29.64.184,,,BR,-10.0000,-55.0000
190.140.62.223,UNKNOWN
190.31.247.174,UNKNOWN
192.108.114.19,Xnthi,03,GR,41.1414,24.8836
192.150.94.81,Utrecht,09,NL,52.0833,5.1333
192.255.255.253,UNKNOWN
192.35.156.12,San Diego,CA,US,32.7977,-117.1322
192.67.63.148,Plano,TX,US,33.0260,-96.6990
193.110.91.7,London,P5,GB,51.5000,-0.1167
193.111.87.20,,,CY,35.0000,33.0000
193.167.127.81,Espoo,13,FI,60.2167,24.6667
193.19.77.145,Toulouse,B3,FR,43.6000,1.4333
193.196.182.215,Lrrach,01,DE,47.6167,7.6667
193.198.207.6,Zagreb,21,HR,45.8000,16.0000
193.201.52.133,Hannver,06,DE,53.1833,8.5167
193.202.88.3,Budapest,05,HU,47.5000,19.0833
193.219.115.200,UNKNOWN
193.219.28.244,Warsaw,67,PL,52.2500,21.0000
193.224.70.6,Budapest,05,HU,47.5000,19.0833
193.224.70.7,Budapest,05,HU,47.5000,19.0833
193.34.68.132,UNKNOWN
193.55.112.121,Paris,A8,FR,48.8667,2.3333
193.93.3.6,Muenster,07,DE,51.9667,7.6333
194.109.206.212,Amsterdam,07,NL,52.3500,4.9167
194.152.123.48,Vienna,09,AT,48.2000,16.3667
194.169.192.183,UNKNOWN
194.171.167.147,Utrecht,09,NL,52.0833,5.1333
194.177.96.78,Codogno,05,IT,45.1500,9.7000
194.187.213.89,Espoo,13,FI,60.2167,24.6667
194.231.188.66,,,DE,51.0000,9.0000
194.46.243.32,,,IE,53.0000,-8.0000
194.88.217.156,Wien,09,AT,48.2000,16.3667
194.97.160.186,Leithe,07,DE,51.4667,7.1167
195.111.98.214,Budapest,05,HU,47.5000,19.0833
195.113.141.130,st Nad Labem,89,CZ,50.6667,14.0333
195.113.36.49,Prague,52,CZ,50.0833,14.4667
195.14.235.213,Cologne,07,DE,50.9333,6.9500
195.140.191.14,Odessa,17,UA,46.4667,30.7333
195.146.244.253,Croix,B4,FR,50.6667,3.1500
195.158.167.56,Hamburg,04,DE,53.5500,10.0000
195.158.167.63,Hamburg,04,DE,53.5500,10.0000
195.165.82.253,Lappeenranta,13,FI,61.0667,28.1833
195.169.205.25,Nijmegen,03,NL,51.8333,5.8667
195.177.250.222,Wien,09,AT,48.2000,16.3667
195.230.168.95,Eisenstadt,01,AT,47.8500,16.5167
195.234.100.13,Graz,06,AT,47.0667,15.4500
195.36.241.63,,,FR,46.0000,2.0000
195.37.132.28,Franken,08,DE,50.5000,7.2332
195.70.150.44,Praha,52,CZ,50.0833,14.4667
195.71.8.10,Verl,07,DE,51.8833,8.5167
195.71.90.10,Verl,07,DE,51.8833,8.5167
195.85.225.145,Zaandam,07,NL,52.4500,4.8333
196.2.121.177,Johannesburg,06,ZA,-26.2000,28.0833
196.206.223.240,Rabat,24,MA,34.0253,-6.8361
196.206.41.113,Rabat,24,MA,34.0253,-6.8361
198.145.242.242,Vancouver,WA,US,45.6023,-122.5167
199.201.145.178,Brookline,MA,US,42.3326,-71.1282
2.254.46.95,UNKNOWN
200.177.0.46,Porto Alegre,23,BR,-30.0333,-51.2000
200.188.241.228,Florianpolis,26,BR,-27.5833,-48.5667
200.94.91.115,La Paz,03,MX,24.1667,-110.3000
201.233.192.128,UNKNOWN
201.243.138.187,Caracas,25,VE,10.5000,-66.9167
201.29.181.237,Rio De Janeiro,21,BR,-22.9000,-43.2333
201.37.205.200,So Paulo,27,BR,-23.5333,-46.6167
202.113.118.250,Tianjin,28,CN,39.1422,117.1767
202.156.177.215,Singapore,00,SG,1.2931,103.8558
202.173.141.155,Hillcrest,04,AU,-17.3667,145.6000
202.196.113.125,Zhengzhou,09,CN,34.7578,113.6486
202.69.68.58,Hong Kong,00,HK,22.2833,114.1500
202.71.232.26,Chung Kwai Chung,00,HK,22.3667,114.1333
203.155.165.248,Bangkok,40,TH,13.7500,100.5167
203.218.215.38,Central District,00,HK,22.2833,114.1500
204.11.104.245,Berkeley,CA,US,37.8670,-122.2400
204.13.236.244,Red Oak,TX,US,32.5227,-96.8048
204.15.133.171,Dana Point,CA,US,33.4782,-117.7064
204.253.162.11,San Francisco,CA,US,37.7645,-122.4294
205.244.242.67,Orlando,FL,US,28.5037,-81.3306
206.174.19.25,Fairbanks,AK,US,64.8834,-147.4985
206.222.29.14,Columbus,OH,US,40.0842,-82.9378
206.231.255.250,Silver Spring,MD,US,39.0046,-77.0369
206.55.74.0,Milwaukee,WI,US,43.0362,-87.9170
207.160.159.85,Columbia,MO,US,38.8896,-92.2236
207.174.191.134,Berthoud,CO,US,40.2912,-105.0816
207.210.74.165,Atlanta,GA,US,33.7516,-84.3915
207.224.113.38,Denver,CO,US,39.7525,-104.9995
207.36.232.16,Fort Lauderdale,FL,US,26.1882,-80.1711
207.38.252.195,Rego Park,NY,US,40.7235,-73.8612
207.44.180.3,Houston,TX,US,29.9342,-95.4057
207.7.145.213,San Francisco,CA,US,37.7758,-122.4128
208.106.21.4,Santa Rosa,CA,US,38.3928,-122.7507
208.116.11.54,Clifton,NJ,US,40.8326,-74.1307
208.40.218.131,Orland Park,IL,US,41.6044,-87.8895
208.51.51.165,Edmond,OK,US,35.6784,-97.4944
208.64.36.69,Troy,MI,US,42.5563,-83.1769
208.69.181.9,San Jose,CA,US,37.3857,-121.8993
208.75.85.115,UNKNOWN
208.75.85.208,UNKNOWN
209.147.127.221,Tacoma,WA,US,47.2626,-122.4413
209.160.32.149,Washington,DC,US,38.9097,-77.0231
209.162.39.130,San Luis Obispo,CA,US,35.2678,-120.6591
209.172.52.78,Cave Creek,AZ,US,33.8045,-111.9318
209.205.236.49,San Ysidro,CA,US,32.5675,-116.9740
209.221.138.34,Seattle,WA,US,47.5951,-122.3326
209.221.193.39,Palmdale,CA,US,34.5200,-118.0835
209.223.236.238,Dallas,TX,US,32.8796,-96.7043
209.237.230.67,San Francisco,CA,US,37.7758,-122.4128
209.242.227.89,Milwaukee,WI,US,43.0522,-87.9650
209.51.169.86,Fremont,CA,US,37.5155,-121.8962
209.59.180.78,Lansing,MI,US,42.7257,-84.6360
209.8.40.177,Centreville,VA,US,38.8159,-77.4607
209.97.215.240,Kelowna,BC,CA,49.9000,-119.4833
210.224.92.251,,,JP,36.0000,138.0000
211.157.109.95,Beijing,22,CN,39.9289,116.3883
211.162.29.86,Nanjing,04,CN,32.0617,118.7778
212.108.197.46,Budapest,05,HU,47.5000,19.0833
212.112.235.78,,,DE,51.0000,9.0000
212.112.241.137,,,DE,51.0000,9.0000
212.112.241.44,,,DE,51.0000,9.0000
212.112.242.159,,,DE,51.0000,9.0000
212.112.242.21,,,DE,51.0000,9.0000
212.112.242.89,,,DE,51.0000,9.0000
212.118.15.221,Amman,11,JO,31.9500,35.9333
212.118.59.154,Penza,57,RU,53.1958,45.0000
212.149.225.3,Kuopio,14,FI,62.9000,27.6833
212.168.190.8,,,DE,51.0000,9.0000
212.17.83.217,Vienna,09,AT,48.2000,16.3667
212.187.48.185,Lelystad,16,NL,52.5167,5.4500
212.202.177.81,Bargstedt,10,DE,54.1667,9.7667
212.202.233.2,Koeln,07,DE,50.9333,6.9500
212.227.108.114,Karlsruhe,01,DE,49.0047,8.3858
212.227.49.27,Karlsruhe,01,DE,49.0047,8.3858
212.24.168.178,Szeged,19,HU,46.2500,20.1667
212.246.67.151,,,FI,64.0000,26.0000
212.35.1.141,Uitikon,01,CH,47.3667,8.4667
212.42.236.140,Sandstedt,06,DE,53.3667,8.5333
212.56.241.116,,,EU,47.0000,8.0000
212.99.207.80,Ohlsdorf,04,DE,53.6167,10.0333
213.100.254.167,Frlunda,28,SE,57.3333,13.0167
213.100.3.233,Kista,26,SE,59.4500,17.9167
213.112.9.121,Gteborg,28,SE,57.7167,11.9667
213.113.162.17,,,SE,62.0000,15.0000
213.114.68.170,,,SE,62.0000,15.0000
213.130.162.253,Amsterdam,07,NL,52.3500,4.9167
213.133.126.124,Gunzenhausen,02,DE,49.1000,10.7500
213.141.77.131,Gvle,03,SE,60.6667,17.1667
213.144.140.50,Zuchwil,18,CH,47.2000,7.5667
213.146.114.96,Kamp,07,DE,50.9333,7.7833
213.17.104.91,Utrecht,09,NL,52.0833,5.1333
213.186.233.196,Pori,15,FI,61.4833,21.7833
213.196.252.236,Cologne,07,DE,50.9333,6.9500
213.202.139.32,Clonmel,26,IE,52.3550,-7.7039
213.203.156.22,Rome,07,IT,41.9000,12.4832
213.203.214.130,Euskirchen,07,DE,50.6667,6.7833
213.220.233.230,Prague,52,CZ,50.0833,14.4667
213.226.88.188,Gravryd,28,SE,57.7667,13.1333
213.228.241.143,London,P5,GB,51.5000,-0.1167
213.231.98.136,Barcelona,56,ES,41.3833,2.1833
213.239.193.119,Gunzenhausen,02,DE,49.1000,10.7500
213.239.202.232,Gunzenhausen,02,DE,49.1000,10.7500
213.239.206.174,Gunzenhausen,02,DE,49.1000,10.7500
213.239.207.67,Gunzenhausen,02,DE,49.1000,10.7500
213.239.211.148,Gunzenhausen,02,DE,49.1000,10.7500
213.239.212.133,Gunzenhausen,02,DE,49.1000,10.7500
213.239.215.85,Gunzenhausen,02,DE,49.1000,10.7500
213.246.63.134,Verdun,B2,FR,49.1667,5.3833
213.25.76.12,Sokolka,24,PL,53.4167,23.5000
213.251.169.20,Roubaix,B4,FR,50.7000,3.1667
213.254.226.25,Madrid,29,ES,40.4000,-3.6833
213.39.164.160,Hamburg,04,DE,53.5500,10.0000
213.41.242.132,Paris,A8,FR,48.8667,2.3333
213.44.61.87,,,FR,46.0000,2.0000
213.65.146.100,,,SE,62.0000,15.0000
213.67.207.73,,,SE,62.0000,15.0000
213.84.147.225,Castricum,07,NL,52.5500,4.6667
213.84.192.84,Rijswijk,11,NL,52.0167,4.3333
213.84.46.114,The Hague,11,NL,52.0833,4.3000
213.9.1.108,Duisburg,07,DE,51.4333,6.7500
216.110.217.24,West Linn,OR,US,45.3422,-122.6639
216.127.93.186,Houston,TX,US,29.9342,-95.4057
216.137.65.86,Cedar Rapids,IA,US,41.9874,-91.6838
216.139.253.42,Austin,TX,US,30.2643,-97.7139
216.194.67.53,Edmonton,AB,CA,53.5500,-113.5000
216.195.133.27,Manchester,NH,US,42.9841,-71.4487
216.211.73.101,Thunder Bay,ON,CA,48.4000,-89.2333
216.220.98.32,New York,NY,US,40.7619,-73.9763
216.224.124.124,Aptos,CA,US,37.0082,-121.8777
216.231.168.178,Pensacola,FL,US,30.4506,-87.2755
216.231.47.120,Seattle,WA,US,47.5951,-122.3326
216.239.81.232,Montral,QC,CA,45.5000,-73.5833
216.27.181.158,Oakland,CA,US,37.7950,-122.2193
216.39.137.58,Seattle,WA,US,47.5951,-122.3326
216.54.123.80,Virginia Beach,VA,US,36.8061,-76.0612
216.86.198.76,Long Beach,CA,US,33.7976,-118.1617
217.10.142.173,Studley,Q4,GB,52.2667,-1.8833
217.10.241.26,Plovdiv,51,BG,42.1500,24.7500
217.11.248.50,Brno,78,CZ,49.2000,16.6333
217.11.54.81,,,DE,51.0000,9.0000
217.113.229.42,Lodz,53,PL,52.2667,16.7500
217.114.79.30,Hamburg,04,DE,53.5500,10.0000
217.115.192.218,Amsterdam,07,NL,52.3500,4.9167
217.115.204.25,Amsterdam,07,NL,52.3500,4.9167
217.116.101.208,Warsaw,67,PL,52.2500,21.0000
217.121.118.110,Leeuwarden,02,NL,53.2000,5.7833
217.144.200.8,Tarnw,64,PL,50.0167,20.9832
217.149.34.124,Schiphol,07,NL,52.3000,4.7500
217.155.230.230,Rochdale,L2,GB,53.6167,-2.1500
217.16.65.190,Skopje,41,MK,42.0000,21.4333
217.160.107.206,Karlsruhe,01,DE,49.0047,8.3858
217.160.111.190,Karlsruhe,01,DE,49.0047,8.3858
217.160.169.57,Karlsruhe,01,DE,49.0047,8.3858
217.160.176.49,Karlsruhe,01,DE,49.0047,8.3858
217.160.203.26,Karlsruhe,01,DE,49.0047,8.3858
217.160.254.116,,OH,US,40.3914,-82.7526
217.160.78.171,Karlsruhe,01,DE,49.0047,8.3858
217.172.183.219,,,DE,51.0000,9.0000
217.172.47.18,Frankfurt,05,DE,50.1167,8.6833
217.173.129.76,Hofheim,05,DE,50.0833,8.4500
217.196.64.205,Vienna,09,AT,48.2000,16.3667
217.20.117.129,Frankfurt,05,DE,50.1167,8.6833
217.20.117.240,Frankfurt,05,DE,50.1167,8.6833
217.20.117.92,Frankfurt,05,DE,50.1167,8.6833
217.20.121.40,Frankfurt,05,DE,50.1167,8.6833
217.216.190.160,Crdoba,51,ES,37.8833,-4.7668
217.219.111.36,Iran,03,IR,32.0922,51.0289
217.227.126.93,Laatzen,06,DE,52.3167,9.8000
217.228.32.82,Krefeld,07,DE,51.3333,6.5667
217.229.246.86,,,DE,51.0000,9.0000
217.230.235.160,Berlin,16,DE,52.5167,13.4000
217.231.16.67,Berlin,16,DE,52.5167,13.4000
217.236.51.127,Wennigsen,06,DE,52.2667,9.5833
217.238.156.119,,,DE,51.0000,9.0000
217.7.67.156,Kissing,02,DE,48.3000,10.9832
217.75.149.120,Sofia,42,BG,42.6833,23.3167
217.79.87.238,Varna,61,BG,43.2167,27.9167
217.80.235.159,Karlsfeld,02,DE,48.2167,11.4667
217.80.83.121,Grnwald,02,DE,48.0500,11.5167
217.87.40.57,,,DE,51.0000,9.0000
217.93.142.168,Frankfurt Am Main,05,DE,50.1167,8.6833
217.96.105.139,Rudnik,45,PL,50.9667,22.4500
218.102.125.231,Central District,00,HK,22.2833,114.1500
218.111.26.171,Kuala Lumpur,14,MY,3.1667,101.7000
218.14.51.24,,,CN,35.0000,105.0000
218.16.124.247,,,CN,35.0000,105.0000
218.18.46.221,,,CN,35.0000,105.0000
218.189.210.17,,,HK,22.2500,114.1667
218.198.122.48,Zhengzhou,09,CN,34.7578,113.6486
218.198.171.174,Zhengzhou,09,CN,34.7578,113.6486
218.198.171.198,Zhengzhou,09,CN,34.7578,113.6486
218.199.29.20,Wuhan,12,CN,30.5833,114.2667
218.21.130.42,,,CN,35.0000,105.0000
218.23.0.86,,,CN,35.0000,105.0000
218.242.10.120,Shanghai,23,CN,31.2222,121.4581
218.58.55.58,Shandong,07,CN,23.5878,117.3508
218.61.138.246,,,CN,35.0000,105.0000
218.79.19.151,Shanghai,23,CN,31.2222,121.4581
218.81.181.205,Shanghai,23,CN,31.2222,121.4581
218.83.249.182,Shanghai,23,CN,31.2222,121.4581
218.83.76.52,Shanghai,23,CN,31.2222,121.4581
218.87.61.229,Beijing,22,CN,39.9289,116.3883
218.9.124.172,,,CN,35.0000,105.0000
219.130.135.26,,,CN,35.0000,105.0000
219.133.175.193,Shenzhen,30,CN,22.5333,114.1333
219.136.170.69,,,CN,35.0000,105.0000
219.156.117.214,Henan,31,CN,18.8572,109.8028
219.234.99.168,Shenzhen,30,CN,22.5333,114.1333
219.31.4.11,,,JP,36.0000,138.0000
219.77.131.211,Central District,00,HK,22.2833,114.1500
220.111.66.236,Tokyo,40,JP,35.6850,139.7514
220.112.165.17,Shenzhen,30,CN,22.5333,114.1333
220.112.233.194,Beijing,22,CN,39.9289,116.3883
220.157.175.94,Asahi,04,JP,35.7167,140.6500
220.171.216.136,,,CN,35.0000,105.0000
220.200.181.80,Beijing,22,CN,39.9289,116.3883
220.233.223.105,,,AU,-27.0000,133.0000
220.237.0.68,Sydney,02,AU,-33.8833,151.2167
220.239.77.129,Sydney,02,AU,-33.8833,151.2167
221.126.153.59,,,HK,22.2500,114.1667
221.129.229.167,Tianjin,28,CN,39.1422,117.1767
221.15.133.163,Beijing,22,CN,39.9289,116.3883
221.216.218.194,Beijing,22,CN,39.9289,116.3883
221.219.216.31,Beijing,22,CN,39.9289,116.3883
221.221.186.186,Beijing,22,CN,39.9289,116.3883
221.225.100.185,Beijing,22,CN,39.9289,116.3883
221.226.85.250,Beijing,22,CN,39.9289,116.3883
221.236.52.34,Beijing,22,CN,39.9289,116.3883
221.3.19.239,Shandong,07,CN,23.5878,117.3508
221.85.38.18,,,JP,36.0000,138.0000
222.104.35.79,Taegu,15,KR,35.8703,128.5911
222.137.73.205,Beijing,22,CN,39.9289,116.3883
222.170.13.7,Zhongshan,30,CN,22.5174,113.3661
222.183.111.138,Beijing,22,CN,39.9289,116.3883
222.209.138.223,Beijing,22,CN,39.9289,116.3883
222.221.221.152,Beijing,22,CN,39.9289,116.3883
222.248.118.45,Shenzhen,30,CN,22.5333,114.1333
222.248.119.183,Shenzhen,30,CN,22.5333,114.1333
222.39.26.33,Beijing,22,CN,39.9289,116.3883
222.64.40.193,Shanghai,23,CN,31.2222,121.4581
222.72.121.113,Beijing,22,CN,39.9289,116.3883
222.77.71.70,Beijing,22,CN,39.9289,116.3883
222.84.47.10,Beijing,22,CN,39.9289,116.3883
222.89.82.130,Beijing,22,CN,39.9289,116.3883
222.93.229.127,Beijing,22,CN,39.9289,116.3883
23.238.141.138,UNKNOWN
24.108.143.182,Saskatoon,SK,CA,52.1333,-106.6668
24.128.11.252,Exeter,NH,US,42.9661,-70.9881
24.128.119.4,Melrose,MA,US,42.4574,-71.0541
24.13.139.93,Chicago,IL,US,41.8675,-87.6744
24.16.125.194,Bellevue,WA,US,47.6027,-122.1557
24.16.54.166,Bothell,WA,US,47.7953,-122.2018
24.165.168.246,Newark,AR,US,35.7309,-91.3903
24.168.217.245,Columbia,SC,US,34.0391,-80.9883
24.17.31.211,Seattle,WA,US,47.5951,-122.3326
24.179.15.82,Saint Louis,MO,US,38.6385,-90.3026
24.180.171.103,Carol Stream,IL,US,41.9153,-88.1287
24.202.116.60,Montral,QC,CA,45.5000,-73.5833
24.202.5.70,Montral,QC,CA,45.5000,-73.5833
24.208.96.212,Boca Raton,FL,US,26.3739,-80.1468
24.21.175.100,Portland,OR,US,45.5184,-122.6554
24.210.100.26,West Bloomfield,MI,US,42.5703,-83.3810
24.211.163.249,Cary,NC,US,35.7821,-78.8177
24.213.243.221,Clifton Park,NY,US,42.8571,-73.7993
24.229.203.25,Palmerton,PA,US,40.8366,-75.5883
24.238.239.34,Spring,TX,US,30.1145,-95.4729
24.26.255.115,San Marcos,TX,US,29.8729,-98.0140
24.29.193.226,Kent,OH,US,41.1413,-81.3339
24.34.114.171,Exeter,NH,US,42.9661,-70.9881
24.34.88.68,Old Saybrook,CT,US,41.3009,-72.3876
24.4.230.89,Salinas,CA,US,36.6859,-121.6293
24.4.89.16,San Mateo,CA,US,37.5488,-122.3124
24.61.37.120,Dedham,MA,US,42.2451,-71.1840
24.71.88.245,Calgary,AB,CA,51.0833,-114.0833
24.9.34.95,Broomfield,CO,US,39.9147,-105.0809
24.90.4.210,Woodhaven,NY,US,40.6931,-73.8575
29.242.154.121,,,US,38.0000,-97.0000
38.119.53.59,Washington,DC,US,38.9144,-77.0763
39.233.11.126,UNKNOWN
5.160.159.185,UNKNOWN
5.171.228.221,UNKNOWN
58.106.45.193,Sydney,02,AU,-33.8833,151.2167
58.141.43.221,Seoul,11,KR,37.5664,126.9997
58.153.18.172,Hong Kong,00,HK,22.2833,114.1500
58.22.133.141,Putian,07,CN,25.4394,119.0103
58.246.247.145,Beijing,22,CN,39.9289,116.3883
58.63.109.78,Beijing,22,CN,39.9289,116.3883
59.134.15.153,,,JP,36.0000,138.0000
59.149.171.231,Hong Kong,00,HK,22.2833,114.1500
59.149.206.178,Hong Kong,00,HK,22.2833,114.1500
59.173.48.182,,,CN,35.0000,105.0000
59.56.158.26,Beijing,22,CN,39.9289,116.3883
59.60.134.153,Beijing,22,CN,39.9289,116.3883
59.66.154.246,Beijing,22,CN,39.9289,116.3883
59.78.26.83,Shanghai,23,CN,31.2222,121.4581
59.78.51.42,Shanghai,23,CN,31.2222,121.4581
59.78.51.43,Shanghai,23,CN,31.2222,121.4581
60.168.81.239,Beijing,22,CN,39.9289,116.3883
60.179.161.16,Ningbo,02,CN,29.8750,121.5419
60.212.214.122,Beijing,22,CN,39.9289,116.3883
60.234.134.113,Auckland,00,NZ,-36.8667,174.7667
60.48.68.15,Kuala Lumpur,14,MY,3.1667,101.7000
60.63.17.147,Shanghai,23,CN,31.2222,121.4581
61.125.222.12,Asahi,04,JP,35.7167,140.6500
61.145.42.177,,,CN,35.0000,105.0000
61.207.170.220,,,JP,36.0000,138.0000
61.239.134.197,Hong Kong,00,HK,22.2833,114.1500
61.79.84.134,,,KR,37.0000,127.5000
61.93.185.237,Hong Kong,00,HK,22.2833,114.1500
62.10.4.57,Rome,07,IT,41.9000,12.4832
62.111.240.11,Marki,67,PL,52.3167,21.1333
62.111.245.119,Poznan,86,PL,52.4167,16.9667
62.112.159.61,,,DE,51.0000,9.0000
62.117.31.194,Wolfsburg,06,DE,52.4333,10.8000
62.121.68.209,Warsaw,67,PL,52.2500,21.0000
62.128.27.167,,,DE,51.0000,9.0000
62.141.56.164,Erfurt,15,DE,50.9833,11.0333
62.141.91.165,Moscow,48,RU,55.7522,37.6156
62.142.248.53,Espoo,13,FI,60.2167,24.6667
62.143.13.58,Dsseldorf,07,DE,51.2167,6.7667
62.146.202.66,Schwabach,02,DE,49.3292,11.0256
62.149.12.179,Kiev,13,UA,50.4333,30.5167
62.149.94.248,Riyadh,10,SA,24.6408,46.7728
62.163.136.55,Amsterdam,07,NL,52.3500,4.9167
62.163.50.62,Osdorp,07,NL,52.3667,4.7833
62.166.240.67,Amsterdam,07,NL,52.3500,4.9167
62.179.68.175,Warsaw,67,PL,52.2500,21.0000
62.194.166.79,Amsterdam,07,NL,52.3500,4.9167
62.197.40.155,Maidenhead,P9,GB,51.5167,-0.7000
62.202.35.184,Muri,05,CH,46.9167,7.4832
62.205.104.38,Brussels,11,BE,50.8333,4.3333
62.206.156.59,Hamburg,04,DE,53.5500,10.0000
62.206.43.161,Hamburg,04,DE,53.5500,10.0000
62.214.197.207,Mittelheubronn,01,DE,47.8000,7.8167
62.214.229.95,Oberfhring,02,DE,48.1667,11.6333
62.214.244.199,Schmargendorf,16,DE,52.4833,13.3000
62.219.121.81,Qiryat Ono,02,IL,32.0636,34.8553
62.219.46.202,Tel Aviv-Yafo,05,IL,32.0678,34.7647
62.220.137.73,Zrich,25,CH,47.3667,8.5500
62.241.240.86,Lohja,13,FI,60.2500,24.0833
62.245.233.242,Munich,02,DE,48.1500,11.5833
62.47.166.185,Vienna,09,AT,48.2000,16.3667
62.48.34.110,Firenze,16,IT,43.7667,11.2500
62.48.42.77,Pietrasanta,16,IT,43.9500,10.2332
62.75.142.20,,,DE,51.0000,9.0000
62.75.150.90,,,DE,51.0000,9.0000
62.75.163.23,,,DE,51.0000,9.0000
62.75.185.82,,,DE,51.0000,9.0000
62.75.186.127,,,DE,51.0000,9.0000
62.75.202.231,,,DE,51.0000,9.0000
62.75.223.163,,,DE,51.0000,9.0000
62.75.252.130,,,DE,51.0000,9.0000
63.228.65.81,Colorado Springs,CO,US,38.8326,-104.7405
63.246.166.66,Austin,TX,US,30.3037,-97.7696
63.85.194.6,Richardson,TX,US,32.9914,-96.6645
64.122.12.107,Portland,OR,US,45.5184,-122.6554
64.142.29.22,Richmond,CA,US,37.9426,-122.3457
64.142.31.83,Concord,CA,US,37.9797,-122.0056
64.142.98.231,Santa Rosa,CA,US,38.3928,-122.7507
64.151.99.196,San Francisco,CA,US,37.7898,-122.3942
64.157.15.26,Tampa,FL,US,27.9578,-82.4622
64.158.128.204,Phoenix,AZ,US,33.5222,-112.0839
64.159.76.19,Tampa,FL,US,27.9578,-82.4622
64.161.78.226,,,US,38.0000,-97.0000
64.164.59.200,Chino Hills,CA,US,33.9473,-117.7289
64.185.20.210,Lubbock,TX,US,33.5663,-101.8830
64.191.50.166,Scranton,PA,US,41.3731,-75.6837
64.191.68.53,Scranton,PA,US,41.3731,-75.6837
64.20.233.234,Austin,TX,US,30.4549,-97.7565
64.22.103.213,UNKNOWN
64.22.71.125,Atlanta,GA,US,33.7516,-84.3915
64.222.126.240,Cranston,RI,US,41.7695,-71.4729
64.230.38.120,Cottam,ON,CA,42.1333,-82.7500
64.230.85.110,Ottawa,ON,CA,45.4167,-75.7000
64.255.172.109,Santa Clara,CA,US,37.3501,-121.9854
64.26.169.184,Ottawa,ON,CA,45.4167,-75.7000
64.27.20.188,Los Angeles,CA,US,34.0619,-118.3098
64.27.25.205,Los Angeles,CA,US,34.0619,-118.3098
64.34.177.245,San Antonio,TX,US,29.4821,-98.4556
64.5.53.220,Dallas,TX,US,32.7825,-96.8207
64.5.53.254,Dallas,TX,US,32.7825,-96.8207
64.62.231.86,Fremont,CA,US,37.5155,-121.8962
64.74.207.50,Atlanta,GA,US,33.7516,-84.3915
64.79.206.216,Bellevue,WA,US,47.5527,-122.1480
64.81.160.72,Seattle,WA,US,47.6145,-122.3480
64.81.53.19,Emeryville,CA,US,37.8342,-122.2897
64.81.59.235,Burlingame,CA,US,37.5671,-122.3710
64.95.64.86,Salem,MA,US,42.5153,-70.9075
65.186.89.136,Hilliard,OH,US,40.0231,-83.1810
65.249.164.72,Buffalo,NY,US,42.9096,-78.8291
65.25.8.48,Youngstown,OH,US,41.0871,-80.6617
65.255.217.11,Long Beach,CA,US,33.7542,-118.2019
65.27.196.244,Cincinnati,OH,US,39.1699,-84.4859
65.38.9.9,Tulsa,OK,US,36.1352,-95.9365
65.39.86.51,Scottsdale,AZ,US,33.5984,-111.8669
65.6.133.55,Atlanta,GA,US,33.8004,-84.3865
65.94.134.233,Toronto,ON,CA,43.6667,-79.4168
65.98.70.171,Clifton,NJ,US,40.8326,-74.1307
65.99.219.91,Dallas,TX,US,32.8148,-96.8706
66.111.43.137,Dacula,GA,US,33.9785,-83.8811
66.114.178.133,Belvidere,IL,US,42.2491,-88.8331
66.114.65.225,New York,NY,US,40.7619,-73.9763
66.116.103.156,San Francisco,CA,US,37.7938,-122.4022
66.117.13.120,UNKNOWN
66.134.212.156,Los Angeles,CA,US,34.0416,-118.2988
66.135.40.74,San Antonio,TX,US,29.4821,-98.4556
66.150.225.107,Atlanta,GA,US,33.7516,-84.3915
66.150.225.130,Atlanta,GA,US,33.7516,-84.3915
66.161.188.33,Cincinnati,OH,US,39.1699,-84.4859
66.175.215.123,UNKNOWN
66.188.99.241,Madison,WI,US,43.0714,-89.3932
66.191.239.246,Sevierville,TN,US,35.8003,-83.5210
66.197.176.115,Moscow,48,RU,55.7522,37.6156
66.199.184.254,Vancouver,BC,CA,49.2500,-123.1333
66.199.236.130,Great River,NY,US,40.7263,-73.1577
66.199.236.138,Great River,NY,US,40.7263,-73.1577
66.199.240.50,Great River,NY,US,40.7263,-73.1577
66.199.252.58,Great River,NY,US,40.7263,-73.1577
66.219.161.166,Doylestown,OH,US,40.9603,-81.6975
66.228.127.27,Carrollton,TX,US,33.0035,-96.9000
66.229.224.108,Los Angeles,CA,US,34.0416,-118.2988
66.23.214.241,Woodstock,GA,US,34.1190,-84.4477
66.240.222.22,San Diego,CA,US,32.8073,-117.1324
66.29.3.183,Parsippany,NJ,US,40.8597,-74.4026
66.31.235.23,Fall River,MA,US,41.6950,-71.1443
66.44.254.169,Mocksville,NC,US,35.8987,-80.5741
66.70.10.53,Hoboken,NJ,US,40.7458,-74.0321
66.92.13.212,San Francisco,CA,US,37.7645,-122.4294
66.92.216.74,Los Angeles,CA,US,34.0530,-118.2642
66.93.220.131,Chicago,IL,US,41.8998,-87.6368
66.93.240.251,Chicago,IL,US,41.8998,-87.6368
66.98.136.49,Houston,TX,US,29.9342,-95.4057
66.98.208.43,Houston,TX,US,29.9342,-95.4057
67.121.242.250,,,US,38.0000,-97.0000
67.15.225.36,Houston,TX,US,29.9342,-95.4057
67.171.72.181,Pittsburgh,PA,US,40.4456,-79.9794
67.18.149.92,Dallas,TX,US,32.7825,-96.8207
67.18.176.110,Dallas,TX,US,32.7825,-96.8207
67.18.92.141,Dallas,TX,US,32.7825,-96.8207
67.18.92.228,Dallas,TX,US,32.7825,-96.8207
67.183.7.242,Bothell,WA,US,47.7953,-122.2018
67.187.144.128,Seattle,WA,US,47.5951,-122.3326
67.43.175.98,Venice,CA,US,33.9944,-118.4639
67.43.74.54,Salem,OR,US,44.9500,-123.0198
67.53.76.66,Eatontown,NJ,US,40.3039,-74.0703
67.67.13.23,Dallas,TX,US,32.7791,-96.8028
67.80.106.153,Wayne,NJ,US,40.9487,-74.2413
67.81.49.158,Neptune,NJ,US,40.2182,-74.0710
67.85.88.5,Spring Valley,NY,US,41.1163,-74.0460
67.88.160.67,Claremont,NH,US,43.3592,-72.3363
68.105.166.197,Gainesville,FL,US,29.6694,-82.3573
68.107.36.62,San Diego,CA,US,32.7977,-117.1322
68.107.79.224,San Diego,CA,US,32.7977,-117.1322
68.117.130.197,Madison,WI,US,43.0714,-89.3932
68.12.186.211,Oklahoma City,OK,US,35.4715,-97.5190
68.144.77.32,Calgary,AB,CA,51.0833,-114.0833
68.146.236.11,Calgary,AB,CA,51.0833,-114.0833
68.178.205.201,Scottsdale,AZ,US,33.6119,-111.8907
68.183.231.16,Winnetka,CA,US,34.2093,-118.5752
68.47.174.246,Knoxville,TN,US,35.9724,-83.9595
68.47.207.110,Knoxville,TN,US,35.9724,-83.9595
68.52.222.138,Franklin,TN,US,35.9340,-86.8878
68.53.110.153,Clarksville,TN,US,36.5090,-87.3396
68.53.139.144,Hermitage,TN,US,36.1782,-86.6099
68.62.77.70,Royal Oak,MI,US,42.5055,-83.1527
68.63.98.46,Hamden,CT,US,41.3820,-72.9171
68.93.137.39,Oklahoma City,OK,US,35.4715,-97.5190
68.95.157.4,Dallas,TX,US,32.8098,-96.7993
69.113.27.13,Eatontown,NJ,US,40.3039,-74.0703
69.116.183.163,Hicksville,NY,US,40.7670,-73.5254
69.12.150.55,Hayward,CA,US,37.6503,-122.0730
69.12.180.247,Santa Rosa,CA,US,38.3928,-122.7507
69.13.8.97,Fort Worth,TX,US,32.7492,-97.2205
69.140.199.51,Washington,DC,US,38.9097,-77.0231
69.16.139.103,Phoenix,AZ,US,33.5083,-112.0718
69.20.97.236,San Jose,CA,US,37.3874,-121.9024
69.207.190.123,Rochester,NY,US,43.1693,-77.6189
69.209.180.140,Waterford,MI,US,42.6612,-83.3824
69.230.8.156,Dallas,TX,US,32.7791,-96.8028
69.243.35.48,Washington,DC,US,38.9097,-77.0231
69.250.186.156,Greenbelt,MD,US,39.0027,-76.8807
69.251.182.82,Bethesda,MD,US,38.9878,-77.1262
69.253.173.96,Fort Monmouth,NJ,US,40.3139,-74.0481
69.34.166.216,Denville,NJ,US,40.8841,-74.4863
69.41.174.196,Dallas,TX,US,32.8120,-96.8143
69.56.173.86,Dallas,TX,US,32.7825,-96.8207
69.57.148.142,Houston,TX,US,29.9342,-95.4057
69.88.231.232,Tacoma,WA,US,47.2626,-122.4413
69.90.109.247,Richmond,BC,CA,49.1667,-122.9667
69.93.121.162,Dallas,TX,US,32.7825,-96.8207
69.93.127.87,Dallas,TX,US,32.7825,-96.8207
70.101.164.134,Houston,TX,US,29.7755,-95.4152
70.110.70.238,Valrico,FL,US,27.9158,-82.2290
70.124.25.84,Palm Harbor,FL,US,28.0901,-82.7251
70.128.42.34,Little Rock,AR,US,34.7338,-92.3665
70.129.55.216,Houston,TX,US,29.7755,-95.4152
70.130.181.234,Saint Louis,MO,US,38.6385,-90.3026
70.133.145.225,Dallas,TX,US,32.7791,-96.8028
70.157.53.151,Augusta,GA,US,33.4393,-82.0512
70.160.183.40,Spring,TX,US,30.1145,-95.4729
70.162.81.229,Mesa,AZ,US,33.4253,-111.7273
70.167.192.250,Atlanta,GA,US,33.8767,-84.3342
70.176.140.197,Phoenix,AZ,US,33.5222,-112.0839
70.181.241.192,Escondido,CA,US,33.1349,-117.0416
70.190.182.173,Scottsdale,AZ,US,33.5984,-111.8669
70.20.57.202,,,US,38.0000,-97.0000
70.236.219.137,Annapolis,MD,US,38.9861,-76.5137
70.238.175.182,Saint Louis,MO,US,38.6385,-90.3026
70.240.176.209,Houston,TX,US,29.7755,-95.4152
70.45.56.242,,,PR,18.2500,-66.5000
70.50.0.53,Ottawa,ON,CA,45.4167,-75.7000
70.51.123.221,Toronto,ON,CA,43.6667,-79.4168
70.51.184.16,Pierrefonds,QC,CA,45.4667,-73.8833
70.63.156.102,,NC,US,35.6442,-79.8266
70.80.131.48,Montral,QC,CA,45.5000,-73.5833
70.83.10.158,Halifax,NS,CA,44.6500,-63.6000
70.84.114.153,Dallas,TX,US,32.7825,-96.8207
70.85.16.127,Dallas,TX,US,32.7825,-96.8207
70.86.138.210,Dallas,TX,US,32.7825,-96.8207
71.11.144.206,Saint Louis,MO,US,38.6385,-90.3026
71.111.248.186,,,US,38.0000,-97.0000
71.112.1.63,Bothell,WA,US,47.7953,-122.2018
71.116.76.63,San Jose,CA,US,37.3073,-121.8569
71.129.40.18,San Diego,CA,US,32.7977,-117.1322
71.141.192.136,San Francisco,CA,US,37.7645,-122.4294
71.162.144.139,,,US,38.0000,-97.0000
71.179.166.230,,,US,38.0000,-97.0000
71.197.166.180,Atlantic Beach,FL,US,30.3607,-81.4262
71.197.28.33,Detroit,MI,US,42.3662,-83.1015
71.199.226.121,,,US,38.0000,-97.0000
71.215.154.165,Denver,CO,US,39.7525,-104.9995
71.225.61.184,Blue Bell,PA,US,40.1576,-75.2757
71.227.0.13,Indianapolis,IN,US,39.8062,-86.1407
71.228.91.0,,,US,38.0000,-97.0000
71.232.250.68,,,US,38.0000,-97.0000
71.236.131.80,,OR,US,44.6044,-122.1155
71.236.166.71,,OR,US,44.6044,-122.1155
71.236.230.160,,OR,US,44.6044,-122.1155
71.240.75.2,Norfolk,VA,US,36.8861,-76.2668
71.28.231.114,Elizabethtown,KY,US,37.7153,-85.8565
71.32.5.248,Denver,CO,US,39.7525,-104.9995
71.42.46.180,Herndon,VA,US,38.9266,-77.3937
71.80.27.17,Cleveland,TN,US,35.1468,-84.8710
71.83.124.90,Bozeman,MT,US,45.7115,-111.0563
72.1.154.66,Olathe,KS,US,38.8686,-94.8344
72.1.217.148,Ottawa,ON,CA,45.4167,-75.7000
72.128.43.18,Kansas City,MO,US,39.1024,-94.5502
72.130.183.198,Herndon,VA,US,38.9266,-77.3937
72.147.54.227,,,US,38.0000,-97.0000
72.148.54.247,,,US,38.0000,-97.0000
72.15.233.132,Charlotte,NC,US,35.2060,-80.8290
72.160.105.204,Monroe,LA,US,32.5206,-92.1066
72.193.22.68,Vancouver,WA,US,45.6676,-122.6063
72.201.57.119,Atlanta,GA,US,33.8767,-84.3342
72.204.33.195,Atlanta,GA,US,33.8767,-84.3342
72.208.67.77,Atlanta,GA,US,33.8767,-84.3342
72.22.92.63,Santa Monica,CA,US,34.0119,-118.4682
72.225.234.118,New York,NY,US,40.7619,-73.9763
72.226.235.52,Branford,CT,US,41.2864,-72.7956
72.29.105.147,Carson City,NV,US,39.1496,-119.7178
72.36.239.30,Dallas,TX,US,32.9988,-96.7831
72.43.122.119,Chapel Hill,NC,US,35.9098,-79.0782
72.5.28.193,Newton Highlands,MA,US,42.3169,-71.2082
72.53.5.20,Calgary,AB,CA,51.0833,-114.0833
72.53.58.70,Calgary,AB,CA,51.0833,-114.0833
72.55.153.154,UNKNOWN
72.64.0.100,,,US,38.0000,-97.0000
72.8.103.205,UNKNOWN
72.81.214.109,,,US,38.0000,-97.0000
72.9.108.50,Great River,NY,US,40.7263,-73.1577
74.100.7.19,,,CA,60.0000,-95.0000
74.119.238.80,,,CA,60.0000,-95.0000
74.120.203.162,,,CA,60.0000,-95.0000
74.131.6.36,Louisville,KY,US,38.2552,-85.5459
74.134.92.57,Louisville,KY,US,38.2552,-85.5459
74.173.50.215,UNKNOWN
74.222.211.186,UNKNOWN
74.229.201.181,,,US,38.0000,-97.0000
74.69.33.85,,NY,US,42.1436,-74.9306
74.70.30.110,,NY,US,42.1436,-74.9306
74.97.155.75,,,CA,60.0000,-95.0000
75.111.235.5,Tyler,TX,US,32.3180,-95.2921
75.14.59.81,Dallas,TX,US,32.7791,-96.8028
75.161.136.251,UNKNOWN
75.36.234.124,Dallas,TX,US,32.7791,-96.8028
75.45.80.157,Dallas,TX,US,32.7791,-96.8028
75.5.226.71,Kalamazoo,MI,US,42.2899,-85.5883
75.51.57.169,UNKNOWN
75.55.112.14,UNKNOWN
75.58.103.3,UNKNOWN
75.58.57.132,UNKNOWN
75.61.108.179,UNKNOWN
75.67.157.72,,,US,38.0000,-97.0000
75.68.195.189,,,US,38.0000,-97.0000
75.73.50.3,,,US,38.0000,-97.0000
75.75.126.57,,,US,38.0000,-97.0000
76.105.128.69,UNKNOWN
76.105.225.71,UNKNOWN
76.170.83.56,Herndon,VA,US,38.9266,-77.3937
76.178.168.145,Herndon,VA,US,38.9266,-77.3937
76.20.220.233,,,US,38.0000,-97.0000
76.209.225.117,UNKNOWN
76.64.49.112,UNKNOWN
76.79.72.82,UNKNOWN
76.83.101.176,UNKNOWN
77.123.150.99,UNKNOWN
77.129.115.108,UNKNOWN
77.131.84.163,UNKNOWN
77.176.244.133,UNKNOWN
77.177.22.48,UNKNOWN
77.180.47.162,UNKNOWN
77.180.64.181,UNKNOWN
77.181.87.247,UNKNOWN
77.182.23.136,UNKNOWN
77.216.44.44,UNKNOWN
77.5.31.98,UNKNOWN
77.57.26.53,UNKNOWN
77.65.144.81,UNKNOWN
78.47.226.66,UNKNOWN
78.49.187.224,UNKNOWN
78.62.86.70,UNKNOWN
79.8.115.245,UNKNOWN
80.108.1.149,Vienna,09,AT,48.2000,16.3667
80.108.2.141,Vienna,09,AT,48.2000,16.3667
80.108.43.194,Vienna,09,AT,48.2000,16.3667
80.109.167.200,Innsbruck,07,AT,47.2667,11.4000
80.121.57.247,Vienna,09,AT,48.2000,16.3667
80.126.165.90,Amsterdam,07,NL,52.3500,4.9167
80.133.110.241,Velbert,07,DE,51.3333,7.0500
80.133.73.189,Ratingen,07,DE,51.3000,6.8500
80.138.92.218,Frankfurt Am Main,05,DE,50.1167,8.6833
80.142.69.172,Frankfurt,05,DE,50.1167,8.6833
80.144.142.246,Scharrhof,08,DE,49.3500,7.5500
80.145.203.217,Oldenburg,06,DE,53.1667,8.2000
80.163.43.123,Odense,04,DK,55.4000,10.3833
80.165.226.202,Aalborg,07,DK,57.0500,9.9333
80.168.224.11,London,P5,GB,51.5000,-0.1167
80.170.61.176,Tartaras,B9,FR,45.5500,4.6667
80.171.114.66,Hamburg,04,DE,53.5500,10.0000
80.171.14.143,Ohlsdorf,04,DE,53.6167,10.0333
80.171.61.82,Graft,04,DE,53.5167,9.8833
80.171.7.110,Graft,04,DE,53.5167,9.8833
80.176.148.26,London,P5,GB,51.5000,-0.1167
80.190.230.120,,,DE,51.0000,9.0000
80.190.241.118,,,DE,51.0000,9.0000
80.190.243.158,,,DE,51.0000,9.0000
80.190.250.108,,,DE,51.0000,9.0000
80.202.55.146,Oslo,12,NO,59.9167,10.7500
80.203.248.68,Bergen,07,NO,60.3911,5.3247
80.203.49.81,Stavanger,14,NO,58.9667,5.7500
80.212.84.117,Ytre Okslia,09,NO,67.1500,14.3333
80.219.249.40,Zrich,25,CH,47.3667,8.5500
80.219.250.158,Ksern,08,CH,47.0000,8.9333
80.219.35.224,Zrich,25,CH,47.3667,8.5500
80.221.63.227,Gamlas,13,FI,60.2394,24.8878
80.222.209.62,Helsinki,13,FI,60.1756,24.9342
80.222.65.173,Helsinki,13,FI,60.1756,24.9342
80.223.106.128,Kuopio,14,FI,62.9000,27.6833
80.229.7.209,,,GB,54.0000,-2.0000
80.237.156.59,Koeln,07,DE,50.9333,6.9500
80.237.173.67,Koeln,07,DE,50.9333,6.9500
80.237.200.9,Koeln,07,DE,50.9333,6.9500
80.242.195.68,Frenkendorf,01,CH,47.5000,7.7167
80.248.248.184,Espoo,13,FI,60.2167,24.6667
80.248.254.68,Espoo,13,FI,60.2167,24.6667
80.25.128.222,Madrid,29,ES,40.4000,-3.6833
80.251.122.132,Moscow,48,RU,55.7522,37.6156
80.252.209.6,Gteborg,28,SE,57.7167,11.9667
80.48.203.67,Terespol,53,PL,52.0833,16.3000
80.56.237.114,The Hague,11,NL,52.0833,4.3000
80.68.125.111,Vgen,22,SE,59.5167,14.3000
80.68.85.45,York,Q5,GB,53.9667,-1.0833
80.86.174.49,Wuppertal,07,DE,51.2667,7.1833
80.9.141.219,Orlans,A3,FR,47.9167,1.9000
80.92.122.238,Hall,06,AT,47.6000,14.4500
81.0.225.29,Prague,52,CZ,50.0833,14.4667
81.0.246.9,Prague,52,CZ,50.0833,14.4667
81.10.180.172,Linz,04,AT,48.3000,14.3000
81.106.199.165,Alfreton,D3,GB,53.1000,-1.3833
81.110.78.139,Leatherhead,B8,GB,51.2833,-0.3167
81.155.111.72,Welling,A6,GB,51.4500,0.1000
81.169.133.125,Berlin,16,DE,52.5167,13.4000
81.169.136.161,Berlin,16,DE,52.5167,13.4000
81.169.137.115,Berlin,16,DE,52.5167,13.4000
81.169.137.209,Berlin,16,DE,52.5167,13.4000
81.169.155.246,Berlin,16,DE,52.5167,13.4000
81.169.156.213,Berlin,16,DE,52.5167,13.4000
81.169.156.7,Berlin,16,DE,52.5167,13.4000
81.169.157.6,Berlin,16,DE,52.5167,13.4000
81.169.158.102,Berlin,16,DE,52.5167,13.4000
81.169.168.142,Berlin,16,DE,52.5167,13.4000
81.169.168.22,Berlin,16,DE,52.5167,13.4000
81.169.168.60,Berlin,16,DE,52.5167,13.4000
81.169.171.90,Berlin,16,DE,52.5167,13.4000
81.169.173.120,Berlin,16,DE,52.5167,13.4000
81.169.173.134,Berlin,16,DE,52.5167,13.4000
81.169.174.124,Berlin,16,DE,52.5167,13.4000
81.169.183.122,Berlin,16,DE,52.5167,13.4000
81.169.183.77,Berlin,16,DE,52.5167,13.4000
81.169.186.185,Berlin,16,DE,52.5167,13.4000
81.169.186.252,Berlin,16,DE,52.5167,13.4000
81.173.235.56,Hrth,07,DE,50.8667,6.8667
81.190.198.94,Gdynia,31,PL,54.5000,18.5500
81.197.100.57,Helsinki,13,FI,60.1756,24.9342
81.208.101.62,Milano,09,IT,45.4667,9.2000
81.216.158.19,Nora,26,SE,59.3167,18.5500
81.219.244.211,Warszawa,67,PL,52.2500,21.0000
81.220.85.19,Toulouse,B3,FR,43.6000,1.4333
81.227.239.183,,,SE,62.0000,15.0000
81.227.86.210,,,SE,62.0000,15.0000
81.233.3.224,,,SE,62.0000,15.0000
81.42.148.113,Aracena,51,ES,37.8833,-6.5500
81.56.235.34,Pont Du Loup,B8,FR,43.7167,7.0000
81.56.238.202,Paris,A8,FR,48.8667,2.3333
81.56.76.118,Arcueil,A8,FR,48.8000,2.3333
81.57.208.135,Gonesse,A8,FR,48.9833,2.4500
81.57.229.242,Paris,A8,FR,48.8667,2.3333
81.57.40.124,Paris,A8,FR,48.8667,2.3333
81.65.70.116,Paris,A8,FR,48.8667,2.3333
81.71.21.172,Heemskerk,07,NL,52.5167,4.6667
81.88.14.199,Muggebo,16,SE,58.1500,15.6333
81.96.187.26,Horley,A7,GB,52.0833,-1.3833
82.10.187.218,Compton Abbas,D6,GB,50.7333,-2.6167
82.101.219.246,Amsterdam,07,NL,52.3500,4.9167
82.103.132.227,,,DK,56.0000,10.0000
82.103.133.88,,,DK,56.0000,10.0000
82.118.210.65,,,FI,64.0000,26.0000
82.126.116.24,ragny,A8,FR,49.0167,2.1000
82.128.190.114,Oulu,08,FI,65.0167,25.4667
82.135.4.187,Munich,02,DE,48.1500,11.5833
82.135.5.220,Munich,02,DE,48.1500,11.5833
82.135.71.193,Munich,02,DE,48.1500,11.5833
82.146.73.51,Ofte,19,NO,58.1833,6.8000
82.149.72.85,Heroldsberg,02,DE,49.5339,11.1556
82.150.138.109,Groningen,04,NL,53.2167,6.5500
82.165.144.169,,OH,US,40.3914,-82.7526
82.165.180.112,,OH,US,40.3914,-82.7526
82.165.184.7,,OH,US,40.3914,-82.7526
82.171.69.175,Rijswijk,11,NL,52.0167,4.3333
82.172.14.79,Rijnsburg,11,NL,52.1833,4.4500
82.173.189.74,Rotterdam,11,NL,51.9167,4.5000
82.182.109.115,Mlnlycke,28,SE,57.6500,12.1333
82.182.15.84,Sdertlje,26,SE,59.2000,17.6167
82.182.59.155,Nacka,24,SE,62.4739,17.4161
82.19.248.115,Bournemouth,B2,GB,50.7167,-1.8833
82.199.205.254,Sofia,42,BG,42.6833,23.3167
82.207.1.72,Kiev,13,UA,50.4333,30.5167
82.208.160.36,Braila,08,RO,45.2667,27.9832
82.21.60.203,London,H1,GB,51.5000,-0.1167
82.210.142.40,Warsaw,67,PL,52.2500,21.0000
82.214.2.226,Gteborg,28,SE,57.7167,11.9667
82.216.67.187,Paris,A8,FR,48.8667,2.3333
82.225.144.232,Paris,A8,FR,48.8667,2.3333
82.225.192.198,Maisons-Alfort,A8,FR,48.8000,2.4333
82.226.84.53,Rosny,A7,FR,49.0000,1.6333
82.227.101.236,Montpellier,A9,FR,43.6000,3.8833
82.227.12.18,Taverny,A8,FR,49.0333,2.2167
82.228.101.7,Lyon,B9,FR,45.7500,4.8500
82.228.20.246,Paris,A8,FR,48.8667,2.3333
82.228.218.46,Saint-Mand,A8,FR,48.8333,2.4167
82.228.252.20,ragny,A8,FR,49.0167,2.1000
82.229.84.252,Beauvais,B6,FR,49.4333,2.0833
82.231.111.160,Pont Du Loup,B8,FR,43.7167,7.0000
82.231.59.44,Saint-Mand,A8,FR,48.8333,2.4167
82.231.61.186,Paris,A8,FR,48.8667,2.3333
82.233.236.81,Entremont,B9,FR,45.4333,5.8833
82.234.204.192,Beauvais,B6,FR,49.4333,2.0833
82.236.48.236,Lille,B4,FR,50.6333,3.0667
82.237.210.200,Bezons,A8,FR,48.9333,2.2167
82.238.198.196,Gonfaron,B8,FR,43.3167,6.2833
82.240.206.88,Rennes,A2,FR,48.0833,-1.6833
82.240.214.49,Rennes,A2,FR,48.0833,-1.6833
82.240.72.48,Orlans,A3,FR,47.9167,1.9000
82.241.115.49,Saverne,C1,FR,48.7333,7.3667
82.241.93.120,Paris,A8,FR,48.8667,2.3333
82.244.46.148,Dijon,A1,FR,47.3167,5.0167
82.245.214.104,Paris,A8,FR,48.8667,2.3333
82.247.153.205,Paris,A8,FR,48.8667,2.3333
82.247.33.105,Paris,A8,FR,48.8667,2.3333
82.247.82.223,Paris,A8,FR,48.8667,2.3333
82.249.121.65,Paris,A8,FR,48.8667,2.3333
82.249.254.123,Vougeot,A1,FR,47.1667,4.9667
82.250.164.196,Marly-sur-Seille,B2,FR,49.0667,6.1500
82.250.84.177,Nantes,B5,FR,47.2167,-1.5500
82.252.136.30,Ivry-sur-Seine,A8,FR,48.8167,2.3833
82.253.227.151,Orgeval,B6,FR,49.5167,3.7000
82.32.73.70,Wormleighton,P3,GB,52.1833,-1.3500
82.33.45.32,,,GB,54.0000,-2.0000
82.43.196.208,,,GB,54.0000,-2.0000
82.43.96.136,Stevenage,I9,GB,51.9167,-0.2167
82.49.95.122,Roma,07,IT,41.9000,12.4832
82.53.86.11,Roma,07,IT,41.9000,12.4832
82.54.207.221,Roma,07,IT,41.9000,12.4832
82.59.80.75,Roma,07,IT,41.9000,12.4832
82.6.104.255,,,GB,54.0000,-2.0000
82.66.92.71,Tartaras,B9,FR,45.5500,4.6667
82.76.242.25,Bucharest,10,RO,44.4333,26.1000
82.77.101.170,Budapest,05,HU,47.5000,19.0833
82.82.116.207,Mnchengladbach,07,DE,51.2000,6.4333
82.82.64.226,Eschborn,05,DE,50.1333,8.5500
82.83.224.96,Eschborn,05,DE,50.1333,8.5500
82.84.168.60,Cagliari,14,IT,39.2167,9.1167
82.92.197.115,Amsterdam,07,NL,52.3500,4.9167
82.93.130.253,Rotterdam,11,NL,51.9167,4.5000
82.93.181.15,Amsterdam,07,NL,52.3500,4.9167
82.94.251.206,Amsterdam,07,NL,52.3500,4.9167
82.95.236.50,Amsterdam,07,NL,52.3500,4.9167
82.95.239.45,Amsterdam,07,NL,52.3500,4.9167
82.99.212.175,Iran,03,IR,32.0922,51.0289
83.113.188.31,Toulon,B8,FR,43.1167,5.9333
83.125.32.209,Bocholt,07,DE,51.8333,6.6000
83.125.33.127,Bocholt,07,DE,51.8333,6.6000
83.125.40.111,,,EU,47.0000,8.0000
83.133.125.189,Hausham,02,DE,47.7500,11.8500
83.134.139.16,Leuven,12,BE,50.8833,4.7000
83.135.213.119,Stuttgart,01,DE,48.7667,9.1833
83.135.70.0,Bochum,07,DE,51.4833,7.2167
83.140.180.23,Stockholm,26,SE,59.3333,18.0500
83.142.221.25,Bedzin,35,PL,50.3333,19.1500
83.148.114.19,,,BG,43.0000,25.0000
83.149.231.208,Moscow,48,RU,55.7522,37.6156
83.151.29.12,,,DE,51.0000,9.0000
83.16.228.227,Bobolice,29,PL,50.6167,19.5000
83.160.194.169,Rotterdam,11,NL,51.9167,4.5000
83.168.118.109,Szczecin,87,PL,53.4167,14.5833
83.171.147.18,Bochum,07,DE,51.4833,7.2167
83.171.159.38,,,DE,51.0000,9.0000
83.171.159.7,,,DE,51.0000,9.0000
83.171.168.84,,,DE,51.0000,9.0000
83.171.188.2,,,DE,51.0000,9.0000
83.184.253.120,,,IT,42.8333,12.8333
83.196.36.244,Nancy,B2,FR,48.6833,6.2000
83.212.51.46,Ptra,38,GR,38.2444,21.7344
83.216.204.134,Vienna,09,AT,48.2000,16.3667
83.218.175.99,Imst,07,AT,47.2333,10.7332
83.219.212.101,Malm,27,SE,55.6000,13.0000
83.228.112.250,Sofia,42,BG,42.6833,23.3167
83.228.184.208,Pully,23,CH,46.5167,6.6500
83.233.144.246,,,SE,62.0000,15.0000
83.237.229.23,Moscow,48,RU,55.7522,37.6156
83.24.130.47,Warsaw,67,PL,52.2500,21.0000
83.240.24.205,Brno,78,CZ,49.2000,16.6333
83.245.236.91,,,FI,64.0000,26.0000
83.246.118.110,Hannver,06,DE,53.1833,8.5167
83.246.64.164,Hannver,06,DE,53.1833,8.5167
83.246.72.228,Hannver,06,DE,53.1833,8.5167
83.246.94.31,Hannver,06,DE,53.1833,8.5167
83.248.101.153,Stockholm,26,SE,59.3333,18.0500
83.249.227.10,Stockholm,26,SE,59.3333,18.0500
83.255.196.44,Strand,10,SE,60.4833,15.7332
83.26.59.203,Lodz,53,PL,52.2667,16.7500
83.28.38.19,Lublin,75,PL,51.2500,22.5667
83.50.54.95,Madrid,29,ES,40.4000,-3.6833
83.6.87.11,Warszawa,67,PL,52.2500,21.0000
83.64.118.186,Wien,09,AT,48.2000,16.3667
83.64.208.20,Lofer,05,AT,47.5833,12.6833
83.67.143.62,Stoke Mandeville,B9,GB,51.7833,-0.7833
83.70.200.103,Dublin,07,IE,53.3331,-6.2489
84.100.139.126,Toulouse,B3,FR,43.6000,1.4333
84.101.249.95,Arbis,97,FR,44.6667,-0.2500
84.107.147.141,Utrecht,09,NL,52.0833,5.1333
84.107.167.247,Utrecht,09,NL,52.0833,5.1333
84.113.155.16,,,SE,62.0000,15.0000
84.129.249.28,Bochum,07,DE,51.4833,7.2167
84.131.137.54,Wennigsen,06,DE,52.2667,9.5833
84.132.186.111,Berlin,16,DE,52.5167,13.4000
84.134.82.179,Essen,07,DE,51.4500,7.0167
84.141.101.17,Kiel,10,DE,54.3333,10.1333
84.141.173.148,Hamburg,04,DE,53.5500,10.0000
84.143.141.36,Nrnberg,02,DE,49.4478,11.0683
84.144.161.8,,,DE,51.0000,9.0000
84.145.110.29,Cologne,07,DE,50.9333,6.9500
84.147.190.29,,,DE,51.0000,9.0000
84.147.202.193,Hamburg,04,DE,53.5500,10.0000
84.149.204.235,Grnwald,02,DE,48.0500,11.5167
84.150.91.237,Wennigsen,06,DE,52.2667,9.5833
84.154.194.232,Dorndorf,15,DE,50.7833,11.4500
84.157.132.218,Waiblingen,01,DE,48.8333,9.3000
84.159.118.16,Mnchengladbach,07,DE,51.2000,6.4333
84.16.226.24,Frankfurt,05,DE,50.1167,8.6833
84.16.229.137,Frankfurt,05,DE,50.1167,8.6833
84.16.233.47,Frankfurt,05,DE,50.1167,8.6833
84.16.234.128,Frankfurt,05,DE,50.1167,8.6833
84.16.234.49,Frankfurt,05,DE,50.1167,8.6833
84.16.236.173,Frankfurt,05,DE,50.1167,8.6833
84.16.238.147,Frankfurt,05,DE,50.1167,8.6833
84.16.238.86,Frankfurt,05,DE,50.1167,8.6833
84.16.245.68,Frankfurt,05,DE,50.1167,8.6833
84.16.249.198,Frankfurt,05,DE,50.1167,8.6833
84.161.131.227,Waiblingen,01,DE,48.8333,9.3000
84.162.97.22,,,DE,51.0000,9.0000
84.165.73.75,Hamburg,04,DE,53.5500,10.0000
84.167.119.66,Bochum,07,DE,51.4833,7.2167
84.169.109.172,Eltville,05,DE,50.0333,8.1167
84.177.24.240,Ginsheim-Gustavsburg,05,DE,49.9858,8.3425
84.179.252.221,Dresden,13,DE,51.0500,13.7500
84.180.48.190,,,DE,51.0000,9.0000
84.181.66.18,,,DE,51.0000,9.0000
84.184.143.17,Bochum,07,DE,51.4833,7.2167
84.19.177.90,Erfurt,15,DE,50.9833,11.0333
84.19.181.66,Erfurt,15,DE,50.9833,11.0333
84.19.182.23,Erfurt,15,DE,50.9833,11.0333
84.191.96.139,Berlin,16,DE,52.5167,13.4000
84.220.115.17,Sabbioncello,20,IT,45.3667,11.9832
84.221.196.201,Cagliari,14,IT,39.2167,9.1167
84.221.197.117,Cagliari,14,IT,39.2167,9.1167
84.244.189.19,Rotterdam,11,NL,51.9167,4.5000
84.26.115.1,Nijmegen,03,NL,51.8333,5.8667
84.38.64.155,,,DE,51.0000,9.0000
84.40.199.218,Wroclaw,72,PL,51.1000,17.0333
84.40.207.70,Wroclaw,72,PL,51.1000,17.0333
84.41.177.144,Almere,16,NL,52.3667,5.1500
84.44.211.166,Hrth,07,DE,50.8667,6.8667
84.46.0.7,Norderstedt,10,DE,53.7000,10.0167
84.51.135.171,Sheffield,L9,GB,53.3667,-1.5000
84.56.26.190,Munich,02,DE,48.1500,11.5833
84.57.236.39,Eschborn,05,DE,50.1333,8.5500
84.57.98.213,Kabel,07,DE,51.4000,7.4832
84.58.130.207,Bingen Am Rhein,08,DE,49.9667,7.9000
84.58.140.71,Ginsheim-Gustavsburg,05,DE,49.9858,8.3425
84.58.164.137,Mainz,08,DE,50.0000,8.2711
84.58.222.75,Eschborn,05,DE,50.1333,8.5500
84.59.97.158,Eschborn,05,DE,50.1333,8.5500
84.60.24.26,Leithe,07,DE,51.4667,7.1167
84.62.171.29,Eschborn,05,DE,50.1333,8.5500
84.62.8.212,Dsseldorf,07,DE,51.2167,6.7667
84.73.173.24,Hnenberg,24,CH,47.1667,8.4167
84.73.183.152,Pully,23,CH,46.5167,6.6500
84.73.20.236,Effretikon,25,CH,47.4333,8.6833
84.75.209.86,Zrich,25,CH,47.3667,8.5500
84.75.246.166,Zrich,25,CH,47.3667,8.5500
84.75.65.248,Zrich,25,CH,47.3667,8.5500
84.85.160.44,Amersfoort,09,NL,52.1500,5.3833
85.10.192.137,Gunzenhausen,02,DE,49.1000,10.7500
85.10.198.236,Gunzenhausen,02,DE,49.1000,10.7500
85.10.200.47,Gunzenhausen,02,DE,49.1000,10.7500
85.10.225.4,Gunzenhausen,02,DE,49.1000,10.7500
85.10.240.250,Gunzenhausen,02,DE,49.1000,10.7500
85.114.128.112,,,DE,51.0000,9.0000
85.114.130.50,,,DE,51.0000,9.0000
85.115.168.138,Yekaterinburg,71,RU,56.8500,60.6000
85.119.156.72,Warendorf,07,DE,51.9500,7.9832
85.119.158.191,Homburg,09,DE,49.3167,7.3333
85.124.36.94,Vienna,09,AT,48.2000,16.3667
85.132.24.109,Baku,09,AZ,40.3953,49.8822
85.14.217.51,Coburg,02,DE,50.2500,10.9667
85.140.205.79,Moscow,48,RU,55.7522,37.6156
85.141.66.217,Moscow,48,RU,55.7522,37.6156
85.145.184.81,Amsterdam,07,NL,52.3500,4.9167
85.176.134.208,Seevetal,06,DE,53.4000,9.9667
85.176.203.186,Hamburg,04,DE,53.5500,10.0000
85.176.231.187,Hamburg,04,DE,53.5500,10.0000
85.176.65.16,Hamburg,04,DE,53.5500,10.0000
85.176.92.8,Hamburg,04,DE,53.5500,10.0000
85.177.166.213,Hamburg,04,DE,53.5500,10.0000
85.177.2.161,Hamburg,04,DE,53.5500,10.0000
85.177.225.113,Hamburg,04,DE,53.5500,10.0000
85.178.106.73,Berlin,16,DE,52.5167,13.4000
85.178.66.63,Berlin,16,DE,52.5167,13.4000
85.178.89.24,Berlin,16,DE,52.5167,13.4000
85.179.125.64,Hamburg,04,DE,53.5500,10.0000
85.179.8.203,Hamburg,04,DE,53.5500,10.0000
85.18.107.240,Padova,20,IT,45.4167,11.8833
85.180.68.132,Hamburg,04,DE,53.5500,10.0000
85.180.73.26,Hamburg,04,DE,53.5500,10.0000
85.181.95.158,Mainz,08,DE,50.0000,8.2711
85.186.13.252,Marius,32,RO,47.6667,23.1833
85.187.152.189,Sofia,42,BG,42.6833,23.3167
85.187.158.179,Sofia,42,BG,42.6833,23.3167
85.193.8.34,Klasterec Nad Ohri,89,CZ,50.3833,13.1500
85.2.179.80,Zrich,25,CH,47.3667,8.5500
85.204.85.4,Giurgiu,42,RO,43.8833,25.9667
85.21.246.152,Saint Petersburg,66,RU,59.8944,30.2642
85.211.71.137,Oxford,K2,GB,51.7500,-1.2500
85.214.17.144,Berlin,16,DE,52.5167,13.4000
85.214.18.16,Berlin,16,DE,52.5167,13.4000
85.214.24.183,Berlin,16,DE,52.5167,13.4000
85.214.26.150,Berlin,16,DE,52.5167,13.4000
85.214.29.10,Berlin,16,DE,52.5167,13.4000
85.214.29.33,Berlin,16,DE,52.5167,13.4000
85.214.29.61,Berlin,16,DE,52.5167,13.4000
85.214.36.108,Berlin,16,DE,52.5167,13.4000
85.214.38.21,Berlin,16,DE,52.5167,13.4000
85.214.41.167,Berlin,16,DE,52.5167,13.4000
85.214.50.115,Berlin,16,DE,52.5167,13.4000
85.214.54.254,Berlin,16,DE,52.5167,13.4000
85.214.57.226,Berlin,16,DE,52.5167,13.4000
85.214.63.253,Berlin,16,DE,52.5167,13.4000
85.214.66.10,Berlin,16,DE,52.5167,13.4000
85.214.66.61,Berlin,16,DE,52.5167,13.4000
85.214.68.105,Berlin,16,DE,52.5167,13.4000
85.214.68.148,Berlin,16,DE,52.5167,13.4000
85.214.68.60,Berlin,16,DE,52.5167,13.4000
85.214.69.239,Berlin,16,DE,52.5167,13.4000
85.214.72.37,Berlin,16,DE,52.5167,13.4000
85.214.78.217,Berlin,16,DE,52.5167,13.4000
85.214.83.203,Berlin,16,DE,52.5167,13.4000
85.214.85.116,Berlin,16,DE,52.5167,13.4000
85.214.90.235,Berlin,16,DE,52.5167,13.4000
85.214.91.152,Berlin,16,DE,52.5167,13.4000
85.214.91.190,Berlin,16,DE,52.5167,13.4000
85.214.94.149,Berlin,16,DE,52.5167,13.4000
85.214.95.137,Berlin,16,DE,52.5167,13.4000
85.214.95.75,Berlin,16,DE,52.5167,13.4000
85.216.31.195,Baden,01,DE,48.7500,8.2500
85.225.13.0,Stockholm,26,SE,59.3333,18.0500
85.225.171.211,,,SE,62.0000,15.0000
85.227.202.122,,,SE,62.0000,15.0000
85.228.189.100,,,SE,62.0000,15.0000
85.228.74.108,Tumba,26,SE,59.2000,17.8167
85.233.44.120,Seevetal,06,DE,53.4000,9.9667
85.234.130.43,London,P5,GB,51.5000,-0.1167
85.234.136.20,,,GB,54.0000,-2.0000
85.234.144.236,,,GB,54.0000,-2.0000
85.243.25.32,Lisboa,14,PT,38.7167,-9.1333
85.25.130.195,,,DE,51.0000,9.0000
85.25.132.119,,,DE,51.0000,9.0000
85.25.136.235,,,DE,51.0000,9.0000
85.25.138.205,,,DE,51.0000,9.0000
85.25.138.220,,,DE,51.0000,9.0000
85.25.141.60,,,DE,51.0000,9.0000
85.25.144.94,,,DE,51.0000,9.0000
85.25.146.77,,,DE,51.0000,9.0000
85.25.148.13,,,DE,51.0000,9.0000
85.25.20.175,,,DE,51.0000,9.0000
85.25.253.104,,,DE,51.0000,9.0000
85.25.5.64,,,DE,51.0000,9.0000
85.25.61.5,,,DE,51.0000,9.0000
85.25.62.36,,,DE,51.0000,9.0000
85.31.187.203,Jena,15,DE,50.9333,11.5833
85.31.187.84,Jena,15,DE,50.9333,11.5833
85.75.197.113,Sna,42,GR,36.8000,22.5000
85.8.136.101,Castletown,V3,GB,58.5833,-3.3833
85.84.33.31,Derio,59,ES,43.3000,-2.8667
85.88.6.170,Oberhausen,07,DE,51.4667,6.8500
85.89.179.43,Lodz,53,PL,52.2667,16.7500
85.93.3.104,Oldenburg,06,DE,53.1667,8.2000
86.106.254.231,Chisinau,48,MD,47.0056,28.8575
86.130.3.94,Warrington,P2,GB,53.3833,-2.6000
86.136.203.159,Leatherhead,B8,GB,51.2833,-0.3167
86.15.239.219,,,GB,54.0000,-2.0000
86.211.3.235,Nice,B8,FR,43.7000,7.2500
86.217.194.216,Bordeaux,97,FR,44.8333,-0.5667
86.33.232.99,,,AT,47.3333,13.3333
86.42.177.73,Dublin,07,IE,53.3331,-6.2489
86.49.49.126,Ceska,78,CZ,49.2833,16.5667
86.56.100.79,Hannver,06,DE,53.1833,8.5167
86.56.106.45,Hannver,06,DE,53.1833,8.5167
86.59.21.38,Klosterneuburg,03,AT,48.3000,16.3167
86.63.150.82,Lublin,75,PL,51.2500,22.5667
86.63.201.9,Ceska Lipa,83,CZ,50.6833,14.5500
86.71.5.81,Billancourt,B6,FR,49.7167,2.8833
86.76.72.109,Billancourt,B6,FR,49.7167,2.8833
86.88.140.156,Amersfoort,09,NL,52.1500,5.3833
87.102.80.216,Kingston,N1,GB,52.8500,-1.9000
87.105.192.100,Wroclaw,72,PL,51.1000,17.0333
87.105.217.149,Wroclaw,72,PL,51.1000,17.0333
87.106.27.17,Karlsruhe,01,DE,49.0047,8.3858
87.106.34.45,Karlsruhe,01,DE,49.0047,8.3858
87.106.4.7,Karlsruhe,01,DE,49.0047,8.3858
87.106.77.37,Karlsruhe,01,DE,49.0047,8.3858
87.106.79.175,Karlsruhe,01,DE,49.0047,8.3858
87.106.9.89,Karlsruhe,01,DE,49.0047,8.3858
87.108.34.217,,,FI,64.0000,26.0000
87.118.100.187,Erfurt,15,DE,50.9833,11.0333
87.118.110.163,Erfurt,15,DE,50.9833,11.0333
87.118.218.16,Moscow,48,RU,55.7522,37.6156
87.119.206.222,Steele,07,DE,51.4500,7.0833
87.120.199.10,Sofia,42,BG,42.6833,23.3167
87.122.5.21,Barmstedt,10,DE,53.7833,9.7667
87.13.64.22,Roma,07,IT,41.9000,12.4832
87.14.163.210,Roma,07,IT,41.9000,12.4832
87.14.234.199,Roma,07,IT,41.9000,12.4832
87.15.57.22,Roma,07,IT,41.9000,12.4832
87.155.94.40,,,DE,51.0000,9.0000
87.156.110.134,,,DE,51.0000,9.0000
87.16.123.60,Roma,07,IT,41.9000,12.4832
87.16.197.236,Roma,07,IT,41.9000,12.4832
87.160.200.213,,,DE,51.0000,9.0000
87.163.69.44,,,DE,51.0000,9.0000
87.166.34.26,,,DE,51.0000,9.0000
87.17.202.27,Roma,07,IT,41.9000,12.4832
87.175.217.142,,,DE,51.0000,9.0000
87.175.217.29,,,DE,51.0000,9.0000
87.175.79.128,,,DE,51.0000,9.0000
87.178.82.122,,,DE,51.0000,9.0000
87.178.99.145,,,DE,51.0000,9.0000
87.18.202.253,Roma,07,IT,41.9000,12.4832
87.187.74.112,,,DE,51.0000,9.0000
87.194.115.69,London,P5,GB,51.5000,-0.1167
87.194.61.194,London,P5,GB,51.5000,-0.1167
87.194.73.253,London,P5,GB,51.5000,-0.1167
87.20.130.66,Roma,07,IT,41.9000,12.4832
87.20.99.54,Roma,07,IT,41.9000,12.4832
87.204.26.205,Warszawa,67,PL,52.2500,21.0000
87.206.231.78,Krakw,77,PL,50.0833,19.9167
87.207.156.48,Opole,79,PL,50.6667,17.9500
87.226.14.228,Riga,25,LV,56.9500,24.1000
87.230.11.166,Koeln,07,DE,50.9333,6.9500
87.230.17.81,Hst,07,DE,51.6500,6.1833
87.230.18.148,Hst,07,DE,51.6500,6.1833
87.230.18.23,Hst,07,DE,51.6500,6.1833
87.230.20.231,Hst,07,DE,51.6500,6.1833
87.234.125.8,Koeln,07,DE,50.9333,6.9500
87.236.198.84,Praha,52,CZ,50.0833,14.4667
87.240.62.234,Moscow,48,RU,55.7522,37.6156
87.249.206.11,Wroclaw,72,PL,51.1000,17.0333
87.4.248.219,Strada,05,IT,44.3000,11.0333
87.68.206.112,,,IL,31.5000,34.7500
87.79.236.163,Koeln,07,DE,50.9333,6.9500
87.94.90.182,Tampere,15,FI,61.5000,23.7500
87.99.27.160,Wroclaw,72,PL,51.1000,17.0333
88.110.132.129,Warrington,P2,GB,53.3833,-2.6000
88.110.25.128,Harbury,P3,GB,52.2333,-1.4500
88.114.237.166,,,FI,64.0000,26.0000
88.114.54.58,,,FI,64.0000,26.0000
88.115.84.144,,,FI,64.0000,26.0000
88.118.241.93,Vilnius,65,LT,54.6833,25.3167
88.136.100.160,Paris,A8,FR,48.8667,2.3333
88.137.127.226,Paris,A8,FR,48.8667,2.3333
88.149.235.41,Settimo,12,IT,45.1500,7.7667
88.154.39.10,,,IL,31.5000,34.7500
88.157.70.125,Porto,17,PT,41.1500,-8.6167
88.157.84.247,Porto,17,PT,41.1500,-8.6167
88.160.179.6,Paris,A8,FR,48.8667,2.3333
88.161.54.214,Paris,A8,FR,48.8667,2.3333
88.162.149.207,Paris,A8,FR,48.8667,2.3333
88.167.176.33,Paris,A8,FR,48.8667,2.3333
88.168.152.11,Paris,A8,FR,48.8667,2.3333
88.168.4.99,Paris,A8,FR,48.8667,2.3333
88.191.13.5,Paris,A8,FR,48.8667,2.3333
88.191.13.68,Paris,A8,FR,48.8667,2.3333
88.191.14.223,Paris,A8,FR,48.8667,2.3333
88.191.16.100,Paris,A8,FR,48.8667,2.3333
88.191.19.192,Paris,A8,FR,48.8667,2.3333
88.191.19.68,Paris,A8,FR,48.8667,2.3333
88.191.23.111,Paris,A8,FR,48.8667,2.3333
88.191.24.77,Paris,A8,FR,48.8667,2.3333
88.191.26.157,Paris,A8,FR,48.8667,2.3333
88.191.28.23,Paris,A8,FR,48.8667,2.3333
88.191.33.169,Paris,A8,FR,48.8667,2.3333
88.191.36.249,Paris,A8,FR,48.8667,2.3333
88.191.37.194,Paris,A8,FR,48.8667,2.3333
88.191.38.143,Paris,A8,FR,48.8667,2.3333
88.191.51.214,Paris,A8,FR,48.8667,2.3333
88.195.69.49,,,FI,64.0000,26.0000
88.195.73.62,,,FI,64.0000,26.0000
88.198.107.93,Gunzenhausen,02,DE,49.1000,10.7500
88.198.109.123,Gunzenhausen,02,DE,49.1000,10.7500
88.198.11.5,Gunzenhausen,02,DE,49.1000,10.7500
88.198.127.245,Gunzenhausen,02,DE,49.1000,10.7500
88.198.14.249,Gunzenhausen,02,DE,49.1000,10.7500
88.198.160.123,Gunzenhausen,02,DE,49.1000,10.7500
88.198.164.126,Gunzenhausen,02,DE,49.1000,10.7500
88.198.169.99,Gunzenhausen,02,DE,49.1000,10.7500
88.198.175.78,Gunzenhausen,02,DE,49.1000,10.7500
88.198.178.190,Gunzenhausen,02,DE,49.1000,10.7500
88.198.180.62,Gunzenhausen,02,DE,49.1000,10.7500
88.198.192.154,Gunzenhausen,02,DE,49.1000,10.7500
88.198.201.230,Gunzenhausen,02,DE,49.1000,10.7500
88.198.206.70,Gunzenhausen,02,DE,49.1000,10.7500
88.198.25.20,Gunzenhausen,02,DE,49.1000,10.7500
88.198.252.126,Gunzenhausen,02,DE,49.1000,10.7500
88.198.37.146,Gunzenhausen,02,DE,49.1000,10.7500
88.198.43.207,Gunzenhausen,02,DE,49.1000,10.7500
88.198.45.235,Gunzenhausen,02,DE,49.1000,10.7500
88.198.47.72,Gunzenhausen,02,DE,49.1000,10.7500
88.198.59.34,Gunzenhausen,02,DE,49.1000,10.7500
88.198.67.4,Gunzenhausen,02,DE,49.1000,10.7500
88.198.9.235,Gunzenhausen,02,DE,49.1000,10.7500
88.198.90.110,Gunzenhausen,02,DE,49.1000,10.7500
88.198.95.67,Gunzenhausen,02,DE,49.1000,10.7500
88.208.203.85,Gloucester,E6,GB,51.8333,-2.2500
88.211.140.199,Almere,16,NL,52.3667,5.1500
88.215.115.130,Muenchen,02,DE,48.1500,11.5833
88.217.34.25,Muenchen,02,DE,48.1500,11.5833
88.217.35.62,Muenchen,02,DE,48.1500,11.5833
88.42.221.180,Montecchio Maggiore,20,IT,45.5000,11.4000
88.64.136.102,Eschborn,05,DE,50.1333,8.5500
88.65.252.3,Eschborn,05,DE,50.1333,8.5500
88.66.27.207,Eschborn,05,DE,50.1333,8.5500
88.70.85.176,Eschborn,05,DE,50.1333,8.5500
88.72.194.98,Eschborn,05,DE,50.1333,8.5500
88.72.201.38,Eschborn,05,DE,50.1333,8.5500
88.72.206.241,Eschborn,05,DE,50.1333,8.5500
88.73.105.85,Eschborn,05,DE,50.1333,8.5500
88.73.119.137,Eschborn,05,DE,50.1333,8.5500
88.73.159.16,Eschborn,05,DE,50.1333,8.5500
88.73.41.80,Eschborn,05,DE,50.1333,8.5500
88.73.94.62,Eschborn,05,DE,50.1333,8.5500
88.76.176.148,Eschborn,05,DE,50.1333,8.5500
88.76.250.147,Eschborn,05,DE,50.1333,8.5500
88.80.12.78,,,SE,62.0000,15.0000
88.84.142.165,Frankfurt,05,DE,50.1167,8.6833
88.84.154.90,Frankfurt,05,DE,50.1167,8.6833
88.84.155.37,Frankfurt,05,DE,50.1167,8.6833
88.88.230.120,Fornebu,01,NO,59.9022,10.6292
89.110.144.180,Montabaur,08,DE,50.4333,7.8333
89.110.147.209,Montabaur,08,DE,50.4333,7.8333
89.110.149.90,Montabaur,08,DE,50.4333,7.8333
89.110.156.179,Montabaur,08,DE,50.4333,7.8333
89.110.156.203,Montabaur,08,DE,50.4333,7.8333
89.110.157.31,Montabaur,08,DE,50.4333,7.8333
89.111.168.177,Moscow,48,RU,55.7522,37.6156
89.13.55.4,Karlsruhe,01,DE,49.0047,8.3858
89.133.16.43,Budapest,05,HU,47.5000,19.0833
89.138.105.135,Haifa,04,IL,32.8156,34.9892
89.14.86.115,UNKNOWN
89.145.19.143,Schwedt,11,DE,53.0667,14.3000
89.148.139.2,Fratte,06,IT,45.9081,12.7358
89.149.194.143,Frankfurt,05,DE,50.1167,8.6833
89.149.206.52,Frankfurt,05,DE,50.1167,8.6833
89.149.207.172,Frankfurt,05,DE,50.1167,8.6833
89.149.208.121,Frankfurt,05,DE,50.1167,8.6833
89.149.59.75,Bucharest,10,RO,44.4333,26.1000
89.15.41.45,UNKNOWN
89.150.202.174,Halmstad,06,SE,56.6714,12.8556
89.150.232.146,Halmstad,06,SE,56.6714,12.8556
89.152.128.115,Lisboa,14,PT,38.7167,-9.1333
89.159.17.187,,,FR,46.0000,2.0000
89.163.145.20,Coburg,02,DE,50.2500,10.9667
89.165.133.27,,,RO,46.0000,25.0000
89.170.10.244,Billancourt,B6,FR,49.7167,2.8833
89.178.0.53,Moscow,48,RU,55.7522,37.6156
89.179.246.38,Moscow,48,RU,55.7522,37.6156
89.190.215.162,Sofia,42,BG,42.6833,23.3167
89.210.118.213,Athens,35,GR,37.9833,23.7332
89.210.8.70,Athens,35,GR,37.9833,23.7332
89.228.252.27,Kalisz,34,PL,51.7500,18.0833
89.247.2.146,Stuttgart,01,DE,48.7667,9.1833
89.32.28.7,Curtea De Arges,39,RO,45.1333,24.6833
89.32.28.8,Curtea De Arges,39,RO,45.1333,24.6833
89.32.86.122,Bucuresti,10,RO,44.4333,26.1000
89.56.134.117,Kiel,10,DE,54.3333,10.1333
89.57.223.231,Kiel,10,DE,54.3333,10.1333
90.1.109.178,Lille,B4,FR,50.6333,3.0667
90.16.151.170,Paris,A8,FR,48.8667,2.3333
90.176.60.6,UNKNOWN
90.199.170.50,Ripe,E2,GB,50.8500,0.1333
90.21.154.198,Paris,A8,FR,48.8667,2.3333
90.38.96.152,Paris,A8,FR,48.8667,2.3333
90.41.217.11,Paris,A8,FR,48.8667,2.3333
90.8.236.66,Paris,A8,FR,48.8667,2.3333
91.0.92.60,,,DE,51.0000,9.0000
91.109.121.231,,,GB,54.0000,-2.0000
91.12.29.91,,,DE,51.0000,9.0000
91.12.41.185,,,DE,51.0000,9.0000
91.121.18.18,UNKNOWN
91.121.6.52,UNKNOWN
91.126.55.84,UNKNOWN
91.152.87.55,UNKNOWN
91.153.222.134,UNKNOWN
91.165.80.65,Paris,A8,FR,48.8667,2.3333
91.186.18.105,UNKNOWN
91.23.234.250,,,DE,51.0000,9.0000
91.4.63.72,,,DE,51.0000,9.0000
91.4.82.200,,,DE,51.0000,9.0000
91.64.139.199,Kabel,07,DE,51.4000,7.4832
91.64.220.19,Kabel,07,DE,51.4000,7.4832
91.7.3.81,,,DE,51.0000,9.0000
vidalia-0.2.21/pkg/osx/ 0000775 0000000 0000000 00000000000 12056211037 0014574 5 ustar 00root root 0000000 0000000 vidalia-0.2.21/pkg/osx/CMakeLists.txt 0000664 0000000 0000000 00000017114 12056211037 0017340 0 ustar 00root root 0000000 0000000 ##
## $Id$
##
## This file is part of Vidalia, and is subject to the license terms in the
## LICENSE file, found in the top level directory of this distribution. If
## you did not receive the LICENSE file with this file, you may obtain it
## from the Vidalia source package distributed by the Vidalia Project at
## http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
## including this file, may be copied, modified, propagated, or distributed
## except according to the terms described in the LICENSE file.
##
set(VIDALIA_APP_BUNDLE_ROOT ${Vidalia_BINARY_DIR}/src/vidalia/Vidalia.app)
get_target_property(VIDALIA_EXECUTABLE Vidalia LOCATION)
add_custom_target(dist-osx-libraries DEPENDS Vidalia)
if (QT_USE_FRAMEWORKS)
vidalia_install_qt4_framework(QtCore
TARGET dist-osx-libraries NAME QtCore
LIBRARY ${QT_QTCORE_LIBRARY_RELEASE}/QtCore
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
)
vidalia_install_qt4_framework(QtGui
TARGET dist-osx-libraries NAME QtGui
LIBRARY ${QT_QTGUI_LIBRARY_RELEASE}/QtGui
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore}
)
vidalia_install_qt4_framework(QtNetwork
TARGET dist-osx-libraries NAME QtNetwork
LIBRARY ${QT_QTNETWORK_LIBRARY_RELEASE}/QtNetwork
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore}
)
vidalia_install_qt4_framework(QtXml
TARGET dist-osx-libraries NAME QtXml
LIBRARY ${QT_QTXML_LIBRARY_RELEASE}/QtXml
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore}
)
vidalia_install_name_tool(${VIDALIA_EXECUTABLE}
TARGET dist-osx-libraries
FRAMEWORKS ${QtCore} ${QtGui} ${QtNetwork} ${QtXml}
)
if (USE_MARBLE)
vidalia_install_qt4_framework(QtSvg
TARGET dist-osx-libraries NAME QtSvg
LIBRARY ${QT_QTSVG_LIBRARY_RELEASE}/QtSvg
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore} ${QtGui}
)
vidalia_install_qt4_framework(QtScript
TARGET dist-osx-libraries NAME QtScript
LIBRARY ${QT_QTSCRIPT_LIBRARY_RELEASE}/QtScript
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore}
)
vidalia_install_qt4_framework(QtDBus
TARGET dist-osx-libraries NAME QtDBus
LIBRARY ${QT_QTDBUS_LIBRARY_RELEASE}/QtDBus
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore} ${QtXml}
)
vidalia_install_qt4_framework(QtPhonon
TARGET dist-osx-libraries NAME phonon
LIBRARY ${QT_PHONON_LIBRARY_RELEASE}/phonon
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore} ${QtGui} ${QtXml} ${QtDBus}
)
vidalia_install_qt4_framework(QtWebKit
TARGET dist-osx-libraries NAME QtWebKit
LIBRARY ${QT_QTWEBKIT_LIBRARY_RELEASE}/QtWebKit
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore} ${QtGui} ${QtNetwork} ${QtXml} ${QtDBus}
${QtPhonon}
)
vidalia_install_dylib(MarbleWidget
TARGET dist-osx-libraries
LIBRARY ${MARBLEWIDGET_LIBRARY}
APP_BUNDLE ${VIDALIA_APP_BUNDLE_ROOT}
DEPENDS_FRAMEWORKS ${QtCore} ${QtGui} ${QtNetwork} ${QtXml} ${QtSvg}
${QtDBus} ${QtScript} ${QtWebKit}
)
vidalia_install_name_tool(${VIDALIA_EXECUTABLE}
TARGET dist-osx-libraries
FRAMEWORKS ${QtSvg} ${QtDBus} ${QtScript} ${QtWebKit}
LIBRARIES ${MARBLEWIDGET_LIBRARY}
)
endif(USE_MARBLE)
endif(QT_USE_FRAMEWORKS)
if (OSX_FAT_BINARY)
set(DMG_ARCH "universal")
else(OSX_FAT_BINARY)
set(DMG_ARCH ${CMAKE_OSX_ARCHITECTURES})
endif(OSX_FAT_BINARY)
add_custom_target(dist-osx
COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/pkg-dmg
--source ${VIDALIA_APP_BUNDLE_ROOT}
--target ${Vidalia_BINARY_DIR}/vidalia-${VERSION}-${DMG_ARCH}.dmg
--sourcefile --volname "Vidalia ${VERSION}"
--icon ${Vidalia_SOURCE_DIR}/src/vidalia/res/icons/Vidalia.icns
--symlink "/Applications:/Drag to here"
--mkdir /.background
--copy ${CMAKE_CURRENT_SOURCE_DIR}/background.png:/.background/
--copy ${CMAKE_CURRENT_SOURCE_DIR}/nonbundle-ds_store:/.DS_Store
--copy ${CMAKE_CURRENT_SOURCE_DIR}/qt.conf:/Vidalia.app/Contents/Resources/qt.conf
--mkdir /Licenses
--copy ${Vidalia_SOURCE_DIR}/LICENSE:/Licenses/License.txt
--copy ${Vidalia_SOURCE_DIR}/LICENSE-GPLV2:/Licenses/License-GPLv2.txt
--copy ${Vidalia_SOURCE_DIR}/LICENSE-GPLV3:/Licenses/License-GPLv3.txt
--copy ${Vidalia_SOURCE_DIR}/README:/ReadMe.txt
--copy ${Vidalia_SOURCE_DIR}/CHANGELOG:/Changes.txt
COMMENT "Creating vidalia-${VERSION}-${DMG_ARCH}.dmg"
VERBATIM
)
add_dependencies(dist-osx dist-osx-libraries)
if (TOR_SOURCE_DIR)
get_filename_component(TOR_SOURCE_DIR ${TOR_SOURCE_DIR} ABSOLUTE)
## Determine Tor's version string used to build the .dmg filename
vidalia_get_tor_version(TOR_VERSION "${TOR_SOURCE_DIR}/src/or/tor")
if (TOR_VERSION)
message(STATUS "Found Tor ${TOR_VERSION}")
else (TOR_VERSION)
message(FATAL_ERROR "Unable to determine version of ${TOR_SOURCE_DIR}/src/or/tor")
endif(TOR_VERSION)
set(bundle_DMG "vidalia-bundle-${TOR_VERSION}-${VERSION}-${DMG_ARCH}.dmg")
add_custom_target(dist-osx-bundle
COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/pkg-dmg
--source ${VIDALIA_APP_BUNDLE_ROOT}
--target ${Vidalia_BINARY_DIR}/${bundle_DMG}
--sourcefile --volname "Vidalia Bundle ${VERSION}"
--icon ${Vidalia_SOURCE_DIR}/src/vidalia/res/icons/Vidalia.icns
--symlink "/Applications:/Drag to here"
--mkdir /.background
--copy ${CMAKE_CURRENT_SOURCE_DIR}/bundle-background.png:/.background/
--copy ${CMAKE_CURRENT_SOURCE_DIR}/bundle-ds_store:/.DS_Store
--copy ${CMAKE_CURRENT_SOURCE_DIR}/vidalia.conf.sample:/Vidalia.app/Contents/Resources/vidalia.conf
--copy ${CMAKE_CURRENT_SOURCE_DIR}/qt.conf:/Vidalia.app/Contents/Resources/qt.conf
--mkdir /Licenses
--copy ${Vidalia_SOURCE_DIR}/LICENSE:/Licenses/License.txt
--copy ${Vidalia_SOURCE_DIR}/LICENSE-GPLV2:/Licenses/License-GPLv2.txt
--copy ${Vidalia_SOURCE_DIR}/LICENSE-GPLV3:/Licenses/License-GPLv3.txt
--copy ${Vidalia_SOURCE_DIR}/CHANGELOG:/Changes.txt
--copy ${TOR_SOURCE_DIR}/src/or/tor:/Vidalia.app/Contents/MacOS/
--copy ${TOR_SOURCE_DIR}/src/tools/tor-checkkey:/Vidalia.app/Contents/MacOS/
--copy ${TOR_SOURCE_DIR}/src/tools/tor-gencert:/Vidalia.app/Contents/MacOS/
--copy ${TOR_SOURCE_DIR}/src/tools/tor-resolve:/Vidalia.app/Contents/MacOS/
--copy ${TOR_SOURCE_DIR}/src/config/geoip:/Vidalia.app/share/tor/
--copy ${TOR_SOURCE_DIR}/src/config/torrc.sample:/Vidalia.app/Contents/Resources/
COMMENT "Creating ${bundle_DMG}"
VERBATIM
)
add_dependencies(dist-osx-bundle dist-osx-libraries)
add_custom_target(dist-osx-split-bundle
COMMAND hdiutil segment -segmentSize 1.5m
-o "${Vidalia_BINARY_DIR}/split-${bundle_DMG}" "${Vidalia_BINARY_DIR}/${bundle_DMG}"
COMMENT "Creating split-${bundle_DMG}"
VERBATIM
)
add_dependencies(dist-osx-split-bundle dist-osx-bundle)
else(TOR_SOURCE_DIR)
message("-- Skipping dist-osx-bundle build target")
add_custom_target(dist-osx-bundle
COMMAND ${CMAKE_COMMAND} -E echo
"!! The dist-osx-bundle target is not configured."
COMMAND ${CMAKE_COMMAND} -E echo
"!! You must set the -DTOR_SOURCE_DIR CMake variable."
COMMAND ${CMAKE_COMMAND} -E echo "!! Quitting."
)
add_custom_target(dist-osx-split-bundle
COMMAND ${CMAKE_COMMAND} -E echo
"!! The dist-osx-split-bundle target is not configured. Quitting."
COMMAND ${CMAKE_COMMAND} -E echo
"!! You must set the -DTOR_SOURCE_DIR CMake variable."
COMMAND ${CMAKE_COMMAND} -E echo "!! Quitting."
)
endif(TOR_SOURCE_DIR)
vidalia-0.2.21/pkg/osx/InstallTorbutton.scpt.in 0000664 0000000 0000000 00000001504 12056211037 0021423 0 ustar 00root root 0000000 0000000 --
-- $Id$
--
-- This file is part of Vidalia, and is subject to the license terms in the
-- LICENSE file, found in the top level directory of this distribution. If
-- you did not receive the LICENSE file with this file, you may obtain it
-- from the Vidalia source package distributed by the Vidalia Project at
-- http://www.torproject.org/projects/vidalia.html. No part of Vidalia,
-- including this file, may be copied, modified, propagated, or distributed
-- except according to the terms described in the LICENSE file.
--
try
set p to path to me
set p to POSIX path of p
do shell script "open -a Firefox " & quoted form of p & "@TORBUTTON_XPI_FILENAME@"
on error errStr
display dialog
"We were unable to install Torbutton. Please make sure Firefox is installed and try again."
buttons {"OK"}
end try
vidalia-0.2.21/pkg/osx/background.png 0000664 0000000 0000000 00000253132 12056211037 0017427 0 ustar 00root root 0000000 0000000 PNG
IHDR X PY pHYs od IDATx\yUŕ?u}{XDV#`2qQ\Pc4N4N437_#E%ff-qFTelZ}wub>}V:u~uN[Fy RoYK&L#PG>h2d%EH$җ4ҤIgocaC <_Jr 7 lJ2[@`rb"<gFD%'. 7/:֮E\J[_fe@`Κ;k6`v|ؽo
}v
۷lH ygG5C|>e۬_i[[j\vRw^cUD EXR@2훁;\5bͼrlJF([>_pG>/ۛ;0ISpGcp;ʇ;xd^0u-fz,y丿SU"w?wξvzU