tor-commits June 2018

tor-commits@lists.torproject.org

16 participants
2190 discussions

[translation/tails-persistence-setup] Update translations for tails-persistence-setup
by translation＠torproject.org 08 Jun '18

08 Jun '18

commit 524695add83affb3f5c1df1a8609ceefd9a3c9a0 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 8 07:15:59 2018 +0000 Update translations for tails-persistence-setup --- nl_BE/nl_BE.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl_BE/nl_BE.po b/nl_BE/nl_BE.po index 10da329e5..806bcc771 100644 --- a/nl_BE/nl_BE.po +++ b/nl_BE/nl_BE.po @@ -9,8 +9,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: Tails developers <tails(a)boum.org>\n" "POT-Creation-Date: 2017-05-15 13:51+0200\n" -"PO-Revision-Date: 2018-04-12 18:58+0000\n" -"Last-Translator: Nathan Follens\n" +"PO-Revision-Date: 2018-06-08 07:09+0000\n" +"Last-Translator: erinm\n" "Language-Team: Dutch (Belgium) (http://www.transifex.com/otf/torproject/language/nl_BE/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[translation/whisperback_completed] Update translations for whisperback_completed
by translation＠torproject.org 08 Jun '18

08 Jun '18

commit edae4985ea57a4dd06ccf1ffd52f56e76dd36566 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 8 07:15:31 2018 +0000 Update translations for whisperback_completed --- nl_BE/nl_BE.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl_BE/nl_BE.po b/nl_BE/nl_BE.po index 7858496dc..1a41ef844 100644 --- a/nl_BE/nl_BE.po +++ b/nl_BE/nl_BE.po @@ -10,8 +10,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2017-03-20 12:09+0000\n" -"PO-Revision-Date: 2018-04-12 18:55+0000\n" -"Last-Translator: Nathan Follens\n" +"PO-Revision-Date: 2018-06-08 07:09+0000\n" +"Last-Translator: erinm\n" "Language-Team: Dutch (Belgium) (http://www.transifex.com/otf/torproject/language/nl_BE/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[translation/whisperback] Update translations for whisperback
by translation＠torproject.org 08 Jun '18

08 Jun '18

commit 9d7866db99f0ab3aceffc6f7ee82b3bcd37d7be2 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 8 07:15:26 2018 +0000 Update translations for whisperback --- nl_BE/nl_BE.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl_BE/nl_BE.po b/nl_BE/nl_BE.po index 7858496dc..1a41ef844 100644 --- a/nl_BE/nl_BE.po +++ b/nl_BE/nl_BE.po @@ -10,8 +10,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2017-03-20 12:09+0000\n" -"PO-Revision-Date: 2018-04-12 18:55+0000\n" -"Last-Translator: Nathan Follens\n" +"PO-Revision-Date: 2018-06-08 07:09+0000\n" +"Last-Translator: erinm\n" "Language-Team: Dutch (Belgium) (http://www.transifex.com/otf/torproject/language/nl_BE/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[translation/bridgedb_completed] Update translations for bridgedb_completed
by translation＠torproject.org 08 Jun '18

08 Jun '18

commit 902984a14c6f3d89b59c47b20459b41aa519e747 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 8 07:15:13 2018 +0000 Update translations for bridgedb_completed --- nl_BE/LC_MESSAGES/bridgedb.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl_BE/LC_MESSAGES/bridgedb.po b/nl_BE/LC_MESSAGES/bridgedb.po index 4fdd5a82d..73860f1d8 100644 --- a/nl_BE/LC_MESSAGES/bridgedb.po +++ b/nl_BE/LC_MESSAGES/bridgedb.po @@ -9,8 +9,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2015-07-25 03:40+0000\n" -"PO-Revision-Date: 2017-09-19 23:00+0000\n" -"Last-Translator: Katrien Igodt <kigodt(a)gmail.com>\n" +"PO-Revision-Date: 2018-06-08 07:09+0000\n" +"Last-Translator: erinm\n" "Language-Team: Dutch (Belgium) (http://www.transifex.com/otf/torproject/language/nl_BE/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 08 Jun '18

08 Jun '18

commit 01e85d58ccd37afbb47f5c31c90107addc174445 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jun 8 07:15:04 2018 +0000 Update translations for bridgedb --- nl_BE/LC_MESSAGES/bridgedb.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl_BE/LC_MESSAGES/bridgedb.po b/nl_BE/LC_MESSAGES/bridgedb.po index 4fdd5a82d..73860f1d8 100644 --- a/nl_BE/LC_MESSAGES/bridgedb.po +++ b/nl_BE/LC_MESSAGES/bridgedb.po @@ -9,8 +9,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2015-07-25 03:40+0000\n" -"PO-Revision-Date: 2017-09-19 23:00+0000\n" -"Last-Translator: Katrien Igodt <kigodt(a)gmail.com>\n" +"PO-Revision-Date: 2018-06-08 07:09+0000\n" +"Last-Translator: erinm\n" "Language-Team: Dutch (Belgium) (http://www.transifex.com/otf/torproject/language/nl_BE/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[stem/master] Account for attribute types in hash and equality
by atagar＠torproject.org 07 Jun '18

07 Jun '18

commit 4306013ab6e868e99553fbb78ed14ef51a896b7d Author: Damian Johnson <atagar(a)torproject.org> Date: Thu Jun 7 15:20:16 2018 -0700 Account for attribute types in hash and equality Proper equality checks and hash functions should take attribute types into account. Unsurprisingly this uncovered a few small bugs where we forgot to normalize constructor inputs. --- docs/change_log.rst | 3 ++- stem/directory.py | 6 ++--- stem/exit_policy.py | 2 ++ stem/manual.py | 22 ++++++++-------- stem/util/__init__.py | 69 ++++++++++++++++++++++++++++++++++++--------------- 5 files changed, 67 insertions(+), 35 deletions(-) diff --git a/docs/change_log.rst b/docs/change_log.rst index 944d3577..e735d6b2 100644 --- a/docs/change_log.rst +++ b/docs/change_log.rst @@ -22,7 +22,7 @@ Versioning Stem uses `semantic versioning <http://semver.org/>`_, which means that **versions consist of three numbers** (such as '**1.2.4**'). These are used to -convey the kind of backward compatibility a release has... +convey the kind of backward compatibility you can expect... * The first value is the **major version**. This changes infrequently, and indicates that backward incompatible changes have been made (such as the @@ -80,6 +80,7 @@ The following are only available within Stem's `git repository * Fixed PyPy compatibility (:trac:`26207`) * Connection information from proc limited to 10,000 results + * Accouting for attribute types in most equality checks and hashes * **Website** diff --git a/stem/directory.py b/stem/directory.py index 5d1a352d..600c9721 100644 --- a/stem/directory.py +++ b/stem/directory.py @@ -352,19 +352,19 @@ class Fallback(Directory): .. versionadded:: 1.5.0 .. versionchanged:: 1.7.0 - Added the has_extrainfo, and header attributes which are part of + Added the has_extrainfo and header attributes which are part of the `second version of the fallback directories <https://lists.torproject.org/pipermail/tor-dev/2017-December/012721.html>`_. :var bool has_extrainfo: **True** if the relay should be able to provide extrainfo descriptors, **False** otherwise. - :var dict header: metadata about the fallback directory file this originated from + :var collections.OrderedDict header: metadata about the fallback directory file this originated from """ def __init__(self, address = None, or_port = None, dir_port = None, fingerprint = None, nickname = None, has_extrainfo = False, orport_v6 = None, header = None): super(Fallback, self).__init__(address, or_port, dir_port, fingerprint, nickname, orport_v6) self.has_extrainfo = has_extrainfo - self.header = header if header else OrderedDict() + self.header = OrderedDict(header) if header else OrderedDict() @staticmethod def from_cache(path = FALLBACK_CACHE_PATH): diff --git a/stem/exit_policy.py b/stem/exit_policy.py index 27475858..0b956db9 100644 --- a/stem/exit_policy.py +++ b/stem/exit_policy.py @@ -656,6 +656,8 @@ class ExitPolicyRule(object): # policy ::= "accept[6]" exitpattern | "reject[6]" exitpattern # exitpattern ::= addrspec ":" portspec + rule = stem.util.str_tools._to_unicode(rule) + self.is_accept = rule.startswith('accept') is_ipv6_only = rule.startswith('accept6') or rule.startswith('reject6') diff --git a/stem/manual.py b/stem/manual.py index f8e7ea96..47c16d42 100644 --- a/stem/manual.py +++ b/stem/manual.py @@ -359,11 +359,11 @@ class Manual(object): :var str synopsis: brief tor command usage :var str description: general description of what tor does - :var dict commandline_options: mapping of commandline arguments to their descripton - :var dict signals: mapping of signals tor accepts to their description - :var dict files: mapping of file paths to their description + :var collections.OrderedDict commandline_options: mapping of commandline arguments to their descripton + :var collections.OrderedDict signals: mapping of signals tor accepts to their description + :var collections.OrderedDict files: mapping of file paths to their description - :var dict config_options: :class:`~stem.manual.ConfigOption` tuples for tor configuration options + :var collections.OrderedDict config_options: :class:`~stem.manual.ConfigOption` tuples for tor configuration options :var str man_commit: latest tor commit editing the man page when this information was cached @@ -374,10 +374,10 @@ class Manual(object): self.name = name self.synopsis = synopsis self.description = description - self.commandline_options = commandline_options - self.signals = signals - self.files = files - self.config_options = config_options + self.commandline_options = OrderedDict(commandline_options) + self.signals = OrderedDict(signals) + self.files = OrderedDict(files) + self.config_options = OrderedDict(config_options) self.man_commit = None self.stem_commit = None self.schema = None @@ -479,9 +479,9 @@ class Manual(object): conf.get('name', ''), conf.get('synopsis', ''), conf.get('description', ''), - conf.get('commandline_options', {}), - conf.get('signals', {}), - conf.get('files', {}), + conf.get('commandline_options', OrderedDict()), + conf.get('signals', OrderedDict()), + conf.get('files', OrderedDict()), config_options, ) diff --git a/stem/util/__init__.py b/stem/util/__init__.py index c2b4999f..f1a7be6a 100644 --- a/stem/util/__init__.py +++ b/stem/util/__init__.py @@ -24,11 +24,51 @@ __all__ = [ 'datetime_to_unix', ] -# Python hashes booleans to zero or one. Usually this would be fine, but since -# we use hashes for equality checks we need them to be something less common. +# Beginning with Stem 1.7 we take attribute types into account when hashing +# and checking equality. That is to say, if two Stem classes' attributes are +# the same but use different types we no longer consider them to be equal. +# For example... +# +# s1 = Schedule(classes = ['Math', 'Art', 'PE']) +# s2 = Schedule(classes = ('Math', 'Art', 'PE')) +# +# Prior to Stem 1.7 s1 and s2 would be equal, but afterward unless Stem's +# construcotr normalizes the types they won't. +# +# This change in behavior is the right thing to do but carries some risk, so +# we provide the following constant to revert to legacy behavior. If you find +# yourself using it them please let me know (https://www.atagar.com/contact/) +# since this flag will go away in the future. + +HASH_TYPES = True + + +def _hash_value(val): + if not HASH_TYPES: + my_hash = 0 + else: + my_hash = hash(type(val)) + + # TODO: I hate doing this but until Python 2.x support is dropped we + # can't readily be strict about bytes vs unicode for attributes. This + # is because test assertions often use strings, and normalizing this + # would require wrapping most with to_unicode() calls. + # + # This hack will go away when we drop Python 2.x support. + + if _is_str(val): + my_hash = hash(type(str)) + + if isinstance(val, (tuple, list)): + for v in val: + my_hash = (my_hash * 1024) + hash(v) + elif isinstance(val, dict): + for k in sorted(val.keys()): + my_hash = (my_hash * 2048) + (hash(k) * 1024) + hash(val[k]) + else: + my_hash += hash(val) -TRUE_HASH_VALUE = 4813749 -FALSE_HASH_VALUE = 5826450 + return my_hash def _is_str(val): @@ -91,23 +131,12 @@ def _hash_attr(obj, *attributes, **kwargs): :param class parent: parent object to include in the hash value """ - my_hash = 0 if kwargs.get('parent') is None else kwargs.get('parent').__hash__(obj) + # TODO: deal with this parent thing + + my_hash = hash(type(obj)) if kwargs.get('parent') is None else kwargs.get('parent').__hash__(obj) for attr in attributes: - my_hash *= 1024 - - attr_value = getattr(obj, attr) - - if attr_value is not None: - if isinstance(attr_value, dict): - for k in sorted(attr_value.keys()): - my_hash = (my_hash + hash(k)) * 1024 + hash(attr_value[k]) - elif isinstance(attr_value, (list, tuple)): - for entry in attr_value: - my_hash = (my_hash + hash(entry)) * 1024 - elif isinstance(attr_value, bool): - my_hash += TRUE_HASH_VALUE if attr_value else FALSE_HASH_VALUE - else: - my_hash += hash(attr_value) + val = getattr(obj, attr) + my_hash = my_hash * 1024 + _hash_value(val) return my_hash

1 0

[webwml/master] fix wording in fundraising director position
by arma＠torproject.org 07 Jun '18

07 Jun '18

commit 0971b2c5b0c0d1b3be1aff13163238cf3d4d2b6e Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Jun 7 14:30:11 2018 -0400 fix wording in fundraising director position addresses ticket 26325 --- about/en/jobs-fundraising-director.wml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/about/en/jobs-fundraising-director.wml b/about/en/jobs-fundraising-director.wml index aaf75995..a38115e0 100644 --- a/about/en/jobs-fundraising-director.wml +++ b/about/en/jobs-fundraising-director.wml @@ -14,14 +14,15 @@ <h2>(Posted June 5, 2018)</h2> <p> -The Tor Project, Inc., a 501(c)(3) nonprofit organization that provides -technical infrastructure for privacy protection over the internet, +The Tor Project, Inc., a 501(c)(3) nonprofit organization advancing human +rights and freedoms by creating and deploying free and open source +anonymity and privacy technologies, is seeking a dynamic, creative, and organized Fundraising Director to help us grow and expand our funding base. The Fundraising Director will be responsible for planning, directing and coordinating all fundraising activities, with an emphasis on diversifying our funding sources. The ideal candidate will have at least five years of leadership experience -working in the fundraising department of nonprofit organization. This +working in the fundraising department of a nonprofit organization. This person must be able to straddle the worlds of technology and fundraising. The Tor Project is funded in part by government research and development contracts, and in part by individual, foundation and

1 0

[webwml/master] line-wrap (no actual changes yet)
by arma＠torproject.org 07 Jun '18

07 Jun '18

commit 7d4bbd2af6b72c79702e444870261ab923e4d602 Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Jun 7 14:28:53 2018 -0400 line-wrap (no actual changes yet) --- about/en/jobs-fundraising-director.wml | 120 ++++++++++++++++++++++++--------- 1 file changed, 89 insertions(+), 31 deletions(-) diff --git a/about/en/jobs-fundraising-director.wml b/about/en/jobs-fundraising-director.wml index de72b0d0..aaf75995 100644 --- a/about/en/jobs-fundraising-director.wml +++ b/about/en/jobs-fundraising-director.wml @@ -14,62 +14,120 @@ <h2>(Posted June 5, 2018)</h2> <p> -The Tor Project, Inc., a 501(c)(3) nonprofit organization that provides technical infrastructure for privacy protection over the internet, is seeking a dynamic, creative, and organized Fundraising Director to help us grow and expand our funding base. The Fundraising Director will be responsible for planning, directing and coordinating all fundraising activities, with an emphasis on diversifying our funding sources. The ideal candidate will have at least five years of leadership experience working in the fundraising department of nonprofit organization. This person must be able to straddle the worlds of technology and fundraising. The Tor Project is funded in part by government research and development contracts, and in part by individual, foundation and corporate donations. The ability to talk about the Tor Project's work to all different types of current and potential donors is essential. +The Tor Project, Inc., a 501(c)(3) nonprofit organization that provides +technical infrastructure for privacy protection over the internet, +is seeking a dynamic, creative, and organized Fundraising Director to +help us grow and expand our funding base. The Fundraising Director will +be responsible for planning, directing and coordinating all fundraising +activities, with an emphasis on diversifying our funding sources. The +ideal candidate will have at least five years of leadership experience +working in the fundraising department of nonprofit organization. This +person must be able to straddle the worlds of technology and +fundraising. The Tor Project is funded in part by government research +and development contracts, and in part by individual, foundation and +corporate donations. The ability to talk about the Tor Project's work +to all different types of current and potential donors is essential. </p> - <p> -This senior level position will report directly to the Executive Director and will be part of the organization's leadership team. The Fundraising Director will set and guide the strategy for all of our fundraising, including increasing contributions from government, foundation, corporate, and individual donors. This is a new, hands-on position for a highly skilled fundraising professional. +This senior level position will report directly to the Executive Director +and will be part of the organization's leadership team. The Fundraising +Director will set and guide the strategy for all of our fundraising, +including increasing contributions from government, foundation, corporate, +and individual donors. This is a new, hands-on position for a highly +skilled fundraising professional. </p> <h2>Responsibilities:</h2> <ul> -<li>Work with Tor Project program staff to understand and communicate effectively about the range of our projects and accomplishments.</li> +<li>Work with Tor Project program staff to understand and communicate +effectively about the range of our projects and accomplishments.</li> -<li>Grow a major gifts program, including identification, cultivation, and solicitation of major donors.</li> -<li> -Oversee the flow of our donation system, from initial ask to thank you.</li> -<li>Oversee grant seeking, including research, proposal writing, and reporting requirements.</li> -<li>Interact with our current government and foundation program officers, making sure they are receiving necessary reports and keeping them apprised of our work.</li> +<li>Grow a major gifts program, including identification, cultivation, +and solicitation of major donors.</li> +<li>Oversee the flow of our donation system, from initial ask to thank +you.</li> +<li>Oversee grant seeking, including research, proposal writing, and +reporting requirements.</li> +<li>Interact with our current government and foundation program officers, +making sure they are receiving necessary reports and keeping them apprised +of our work.</li> <li>Oversee our annual crowdsourced funding campaign.</li> <li>Supervise and collaborate with our grant writer.</li> -<li>Write and edit grant proposals, grant reports, year-end report, conference one-pagers and other fundraising-specific writing.</li> +<li>Write and edit grant proposals, grant reports, year-end report, +conference one-pagers and other fundraising-specific writing.</li> <li>Plan fundraising events, as appropriate.</li> -<li>Determine appropriate Tor Project booth presence at conferences and events.</li> -<li>Ensure that the time of the Executive Director is used efficiently for fundraising.</li> +<li>Determine appropriate Tor Project booth presence at conferences +and events.</li> +<li>Ensure that the time of the Executive Director is used efficiently +for fundraising.</li> </ul> <h2>Qualifications:</h2> <ul> -<li>Demonstrated track record of success in raising major gifts and writing complex proposals for various audiences, including foundations.</li> -<li>Knowledge and experience in fundraising techniques, particularly major gift fundraising. Must be comfortable making pitches and personally asking people for money.</li> -<li>Excellent verbal, written, and editing skills, including the ability to produce high quality work quickly and under deadline pressure.</li> -<li>Ability to develop fundraising budgets and prepare financial reports.</li> -<li>Comfortable with highly technical topics and ability to explain them clearly and accurately to non-technical audiences. Must embrace the mission of the Tor Project.</li> -<li>Strong generalist understanding of the basic mechanics of how the internet works, as well as issues related to privacy, security, censorship, and surveillance.</li> -<li>Excellent computer skills, including familiarity with donation tracking systems. (We use the open source CiviCRM.)</li> -<li>Experience with, or willingness to learn how to use, communications and collaboration technologies such as PGP, IRC, Jitsi, Signal, WordPress, and etherpads.</li> -<li>Hard working and highly organized with superior attention to detail.</li> +<li>Demonstrated track record of success in raising major gifts +and writing complex proposals for various audiences, including +foundations.</li> +<li>Knowledge and experience in fundraising techniques, particularly +major gift fundraising. Must be comfortable making pitches and personally +asking people for money.</li> +<li>Excellent verbal, written, and editing skills, including the ability +to produce high quality work quickly and under deadline pressure.</li> +<li>Ability to develop fundraising budgets and prepare financial +reports.</li> +<li>Comfortable with highly technical topics and ability to explain +them clearly and accurately to non-technical audiences. Must embrace +the mission of the Tor Project.</li> +<li>Strong generalist understanding of the basic mechanics of how +the internet works, as well as issues related to privacy, security, +censorship, and surveillance.</li> +<li>Excellent computer skills, including familiarity with donation +tracking systems. (We use the open source CiviCRM.)</li> +<li>Experience with, or willingness to learn how to use, communications +and collaboration technologies such as PGP, IRC, Jitsi, Signal, WordPress, +and etherpads.</li> +<li>Hard working and highly organized with superior attention to +detail.</li> <li>Willingness to take responsibility and initiative.</li> -<li>Highly collaborative, preferably with experience working with and as part of remote teams in different time zones.</li> -<li>Prior experience working on U.S. government grants and contracts is a plus.</li> -<li>Willingness to travel to international meetings at least twice a year.</li> -<li>The successful candidate should be eager to be an inspiring mentor and colleague to the board and staff of the Tor Project.</li> +<li>Highly collaborative, preferably with experience working with and +as part of remote teams in different time zones.</li> +<li>Prior experience working on U.S. government grants and contracts is +a plus.</li> +<li>Willingness to travel to international meetings at least twice +a year.</li> +<li>The successful candidate should be eager to be an inspiring mentor +and colleague to the board and staff of the Tor Project.</li> </ul> <p> -The Tor Project's workforce is smart and committed. Experience working with open source communities and/or a dedication to Internet freedom are added pluses. The Tor Project currently has a paid and contract staff of around 35 developers and operational support staff, plus many thousands of volunteers who contribute to our work. The ideal candidate will be energetic, unflappable and flexible, and will thrive in a highly-technical collaborative environment. +The Tor Project's workforce is smart and committed. Experience working +with open source communities and/or a dedication to Internet freedom are +added pluses. The Tor Project currently has a paid and contract staff of +around 35 developers and operational support staff, plus many thousands +of volunteers who contribute to our work. The ideal candidate will be +energetic, unflappable and flexible, and will thrive in a highly-technical +collaborative environment. </p> <p> -This is a full-time, hands-on position, which can be done remotely or in our office in Seattle, WA. Flexible salary, depending on experience. The Tor Project has a competitive benefits package, including a generous PTO policy; 14 paid holidays per year (including the week between Christmas and New Year's, when the office is closed); health, vision, dental, disability, and life insurance paid in full for employee; flexible work schedule; and occasional travel opportunities. +This is a full-time, hands-on position, which can be done remotely or in +our office in Seattle, WA. Flexible salary, depending on experience. The +Tor Project has a competitive benefits package, including a generous PTO +policy; 14 paid holidays per year (including the week between Christmas +and New Year's, when the office is closed); health, vision, dental, +disability, and life insurance paid in full for employee; flexible work +schedule; and occasional travel opportunities. </p> <p> -To apply, send a cover letter and your resume to hr at torproject dot org with the subject "Fundraising Director." Tell us why you think you're the right person for this job, and please include links to writing samples. No phone calls please! +To apply, send a cover letter and your resume to hr at torproject dot org +with the subject "Fundraising Director." Tell us why you think you're +the right person for this job, and please include links to writing +samples. No phone calls please! </p> - <p> -The Tor Project, Inc., is an equal opportunity, affirmative action employer.</p> +<p> +The Tor Project, Inc., is an equal opportunity, affirmative action +employer.</p> </div>  <div id = "sidecol"> @@ -79,4 +137,4 @@ The Tor Project, Inc., is an equal opportunity, affirmative action employer.</p>  </div>  -#include <foot.wmi> \ No newline at end of file +#include <foot.wmi>

1 0

[tor-browser-build/master] Bug 24632: Make sure to use "Tor Browser.app" for `browserdir` on macOS
by gk＠torproject.org 07 Jun '18

07 Jun '18

commit fcb2a3707af71bcd564bf0dd8a563835eeea6b9b Author: Georg Koppen <gk(a)torproject.org> Date: Thu Jun 7 10:40:47 2018 +0000 Bug 24632: Make sure to use "Tor Browser.app" for `browserdir` on macOS --- projects/tor-browser/build | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/tor-browser/build b/projects/tor-browser/build index d807633..19aa657 100644 --- a/projects/tor-browser/build +++ b/projects/tor-browser/build @@ -311,7 +311,7 @@ cp $rootdir/[% c('input_files_by_name/firefox') %]/mar-tools-*.zip "$OUTDIR"/ SET xpi = '$rootdir/' _ c('input_files_by_name/firefox-langpacks') _ '/' _ lang _ '.xpi'; SET tbdir = '$distdir/tor-browser_' _ lang; IF c("var/osx"); - SET browserdir = tbdir _ '/TorBrowser.app'; + SET browserdir = tbdir _ '/Tor Browser.app'; ELSIF c("var/windows"); SET browserdir = tbdir _ '/Tor Browser/Browser'; ELSE;

1 0

[tor-browser-build/master] Bug 24632: Install xz-utils for macOS MAR file creation
by gk＠torproject.org 07 Jun '18

07 Jun '18

commit aabed936170b9ea88df2037e8d452dc5d9915f20 Author: Georg Koppen <gk(a)torproject.org> Date: Thu Jun 7 10:39:48 2018 +0000 Bug 24632: Install xz-utils for macOS MAR file creation --- projects/tor-browser/config | 1 + 1 file changed, 1 insertion(+) diff --git a/projects/tor-browser/config b/projects/tor-browser/config index 62ed70c..225a0bb 100644 --- a/projects/tor-browser/config +++ b/projects/tor-browser/config @@ -24,6 +24,7 @@ targets: - python - bzip2 - faketime + - xz-utils windows: var: arch_deps:

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits June 2018