November 2011 - tor-commits - lists.torproject.org

[translation/orbot] Update translations for orbot
by translation＠torproject.org 23 Nov '11

23 Nov '11

commit aa3b52ca0ff732c95a8cf86fb7b33034ead34762 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Nov 23 19:15:03 2011 +0000 Update translations for orbot --- values-it/strings.xml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/values-it/strings.xml b/values-it/strings.xml index d100f8d..4eb49e8 100644 --- a/values-it/strings.xml +++ b/values-it/strings.xml @@ -13,7 +13,7 @@ <string name="status_shutting_down">Orbot si sta spegnendo</string> <string name="tor_process_starting">Avvio client Tor...</string> <string name="tor_process_complete">completa.</string> - <string name="tor_process_waiting"></string> + <string name="tor_process_waiting">attesa.</string> <string name="not_anonymous_yet">ATTENZIONE: Il traffico non è ancora anonimo! Configura le applicazioni per utilizzare il proxy HTTP 127.0.0.1:8118, SOCKS4A o proxy SOCKS5 127.0.0.1:9050</string> <string name="menu_home">Home</string> <string name="menu_browse">Sfoglia</string> @@ -116,10 +116,10 @@ Visita il nostro sito web https://guardianproject.info/apps/orbot o invia una ma <string name="pref_use_whispercore">Usa WhisperCore</string> <string name="pref_use_whispercore_summary"></string> <string name="pref_proxy_type_title">Tipo proxy</string> - <string name="pref_proxy_type_summary"></string> + <string name="pref_proxy_type_summary">Protocolli da utilizzare per i server proxy: HTTP, HTTPS, Socks4, Socks5</string> <string name="pref_proxy_type_dialog">Inserisci tipo proxy</string> <string name="pref_proxy_host_title">Host proxy</string> - <string name="pref_proxy_host_summary"></string> + <string name="pref_proxy_host_summary">Hostname server proxy</string> <string name="pref_proxy_host_dialog"></string> <string name="pref_proxy_port_title">Porta proxy</string> <string name="pref_proxy_port_summary"></string>

1 0

[stem/master] Nicer logging when receiving controller data
by atagar＠torproject.org 23 Nov '11

23 Nov '11

commit 1c2337a71f9f19e262cd222679bf66eb046a9e73 Author: Damian Johnson <atagar(a)torproject.org> Date: Wed Nov 23 06:47:11 2011 -0800 Nicer logging when receiving controller data Changing the logged controller messages a bit. This is a bit less faithful to the raw controller response but it's more readable. --- stem/types.py | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/stem/types.py b/stem/types.py index 4415598..882ca99 100644 --- a/stem/types.py +++ b/stem/types.py @@ -124,7 +124,9 @@ def read_message(control_file): # end of the message, return the message parsed_content.append((status_code, divider, content)) - LOGGER.debug("Received message:\n" + raw_content) + # replacing the \r\n newline endings and the ending newline since it + # leads to more readable log messages + LOGGER.debug("Received message:\n" + raw_content.replace("\r\n", "\n").rstrip()) return ControlMessage(parsed_content, raw_content) elif divider == "+":

1 0

[stem/master] Defaulting open connection integ target
by atagar＠torproject.org 23 Nov '11

23 Nov '11

commit f98822f01e00197140ccea9dc88690d6ece004df Author: Damian Johnson <atagar(a)torproject.org> Date: Wed Nov 23 09:23:42 2011 -0800 Defaulting open connection integ target All connection targets were being defaulted to false, causing plain "run_tests --integ" runs to be no-ops. Hacking in the default values. I should probably use the more conventional dict/update pattern later. --- run_tests.py | 19 +++++++++++-------- 1 files changed, 11 insertions(+), 8 deletions(-) diff --git a/run_tests.py b/run_tests.py index 3ef21c0..275c50e 100755 --- a/run_tests.py +++ b/run_tests.py @@ -212,18 +212,21 @@ if __name__ == '__main__': if test_config.get("test.integ.target.connection.all", False): connection_types = list(test.runner.TorConnection) else: + # mapping of config type to (enum, default) tuple conn_type_mappings = { - "none": test.runner.TorConnection.NONE, - "open": test.runner.TorConnection.OPEN, - "password": test.runner.TorConnection.PASSWORD, - "cookie": test.runner.TorConnection.COOKIE, - "multiple": test.runner.TorConnection.MULTIPLE, - "socket": test.runner.TorConnection.SOCKET, + "none": (test.runner.TorConnection.NONE, False), + "open": (test.runner.TorConnection.OPEN, True), + "password": (test.runner.TorConnection.PASSWORD, False), + "cookie": (test.runner.TorConnection.COOKIE, False), + "multiple": (test.runner.TorConnection.MULTIPLE, False), + "socket": (test.runner.TorConnection.SOCKET, False), } for type_key in conn_type_mappings: - if test_config.get("test.integ.target.connection.%s" % type_key, False): - connection_types.append(conn_type_mappings[type_key]) + default = conn_type_mappings[type_key][1] + + if test_config.get("test.integ.target.connection.%s" % type_key, default): + connection_types.append(conn_type_mappings[type_key][0]) for connection_type in connection_types: try:

1 0

[stem/master] Function for writting to control sockets
by atagar＠torproject.org 23 Nov '11

23 Nov '11

commit 8dc796d142bebb6d370188f7e5be6bf65e402743 Author: Damian Johnson <atagar(a)torproject.org> Date: Wed Nov 23 09:55:16 2011 -0800 Function for writting to control sockets Writing directly to the socket file isn't hard (it's just a write and flush). However, this is nicer since it wrap the control formatting, logging, and exception quirks. Functions still need unit tests and I might just wrap the socket object completely... --- stem/connection.py | 3 +- stem/types.py | 80 +++++++++++++++++++++++++++++++- test/integ/connection/protocolinfo.py | 4 +- test/integ/types/control_message.py | 48 ++++++------------- test/runner.py | 7 +-- 5 files changed, 97 insertions(+), 45 deletions(-) diff --git a/stem/connection.py b/stem/connection.py index 476c9c3..5fc06c1 100644 --- a/stem/connection.py +++ b/stem/connection.py @@ -107,8 +107,7 @@ def _get_protocolinfo_impl(control_socket, connection_args, keep_alive): control_socket.connect(connection_args) # issues the PROTOCOLINFO query - control_socket_file.write("PROTOCOLINFO 1\r\n") - control_socket_file.flush() + stem.types.write_message(control_socket_file, "PROTOCOLINFO 1") protocolinfo_response = stem.types.read_message(control_socket_file) ProtocolInfoResponse.convert(protocolinfo_response) diff --git a/stem/types.py b/stem/types.py index 882ca99..66aa205 100644 --- a/stem/types.py +++ b/stem/types.py @@ -7,6 +7,8 @@ ControllerError - Base exception raised when using the controller. |- SocketError - Socket used for controller communication errored. +- SocketClosed - Socket terminated. +write_message - Writes a message to a control socket. +format_write_message - Performs the formatting expected from sent messages. read_message - Reads a ControlMessage from a control socket. ControlMessage - Message from the control socket. |- content - provides the parsed message content @@ -58,18 +60,90 @@ class SocketError(ControllerError): "Error arose while communicating with the control socket." pass -class SocketClosed(ControllerError): +class SocketClosed(SocketError): "Control socket was closed before completing the message." pass +def write_message(control_file, message, raw = False): + """ + Sends a message to the control socket, adding the expected formatting for + single verses multiline messages. Neither message type should contain an + ending newline (if so it'll be treated as a multi-line message with a blank + line at the end). If the message doesn't contain a newline then it's sent + as... + + <message>\r\n + + and if it does contain newlines then it's split on \n and sent as... + + +<line 1>\r\n + <line 2>\r\n + <line 3>\r\n + .\r\n + + Arguments: + control_file (file) - file derived from the control socket (see the + socket's makefile() method for more information) + message (str) - message to be sent on the control socket + raw (bool) - leaves the message formatting untouched, passing it + to the socket as-is + + Raises: + SocketError if a problem arises in using the socket + """ + + if not raw: message = format_write_message(message) + + try: + LOGGER.debug("Sending message:\n" + message.replace("\r\n", "\n").rstrip()) + control_file.write(message) + control_file.flush() + except socket.error, exc: + LOGGER.info("Failed to send message: %s" % exc) + raise SocketError(exc) + except AttributeError: + # This happens after the file's close() method has been called, the flush + # causing... + # AttributeError: 'NoneType' object has no attribute 'sendall' + + LOGGER.info("Failed to send message: file has been closed") + raise SocketError("file has been closed") + +def format_write_message(message): + """ + Performs the formatting expected of control messages (for more information + see the write_message function). + + Arguments: + message (str) - message to be formatted + + Returns: + str of the message wrapped by the formatting expected from controllers + """ + + # From 'Commands from controller to Tor' (section 2.2) of the control spec... + # + # Command = Keyword OptArguments CRLF / "+" Keyword OptArguments CRLF CmdData + # Keyword = 1*ALPHA + # OptArguments = [ SP *(SP / VCHAR) ] + # + # A command is either a single line containing a Keyword and arguments, or a + # multiline command whose initial keyword begins with +, and whose data + # section ends with a single "." on a line of its own. + + if "\n" in message: + return "+%s\r\n.\r\n" % message.replace("\n", "\r\n") + else: + return message + "\r\n" + def read_message(control_file): """ Pulls from a control socket until we either have a complete message or encounter a problem. Arguments: - control_file - file derived from the control socket (see the socket's - makefile() method for more information) + control_file (file) - file derived from the control socket (see the + socket's makefile() method for more information) Returns: stem.types.ControlMessage read from the socket diff --git a/test/integ/connection/protocolinfo.py b/test/integ/connection/protocolinfo.py index 1035fe6..e2e9a7b 100644 --- a/test/integ/connection/protocolinfo.py +++ b/test/integ/connection/protocolinfo.py @@ -31,9 +31,7 @@ class TestProtocolInfo(unittest.TestCase): control_socket = runner.get_tor_socket(False) control_socket_file = control_socket.makefile() - control_socket_file.write("PROTOCOLINFO 1\r\n") - control_socket_file.flush() - + stem.types.write_message(control_socket_file, "PROTOCOLINFO 1") protocolinfo_response = stem.types.read_message(control_socket_file) stem.connection.ProtocolInfoResponse.convert(protocolinfo_response) diff --git a/test/integ/types/control_message.py b/test/integ/types/control_message.py index 4aa878f..392cd25 100644 --- a/test/integ/types/control_message.py +++ b/test/integ/types/control_message.py @@ -27,8 +27,7 @@ class TestControlMessage(unittest.TestCase): # PROTOCOLINFO then tor will give an 'Authentication required.' message and # hang up. - control_socket_file.write("GETINFO version\r\n") - control_socket_file.flush() + stem.types.write_message(control_socket_file, "GETINFO version") auth_required_response = stem.types.read_message(control_socket_file) self.assertEquals("Authentication required.", str(auth_required_response)) @@ -39,11 +38,10 @@ class TestControlMessage(unittest.TestCase): # The socket's broken but doesn't realize it yet. Send another message and # it should fail with a closed exception. With a control port we won't get # an error until we read from the socket. However, with a control socket - # the flush will raise a socket.error. + # the write will cause a SocketError. try: - control_socket_file.write("GETINFO version\r\n") - control_socket_file.flush() + stem.types.write_message(control_socket_file, "GETINFO version") except: pass self.assertRaises(stem.types.SocketClosed, stem.types.read_message, control_socket_file) @@ -51,8 +49,7 @@ class TestControlMessage(unittest.TestCase): # Additional socket usage should fail, and pulling more responses will fail # with more closed exceptions. - control_socket_file.write("GETINFO version\r\n") - self.assertRaises(socket.error, control_socket_file.flush) + self.assertRaises(stem.types.SocketError, stem.types.write_message, control_socket_file, "GETINFO version") self.assertRaises(stem.types.SocketClosed, stem.types.read_message, control_socket_file) self.assertRaises(stem.types.SocketClosed, stem.types.read_message, control_socket_file) self.assertRaises(stem.types.SocketClosed, stem.types.read_message, control_socket_file) @@ -61,22 +58,17 @@ class TestControlMessage(unittest.TestCase): # an impact. control_socket.close() - control_socket_file.write("GETINFO version\r\n") - self.assertRaises(socket.error, control_socket_file.flush) + self.assertRaises(stem.types.SocketError, stem.types.write_message, control_socket_file, "GETINFO version") self.assertRaises(stem.types.SocketClosed, stem.types.read_message, control_socket_file) - # Closing the file handler, however, will cause a different type of error. - # This seems to depend on the python version, in 2.6 we get an - # AttributeError and in 2.7 the close() call raises... - # error: [Errno 32] Broken pipe + # Tries again with the file explicitely closed. In python 2.7 the close + # call will raise... + # error: [Errno 32] Broken pipe - try: - control_socket_file.close() - control_socket_file.write("GETINFO version\r\n") + try: control_socket_file.close() except: pass - # receives: AttributeError: 'NoneType' object has no attribute 'sendall' - self.assertRaises(AttributeError, control_socket_file.flush) + self.assertRaises(stem.types.SocketError, stem.types.write_message, control_socket_file, "GETINFO version") # receives: stem.types.SocketClosed: socket file has been closed self.assertRaises(stem.types.SocketClosed, stem.types.read_message, control_socket_file) @@ -90,9 +82,7 @@ class TestControlMessage(unittest.TestCase): if not control_socket: self.skipTest("(no control socket)") control_socket_file = control_socket.makefile() - control_socket_file.write("blarg\r\n") - control_socket_file.flush() - + stem.types.write_message(control_socket_file, "blarg") unrecognized_command_response = stem.types.read_message(control_socket_file) self.assertEquals('Unrecognized command "blarg"', str(unrecognized_command_response)) self.assertEquals(['Unrecognized command "blarg"'], list(unrecognized_command_response)) @@ -111,9 +101,7 @@ class TestControlMessage(unittest.TestCase): if not control_socket: self.skipTest("(no control socket)") control_socket_file = control_socket.makefile() - control_socket_file.write("GETINFO blarg\r\n") - control_socket_file.flush() - + stem.types.write_message(control_socket_file, "GETINFO blarg") unrecognized_key_response = stem.types.read_message(control_socket_file) self.assertEquals('Unrecognized key "blarg"', str(unrecognized_key_response)) self.assertEquals(['Unrecognized key "blarg"'], list(unrecognized_key_response)) @@ -135,9 +123,7 @@ class TestControlMessage(unittest.TestCase): if not control_socket: self.skipTest("(no control socket)") control_socket_file = control_socket.makefile() - control_socket_file.write("GETINFO config-file\r\n") - control_socket_file.flush() - + stem.types.write_message(control_socket_file, "GETINFO config-file") config_file_response = stem.types.read_message(control_socket_file) self.assertEquals("config-file=%s\nOK" % torrc_dst, str(config_file_response)) self.assertEquals(["config-file=%s" % torrc_dst, "OK"], list(config_file_response)) @@ -174,9 +160,7 @@ class TestControlMessage(unittest.TestCase): if not control_socket: self.skipTest("(no control socket)") control_socket_file = control_socket.makefile() - control_socket_file.write("GETINFO config-text\r\n") - control_socket_file.flush() - + stem.types.write_message(control_socket_file, "GETINFO config-text") config_text_response = stem.types.read_message(control_socket_file) # the response should contain two entries, the first being a data response @@ -206,9 +190,7 @@ class TestControlMessage(unittest.TestCase): if not control_socket: self.skipTest("(no control socket)") control_socket_file = control_socket.makefile() - control_socket_file.write("SETEVENTS BW\r\n") - control_socket_file.flush() - + stem.types.write_message(control_socket_file, "SETEVENTS BW") setevents_response = stem.types.read_message(control_socket_file) self.assertEquals("OK", str(setevents_response)) self.assertEquals(["OK"], list(setevents_response)) diff --git a/test/runner.py b/test/runner.py index e1c9f0b..bc8e8ec 100644 --- a/test/runner.py +++ b/test/runner.py @@ -341,13 +341,12 @@ class Runner: auth_cookie_contents = auth_cookie.read() auth_cookie.close() - control_socket_file.write("AUTHENTICATE %s\r\n" % binascii.b2a_hex(auth_cookie_contents)) + stem.types.write_message(control_socket_file, "AUTHENTICATE %s" % binascii.b2a_hex(auth_cookie_contents)) elif OPT_PASSWORD in conn_opts: - control_socket_file.write("AUTHENTICATE \"%s\"\r\n" % CONTROL_PASSWORD) + stem.types.write_message(control_socket_file, "AUTHENTICATE \"%s\"" % CONTROL_PASSWORD) else: - control_socket_file.write("AUTHENTICATE\r\n") + stem.types.write_message(control_socket_file, "AUTHENTICATE") - control_socket_file.flush() authenticate_response = stem.types.read_message(control_socket_file) control_socket_file.close()

1 0

[stem/master] Showing shorter single-line controller messages
by atagar＠torproject.org 23 Nov '11

23 Nov '11

commit e3d4311962b7e95b882a9a50b2402b17f2f2d3d9 Author: Damian Johnson <atagar(a)torproject.org> Date: Wed Nov 23 10:05:15 2011 -0800 Showing shorter single-line controller messages When controller messages are on a single line logging them that way too, making the output a little more readable. I should probably file send/recv at a trace runlevel or with a separate logger... --- stem/types.py | 15 +++++++++++++-- 1 files changed, 13 insertions(+), 2 deletions(-) diff --git a/stem/types.py b/stem/types.py index 66aa205..0bc3c45 100644 --- a/stem/types.py +++ b/stem/types.py @@ -95,7 +95,13 @@ def write_message(control_file, message, raw = False): if not raw: message = format_write_message(message) try: - LOGGER.debug("Sending message:\n" + message.replace("\r\n", "\n").rstrip()) + log_message = message.replace("\r\n", "\n").rstrip() + + # starts with a newline if this is a multi-line message (more readable) + if "\n" in log_message: log_message = "\n" + log_message + + LOGGER.debug("Sending: " + log_message) + control_file.write(message) control_file.flush() except socket.error, exc: @@ -200,7 +206,12 @@ def read_message(control_file): # replacing the \r\n newline endings and the ending newline since it # leads to more readable log messages - LOGGER.debug("Received message:\n" + raw_content.replace("\r\n", "\n").rstrip()) + log_message = raw_content.replace("\r\n", "\n").rstrip() + + # starts with a newline if this is a multi-line message (more readable) + if "\n" in log_message: log_message = "\n" + log_message + + LOGGER.debug("Received: " + log_message) return ControlMessage(parsed_content, raw_content) elif divider == "+":

1 0

[tor/master] Merge remote-tracking branch 'origin/maint-0.2.2'
by nickm＠torproject.org 23 Nov '11

23 Nov '11

commit 281aa2e237586a1086c3f589ed35a74eda4f1a27 Merge: e18fa28 841247a Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Nov 23 12:12:52 2011 -0500 Merge remote-tracking branch 'origin/maint-0.2.2'

1 0

[tor/master] Fix a compile warning on 64bit OS X
by nickm＠torproject.org 23 Nov '11

23 Nov '11

commit 841247a5864064ce031988ca2dab5808b11408b2 Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Wed Nov 23 01:41:37 2011 +0100 Fix a compile warning on 64bit OS X Backport of 68475fc5c5a806ebbb5657de1667dab2c3e09b7c which accidentally only made it into master. Fixes bug 4547. Bug isn't in any released version. --- src/or/dirserv.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/or/dirserv.c b/src/or/dirserv.c index 19d9702..634b3ec 100644 --- a/src/or/dirserv.c +++ b/src/or/dirserv.c @@ -1909,7 +1909,7 @@ dirserv_compute_performance_thresholds(routerlist_t *rl) * of Fast nodes. */ if (options->AuthDirFastGuarantee && fast_bandwidth > options->AuthDirFastGuarantee) - fast_bandwidth = options->AuthDirFastGuarantee; + fast_bandwidth = (uint32_t)options->AuthDirFastGuarantee; /* Now that we have a time-known that 7/8 routers are known longer than, * fill wfus with the wfu of every such "familiar" router. */

1 0

[tor/maint-0.2.2] Fix a compile warning on 64bit OS X
by nickm＠torproject.org 23 Nov '11

23 Nov '11

commit 841247a5864064ce031988ca2dab5808b11408b2 Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Wed Nov 23 01:41:37 2011 +0100 Fix a compile warning on 64bit OS X Backport of 68475fc5c5a806ebbb5657de1667dab2c3e09b7c which accidentally only made it into master. Fixes bug 4547. Bug isn't in any released version. --- src/or/dirserv.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/or/dirserv.c b/src/or/dirserv.c index 19d9702..634b3ec 100644 --- a/src/or/dirserv.c +++ b/src/or/dirserv.c @@ -1909,7 +1909,7 @@ dirserv_compute_performance_thresholds(routerlist_t *rl) * of Fast nodes. */ if (options->AuthDirFastGuarantee && fast_bandwidth > options->AuthDirFastGuarantee) - fast_bandwidth = options->AuthDirFastGuarantee; + fast_bandwidth = (uint32_t)options->AuthDirFastGuarantee; /* Now that we have a time-known that 7/8 routers are known longer than, * fill wfus with the wfu of every such "familiar" router. */

1 0

r25233: {website} add latest press hits. (website/trunk/press/en)
by Andrew Lewman 23 Nov '11

23 Nov '11

Author: phobos Date: 2011-11-23 17:05:54 +0000 (Wed, 23 Nov 2011) New Revision: 25233 Modified: website/trunk/press/en/inthemedia.wml Log: add latest press hits. Modified: website/trunk/press/en/inthemedia.wml =================================================================== --- website/trunk/press/en/inthemedia.wml 2011-11-23 09:41:01 UTC (rev 25232) +++ website/trunk/press/en/inthemedia.wml 2011-11-23 17:05:54 UTC (rev 25233) @@ -33,6 +33,16 @@ </tr> </thead> <tr style="background-color: #e5e5e5;"> +<td>2011 Nov 23</td> +<td>IT Security Belgium</td> +<td><a href="http://www.itsecurity.be/tor-project-is-tapping-amazons-ec2-cloud-service">Tor Project is tapping Amazon’s EC2 cloud service</a></td> +</tr> +<tr> +<td>2011 Nov 22</td> +<td>Boing Boing</td> +<td><a href="http://boingboing.net/2011/11/22/tor-project-asks-supporters-to.html">Tor project asks supporters to set up virtual Tor bridges in Amazon's cloud</a></td> +</tr> +<tr style="background-color: #e5e5e5;"> <td>2011 Nov 16</td> <td>Forbes</td> <td><a href="http://www.forbes.com/sites/andygreenberg/2011/11/17/chinas-great-firewall-…">China's Great Firewall Tests Mysterious Scans On Encrypted Connections</a></td>

1 0

[torbrowser/maint-2.2] Separated patching of Firefox source into its own target.
by erinn＠torproject.org 23 Nov '11

23 Nov '11

commit 62e72406f499c8e1ff9a6603e0ecd25fac9b9035 Author: Shondoit Walker <shondoit(a)gmail.com> Date: Thu Nov 10 23:29:57 2011 +0100 Separated patching of Firefox source into its own target. --- build-scripts/windows.mk | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/build-scripts/windows.mk b/build-scripts/windows.mk index 201e9d6..80ac087 100644 --- a/build-scripts/windows.mk +++ b/build-scripts/windows.mk @@ -116,12 +116,14 @@ patch-mozbuild: cp ../src/current-patches/mozilla-build/guess-msvc-x64.bat $(MOZ_BUILD) cp patch-mozilla-build.sh $(MOZ_BUILD) cd $(MOZ_BUILD) && ./patch-mozilla-build.sh $(MSVC_VER) + cp $(CONFIG_SRC)/dot_mozconfig $(FIREFOX_DIR)/mozconfig -build-firefox: +patch-firefox-source: cp ../src/current-patches/firefox/* $(FIREFOX_DIR) cp patch-any-src.sh $(FIREFOX_DIR) - cp $(CONFIG_SRC)/dot_mozconfig $(FIREFOX_DIR)/mozconfig cd $(FIREFOX_DIR) && ./patch-any-src.sh + +build-firefox: cd $(MOZ_BUILD) && cmd.exe /c "start-msvc$(MSVC_VER).bat $(FIREFOX_DIR)" copy-firefox:

1 0