Re: [tor-bugs] #22564 [Applications/Tor Browser]: Hide firefox sync

[Tor Bug Tracker & Wiki]

#22564: Hide firefox sync
-+-
 Reporter:  Dbryrtfbcbhgf|  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-7.0-issues, tbb-regression,  |  Actual Points:
  TorBrowserTeam201803   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by Dbryrtfbcbhgf):

 gk, it looks like Mozilla fixed this bug in Firefox 60 with this patch.
 https://hg.mozilla.org/mozilla-central/rev/109cd0a34ffe
 Can this be back ported to TOrBrowser 7.5.x ?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25682 [Core Tor/Tor]: Obsolete Tor Core Encryption, Only use SHA3/ed25519/curve25519 for building Circuits

[Tor Bug Tracker & Wiki]

#25682: Obsolete Tor Core Encryption, Only use SHA3/ed25519/curve25519 for 
building
Circuits
--+---
 Reporter:  Anony |  Owner:  (none)
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by teor):

 * status:  new => closed
 * version:  Tor: unspecified =>
 * resolution:   => duplicate
 * milestone:  Tor: unspecified =>


Comment:

 This is a duplicate of #25662, which has been closed, because we already
 have plans for these changes.

 Please stop posting duplicate tickets.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25680 [Applications/Tor Browser]: Can't use anything in Tor even checking network settings gives error

[Tor Bug Tracker & Wiki]

#25680: Can't use anything in Tor even checking network settings gives error
--+---
 Reporter:  greatormesby  |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by teor):

 * version:  Tor: unspecified =>
 * component:  Core Tor/Tor => Applications/Tor Browser
 * milestone:  Tor: unspecified =>


Comment:

 That picture is a picture of Tor Browser.

 This looks like the error that people get when they are running Kapersky
 antivirus (#25333).

 If you are using kapersky, try:

 2- open kaspersky settings -> additional -> Network-> Encrypt connection
 settings -> CHECK the do not scan encrypted connection

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25483 [Obfuscation/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
---+--
 Reporter:  arlolra|  Owner:  (none)
 Type:  project| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by dcf):

 Replying to [comment:15 boklm]:
 > I have been able to do a build, and I get a tarball containing the same
 files, except that my version also includes some files in the directory
 `webrtc/include/chromium/`:
 > https://people.torproject.org/~boklm/tmp/webrtc-
 88f5d9180eae78a6162cccd78850ff416eb82483-windows-x86_64-ba8356.tar.gz
 > It seems the reason is that I have a chromium directory in
 gclient/webrtc/src, probably from a previous build.

 Thanks for testing and for the suggestions. I suppose we should more
 careful in the recursive search for header files. At least the files we
 had in common are identical, according to diffoscope.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25423 [Core Tor/Stem]: Treat 'ExitRelay 0' as a reject-all policy

[Tor Bug Tracker & Wiki]

#25423: Treat 'ExitRelay 0' as a reject-all policy
---+
 Reporter:  atagar |  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by dmr):

 Replying to [comment:2 arma]:
 > Is stem looking at a 'getconf exitpolicy'?
 >
 > It seems like it should instead be doing a 'getinfo exitpolicy', which
 should tell it what Tor is actually using as its exit policy.

 I've looked into this a bit so far; stem is definitely using GETCONF
 ExitPolicy:
 
https://gitweb.torproject.org/stem.git/tree/stem/control.py?id=72700087b94f2889b5b364738a1178c324862ba5#n1292
 {{{
 for policy_line in self.get_conf('ExitPolicy', multiple = True):
   policy += policy_line.split(',')
 }}}

 On a local test relay (standard Debian9 tor stable) with torrc...
 {{{
 # configuration for local relay, for exploratory testing
 DataDirectory 
 SocksPort 1112
 ORPort 1113
 ControlPort 
 HashedControlPassword 
 ExitRelay 0
 PublishServerDescriptor 0
 AssumeReachable 1
 DownloadExtraInfo 1
 Log notice stdout
 Log notice file /tor_log
 }}}
 ... `str(controller.get_exit_policy())` returns:
 {{{
 'reject 0.0.0.0/8:*, reject 169.254.0.0/16:*, reject 127.0.0.0/8:*, reject
 192.168.0.0/16:*, reject 10.0.0.0/8:*, reject 172.16.0.0/12:*, reject
 107.5.239.102:*, reject *:25, reject *:119, reject *:135-139, reject
 *:445, reject *:563, reject *:1214, reject *:4661-4666, reject
 *:6346-6429, reject *:6699, reject *:6881-6999, accept *:*'controller.
 }}}
 On a standard Debian9 tor client (i.e. no relaying),
 `str(controller.get_exit_policy())` returns the same.

 Obviously these are both incorrect.

 I'm looking into switching `get_exit_policy()` to use `controller.get_info
 ('exit-policy/full')` instead.
 I think that will cover a lot of the more-complicated `get_conf` /
 `get_info` logic (e.g. `get_info('exit-policy/default')`) that currently
 exists in `get_exit_policy()`, but I'm checking fairly conservatively.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25423 [Core Tor/Stem]: Treat 'ExitRelay 0' as a reject-all policy

[Tor Bug Tracker & Wiki]

#25423: Treat 'ExitRelay 0' as a reject-all policy
---+--
 Reporter:  atagar |  Owner:  dmr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by dmr):

 * owner:  atagar => dmr
 * status:  new => assigned


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25681 [Obfuscation/Snowflake]: Defend against flooding of the broker by low bandwidth snowflakes

[Tor Bug Tracker & Wiki]

#25681: Defend against flooding of the broker by low bandwidth snowflakes
---+
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by arlolra):

 Could fall under the rubric of #25593

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25682 [Core Tor/Tor]: Obsolete Tor Core Encryption, Only use SHA3/ed25519/curve25519 for building Circuits

[Tor Bug Tracker & Wiki]

#25682: Obsolete Tor Core Encryption, Only use SHA3/ed25519/curve25519 for 
building
Circuits
--+--
 Reporter:  Anony |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

 * priority:  Immediate => Medium
 * severity:  Critical => Normal


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #13510 [Applications/Tor Browser]: Master password can't be changed from default

[Tor Bug Tracker & Wiki]

#13510: Master password can't be changed from default
--+--
 Reporter:  User11|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by etienne):

 Where is that security.nocertdb ?

 I can't find it in about:config

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #13510 [Applications/Tor Browser]: Master password can't be changed from default

[Tor Bug Tracker & Wiki]

#13510: Master password can't be changed from default
--+--
 Reporter:  User11|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by etienne):

 Please consider tackling this bug, it's an important/basic security
 feature !

 This bug was opened 3 years ago 

 Unfortunately I can't help, I don't have skills to help.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25682 [Core Tor/Tor]: Obsolete Tor Core Encryption, Only use SHA3/ed25519/curve25519 for building Circuits

[Tor Bug Tracker & Wiki]

#25682: Obsolete Tor Core Encryption, Only use SHA3/ed25519/curve25519 for 
building
Circuits
--+--
 Reporter:  Anony |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Immediate |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Critical  |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 a) Better crypto (replaced SHA1/DH/RSA1024 with SHA3/ed25519/curve25519)

 Don't allow New Tor nodes to build circuits with obsolete Tor Nodes unless
 they support the newer encryption version 0.3.2.9 - 2018-01-09

 Only use the old crypto to resolve old .Onion honeypots...

 Only use SHA3/ed25519/curve25519 to build New 3 hop Circuits.  This will
 provide better anon for hidden services which use the same transport
 system.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21816 [Core Tor/Tor]: Add support for Pluggable Transports 2.0

[Tor Bug Tracker & Wiki]

#21816: Add support for Pluggable Transports 2.0
-+-
 Reporter:  chelseakomlo |  Owner:
 |  dasyatid1
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, tor-pt, tor-bridge,  |  Actual Points:
  design, pt2, review-group-23, review-  |
  group-24, 034-triage-20180328, |
  034-removed-20180328   |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
 |  SponsorM-can
-+-
Changes (by ahf):

 * cc: ahf (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25483 [Obfuscation/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
---+--
 Reporter:  arlolra|  Owner:  (none)
 Type:  project| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by boklm):

 Replying to [comment:15 boklm]:
 > I have been able to do a build, and I get a tarball containing the same
 files, except that my version also includes some files in the directory
 `webrtc/include/chromium/`:
 > https://people.torproject.org/~boklm/tmp/webrtc-
 88f5d9180eae78a6162cccd78850ff416eb82483-windows-x86_64-ba8356.tar.gz

 It seems the reason is that I have a `chromium` directory in
 `gclient/webrtc/src`, probably from a previous build.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25483 [Obfuscation/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
---+--
 Reporter:  arlolra|  Owner:  (none)
 Type:  project| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by boklm):

 Replying to [comment:14 dcf]:

 >This branch lets the webrtc build work for windows-i686. To test it,
 first `get fetch` an updated go-webrtc as described above. If have done a
 build in this directory previously, run
 >{{{
 >rm gclient/webrtc/.gclient
 >}}}
 >The .gclient will be regenerated with the addition of `target_os =
 ['win']`, which will cause `gclient sync` to pull the prebuilt clang
 cross-compiler.

 I think we could add something like this, to automatically remove
 `gclient/webrtc/src/testing/{gmock,gtest}`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_25483_v0=d5514f7f3b566cf37bfc59ec8105a96130577ff2

 And this to remove the `.gclient` file if it does not contain the
 target_os line:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_25483_v0=60a0b31b389fa2ca47dfbe305f9f9211b58f509e

 > The output of the build is a file, out/webrtc/webrtc-
 88f5d9180eae78a6162cccd78850ff416eb82483-windows-x86_64-ba8356.tar.gz. You
 can compare it against mine:
 >   https://people.torproject.org/~dcf/pt-bundle/snowflake/webrtc-
 88f5d9180eae78a6162cccd78850ff416eb82483-windows-x86_64-ba8356.tar.gz

 I have been able to do a build, and I get a tarball containing the same
 files, except that my version also includes some files in the directory
 `webrtc/include/chromium/`:
 https://people.torproject.org/~boklm/tmp/webrtc-
 88f5d9180eae78a6162cccd78850ff416eb82483-windows-x86_64-ba8356.tar.gz

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24342 [Core Tor]: Various spec fixes to dir-spec, rend-spec-v3

[Tor Bug Tracker & Wiki]

#24342: Various spec fixes to dir-spec, rend-spec-v3
-+-
 Reporter:  filippo  |  Owner:  asn
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, review-group-26, review-   |  Actual Points:
  group-27, 033-triage-20180320, fast-fix,   |
  033-included-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by asn):

 Replying to [comment:17 nickm]:
 > What are we merging here?  The master branch at
 ab22bd1dce3b62b6120300fdead958c6924fe553?

 Yes indeed. The four commits at that `master` branch.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25681 [Obfuscation/Snowflake]: Defend against flooding of the broker by low bandwidth snowflakes

[Tor Bug Tracker & Wiki]

#25681: Defend against flooding of the broker by low bandwidth snowflakes
---+
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 An adversary may attempt to flood the broker by thousands of low bandwidth
 snowflakes, as a result users will have a higher chance of happening on
 them thereby deteriorating their experience.

 Maybe there should be some way to ensure that their bandwidth is higher
 than some level before they can be distributed by the broker.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24031 [Core Tor/Tor]: Protover.rs could use a better algorithm

[Tor Bug Tracker & Wiki]

#24031: Protover.rs could use a better algorithm
-+-
 Reporter:  nickm|  Owner:  isis
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  rust, 033-must, protover, security,  |  Actual Points:  5
  033-triage-20180326, 033-included-20180326 |
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  SponsorM-can
-+-

Comment (by nickm):

 Update: I like the fixups you made last night, and I think I buy your
 argument about the new C protover_all_supported implementation.  There are
 a couple of comments on some of your later commits that you didn't get to
 yet, however -- I'd especially want to know about the testing-mode build
 one on  f6377a4.

 Once you're happy with that, our next step is to make a new _r5 branch,
 and get the branch into usable condition.  There are two changes that will
 be needed for that:
   * It needs to be based on maint-0.3.3 if we're going to try to merge it
 into 0.3.3; the current version of this branch is baased on master.
   * It needs to be squashed.

 I tried rebasing and squashing it myself, using 'git rebase master --onto
 maint-0.3.3 --autosquash -i', but I ran into conflicts that I'd rather not
 try to resolve myself.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25680 [Core Tor/Tor]: Can't use anything in Tor even checking network settings gives error

[Tor Bug Tracker & Wiki]

#25680: Can't use anything in Tor even checking network settings gives error
--+---
 Reporter:  greatormesby  |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by cypherpunks):

 * status:  new => needs_information


Comment:

 Are you using some antivirus?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25680 [Core Tor/Tor]: Can't use anything in Tor even checking network settings gives error

[Tor Bug Tracker & Wiki]

#25680: Can't use anything in Tor even checking network settings gives error
--+--
 Reporter:  greatormesby  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by greatormesby):

 Hope you can help and thanks in advance

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25680 [Core Tor/Tor]: Can't use anything in Tor even checking network settings gives error

[Tor Bug Tracker & Wiki]

#25680: Can't use anything in Tor even checking network settings gives error
--+--
 Reporter:  greatormesby  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by greatormesby):

 * Attachment "tor2.PNG" added.

 example of message

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24342 [Core Tor]: Various spec fixes to dir-spec, rend-spec-v3

[Tor Bug Tracker & Wiki]

#24342: Various spec fixes to dir-spec, rend-spec-v3
-+-
 Reporter:  filippo  |  Owner:  asn
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, review-group-26, review-   |  Actual Points:
  group-27, 033-triage-20180320, fast-fix,   |
  033-included-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 What are we merging here?  The master branch at
 ab22bd1dce3b62b6120300fdead958c6924fe553?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25680 [Core Tor/Tor]: Can't use anything in Tor even checking network settings gives error

[Tor Bug Tracker & Wiki]

#25680: Can't use anything in Tor even checking network settings gives error
--+--
 Reporter:  greatormesby  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Major |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25675 [Core Tor/Tor]: fix CID 1433643

[Tor Bug Tracker & Wiki]

#25675: fix CID 1433643
--+
 Reporter:  catalyst  |  Owner:  catalyst
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.7.3-rc
 Severity:  Normal| Resolution:  fixed
 Keywords:  coverity  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor3
--+
Changes (by nickm):

 * status:  needs_review => closed
 * resolution:   => fixed


Comment:

 Solid work.  I hadn't thought of this move-the-pointer-out solution.
 Merging!

 I agree that no backport is needed, since we're not going to backport any
 more restart-fixes to 0.3.3.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23793 [Webpages/Website]: Public users should not be allowed to edit your ethercalc

[Tor Bug Tracker & Wiki]

#23793: Public users should not be allowed to edit your ethercalc
--+-
 Reporter:  Dbryrtfbcbhgf |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Major | Resolution:  wontfix
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by hiro):

 * status:  new => closed
 * resolution:   => wontfix


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24782 [Core Tor/Tor]: Set a lower default MaxMemInQueues value

[Tor Bug Tracker & Wiki]

#24782: Set a lower default MaxMemInQueues value
-+-
 Reporter:  teor |  Owner:  ahf
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, tor-dos, 033-must,|  Actual Points:
  security, 033-triage-20180320, |
  033-included-20180320  |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by ahf):

 We should probably come up with a decision here on what we'd like to do
 for us to get this into 033 (if we think it's still important).

 I think David's comment in comment 11 looks reasonable, but reaching some
 kind of consensus would be good.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25428 [Webpages/Website]: Please add job description to website: Community Liaison

[Tor Bug Tracker & Wiki]

#25428: Please add job description to website: Community Liaison
--+
 Reporter:  ewyatt|  Owner:  (none)
 Type:  task  | Status:  closed
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by hiro):

 * status:  new => closed
 * resolution:   => fixed


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25679 [Core Tor/Tor]: Default for TOR_RUST_DEPENDENCIES is wrong?

[Tor Bug Tracker & Wiki]

#25679: Default for TOR_RUST_DEPENDENCIES is wrong?
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  fast-fix  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  assigned => needs_review


Comment:

 Tiny fix in `bug25679_033`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25679 [Core Tor/Tor]: Default for TOR_RUST_DEPENDENCIES is wrong?

[Tor Bug Tracker & Wiki]

#25679: Default for TOR_RUST_DEPENDENCIES is wrong?
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  fast-fix
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Try building Tor using the tor-rust-dependencies submodule, without
 actually setting TOR_RUST_DEPENDENCIES.  It's supposed to work, but it
 doesn't: it looks at the wrong directory.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24795 [Core Tor/Tor]: test_rust fails on osx with "can't find crate for `libc`"

[Tor Bug Tracker & Wiki]

#24795: test_rust fails on osx with "can't find crate for `libc`"
-+-
 Reporter:  nickm|  Owner:  isis
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, osx, tests, 032-backport,  |  worksforme
  033-triage-20180320, fast-fix  |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorM-can
-+-
Changes (by nickm):

 * status:  needs_information => closed
 * resolution:   => worksforme


Comment:

 Oh. This ''was'' me, but after a bunch of experimentation, it turned out
 to have been caused by something stale in one of the cargo directories
 inside the tor build.  "git clean -xf" made things work again.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #23846 [Core Tor/Tor]: Use libtool for building shared library

[Tor Bug Tracker & Wiki]

#23846: Use libtool for building shared library
-+-
 Reporter:  hellais  |  Owner:  sbs
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-mobile, s8-api,  |  Actual Points:
  034-triage-20180328|
Parent ID:  #23684   | Points:
 Reviewer:  ahf  |Sponsor:
 |  Sponsor8
-+-
Changes (by ahf):

 * status:  needs_review => needs_revision


Comment:

 I think overall this looks like it's fine, but I would like you to do the
 following:

 1. Fork the https://github.com/torproject/tor.git repository to your own
 account.
 2. Push your patches to a branch in your fork.

 That should allow us to see if everything is going well with our Travis
 CI. Around build-system changes it is probably a very good idea to be sure
 we don't break anything here.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25440 [Core Tor/Tor]: Broken openat syscall in Sandbox mode

[Tor Bug Tracker & Wiki]

#25440: Broken openat syscall in Sandbox mode
-+-
 Reporter:  ageisp0lis   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.3-alpha
 Severity:  Normal   | Resolution:
 Keywords:  sandbox, 033-must, regression,   |  Actual Points:
  033-triage-20180326, 033-included-20180326,|
  AffectsTails   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by intrigeri):

 * cc: intrigeri (added)
 * keywords:
 sandbox, 033-must, regression, 033-triage-20180326,
 033-included-20180326
 =>
 sandbox, 033-must, regression, 033-triage-20180326,
 033-included-20180326, AffectsTails


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25440 [Core Tor/Tor]: Broken openat syscall in Sandbox mode

[Tor Bug Tracker & Wiki]

#25440: Broken openat syscall in Sandbox mode
-+-
 Reporter:  ageisp0lis   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.3-alpha
 Severity:  Normal   | Resolution:
 Keywords:  sandbox, 033-must, regression,   |  Actual Points:
  033-triage-20180326, 033-included-20180326 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by intrigeri):

 I see a very similar startup failure on the development version of Tails
 based on Debian 10 (Buster); to r is 0.3.2.10-1, libc6 is 2.27-2 (both
 from Debian testing).


 {{{
 [notice] Tor 0.3.2.10 (git-0edaa32732ec8930) running on Linux with
 Libevent 2.1.8-stable, OpenSSL 1.1.0h, Zlib 1.2.8, Liblzma 5.2.2, and
 Libzstd 1.3.3.
 [notice] Tor can't help you if you use it wrong! Learn how to be safe at
 https://www.torproject.org/download/download#warning
 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-
 torrc".
 [notice] Read configuration file "/etc/tor/torrc".
 [warn] Skipping obsolete configuration option 'ControlListenAddress'
 [warn] Skipping obsolete configuration option 'TransListenAddress'
 [warn] Skipping obsolete configuration option 'WarnUnsafeSocks'
 lid
 [notice] Tor 0.3.2.10 (git-0edaa32732ec8930) running on Linux with
 Libevent 2.1.8-stable, OpenSSL 1.1.0h, Zlib 1.2.8, Liblzma 5.2.2, and
 Libzstd 1.3.3.
 [notice] Tor can't help you if you use it wrong! Learn how to be safe at
 https://www.torproject.org/download/download#warning
 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-
 torrc".
 [notice] Read configuration file "/etc/tor/torrc".
 [warn] Skipping obsolete configuration option 'ControlListenAddress'
 [warn] Skipping obsolete configuration option 'TransListenAddress'
 [warn] Skipping obsolete configuration option 'WarnUnsafeSocks'
 [notice] Scheduler type KIST has been enabled.
 [notice] Opening Socks listener on 127.0.0.1:9050
 [notice] Opening Socks listener on 127.0.0.1:9062
 [notice] Opening Socks listener on 127.0.0.1:9150
 [notice] Opening DNS listener on 127.0.0.1:5353
 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040
 [notice] Opening Control listener on 127.0.0.1:9052
  T= 1522412451
 (Sandbox) Caught a bad syscall attempt (syscall openat)
 /usr/bin/tor(+0x1a2f3a)[0x5fe2178aff3a]
 /lib/x86_64-linux-gnu/libpthread.so.0(open64+0x4b)[0x7b392350d3ab]
 /usr/bin/tor(tor_open_cloexec+0x40)[0x5fe217896260]
 /usr/bin/tor(start_writing_to_file+0x17a)[0x5fe2178a9a3a]
 /usr/bin/tor(+0x19cb1b)[0x5fe2178a9b1b]
 /usr/bin/tor(+0x19cc68)[0x5fe2178a9c68]
 /usr/bin/tor(networkstatus_set_current_consensus+0xc99)[0x5fe21776c3e9]
 /usr/bin/tor(connection_dir_reached_eof+0x14cb)[0x5fe217841ccb]
 /usr/bin/tor(+0x10c9d9)[0x5fe2178199d9]
 /usr/bin/tor(+0x52a1e)[0x5fe21775fa1e]
 /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x229ba)[0x7b39249ac9ba]
 /usr/lib/x86_64-linux-
 gnu/libevent-2.1.so.6(event_base_loop+0x5a7)[0x7b39249ad537]
 /usr/bin/tor(do_main_loop+0x28d)[0x5fe21776096d]
 /usr/bin/tor(tor_main+0xe1d)[0x5fe21776378d]
 /usr/bin/tor(main+0x19)[0x5fe21775c1b9]
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7b3922f5fa87]
 /usr/bin/tor(_start+0x2a)[0x5fe21775c20a]
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #20212 [Core Tor/Tor]: Tor can be forced to open too many circuits by embedding .onion resources

[Tor Bug Tracker & Wiki]

#20212: Tor can be forced to open too many circuits by embedding .onion 
resources
-+-
 Reporter:  gacar|  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  guard-discovery, |  Actual Points:
  TorBrowserTeam201803, 034-roadmap-proposed,|
  security   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * keywords:  guard-discovery, TorBrowserTeam201803 => guard-discovery,
 TorBrowserTeam201803, 034-roadmap-proposed, security


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25678 [Core Tor/Tor]: Clarify how ed25519 extended private keys are used in rend-spec-v3.txt

[Tor Bug Tracker & Wiki]

#25678: Clarify how ed25519 extended private keys are used in rend-spec-v3.txt
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, review-group-26, review-   |  Actual Points:
  group-27, 033-triage-20180320, fast-fix,   |
  033-included-20180326  |
Parent ID:  #24342   | Points:
 Reviewer:   |Sponsor:
-+-
Description changed by asn:

Old description:

> In #24342 we started specifying how extended private keys are used in
> rend-spec-v3.txt but we didn't do it in a complete manner (see
> comment:9).
>
> We should improve the state of the spec on this regard.

New description:

 In #24342 we started specifying how extended private keys are used in
 rend-spec-v3.txt but we didn't do it in a complete manner (see
 comment:9:ticket:24342).

 We should improve the state of the spec on this regard.

--

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24342 [Core Tor]: Various spec fixes to dir-spec, rend-spec-v3

[Tor Bug Tracker & Wiki]

#24342: Various spec fixes to dir-spec, rend-spec-v3
-+-
 Reporter:  filippo  |  Owner:  asn
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, review-group-26, review-   |  Actual Points:
  group-27, 033-triage-20180320, fast-fix,   |
  033-included-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * status:  assigned => merge_ready


Comment:

 Marking this as `merge_ready` since it contains very useful fixes that
 should be merged ASAP.

 I opened #25678 to resolve the issues from comment:9 in the future, since
 I tried to do it on the spot but clarifying how extended private keys are
 used in ed25519 (and in hierarchical key derivation schemes) is not an
 easy fix.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25678 [Core Tor/Tor]: Clarify how ed25519 extended private keys are used in rend-spec-v3.txt

[Tor Bug Tracker & Wiki]

#25678: Clarify how ed25519 extended private keys are used in rend-spec-v3.txt
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core |Version:
  Tor/Tor|   Keywords:  tor-spec, review-group-26, review-
 Severity:  Normal   |  group-27, 033-triage-20180320, fast-fix,
 |  033-included-20180326
Actual Points:   |  Parent ID:  #24342
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 In #24342 we started specifying how extended private keys are used in
 rend-spec-v3.txt but we didn't do it in a complete manner (see comment:9).

 We should improve the state of the spec on this regard.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25552 [Core Tor/Tor]: prop224: Onion service rev counters are useless and actually harmful for scalability

[Tor Bug Tracker & Wiki]

#25552: prop224: Onion service rev counters are useless and actually harmful for
scalability
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.9
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs prop224 034-roadmap-proposed  |  Actual Points:
Parent ID:   | Points:  4
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * keywords:  tor-hs prop224 => tor-hs prop224 034-roadmap-proposed


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25545 [Core Tor/Tor]: Figure out default vanguard script parameters

[Tor Bug Tracker & Wiki]

#25545: Figure out default vanguard script parameters
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-guard, guard-discovery, 034  |  Actual Points:
  -roadmap-master, 034-triage-20180328,  |
  034-included-20180328  |
Parent ID:   | Points:
 Reviewer:  mikeperry|Sponsor:
 |  SponsorV
-+-

Comment (by asn):

 Hello, I just pushed a first draft of the vanguard simulator in:
 https://github.com/asn-d6/vanguard_simulator

 Mike, if you want, check it out and let me know if it works for you.

 I plan to work more on it next week and try to get some useful data.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25483 [Obfuscation/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
---+--
 Reporter:  arlolra|  Owner:  (none)
 Type:  project| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by dcf):

 * status:  new => needs_review


Comment:

 I've made progress with cross-compiling webrtc for windows-x86_64. It's in
 two branches. The first branch just upgrades webrtc to branch-heads/64,
 which has the cross-compiling support. The second branch builds off the
 first and adds a build script for windows.

 The build is currently using the prebuilt clang cross-compiler that Google
 puts among the dependencies of webrtc. Eventually we will have to make it
 use our own compiler instead, as we already do on mac and linux. Reliance
 on the prebuilt compiler is the reason why the build currently only works
 for windows-x86_64, not windows-i686: there's no 32-bit prebuilt compiler
 available.

  https://github.com/uumaro/tor-browser-build/commits/webrtc-64 (currently
 [https://github.com/uumaro/tor-browser-
 build/commits/c8048d746ca176808225a428b8820996d65139f8 c8048d746c])::
This branch updates the build scripts to use a webrtc based on branch-
 heads/64. It depends on having a go-webrtc that also supports the branch-
 heads/64 API. That code hasn't been merged into go-webrtc yet, but there
 is [https://github.com/keroserene/go-webrtc/pull/79 a pull request] for
 it. To test the code before the go-webrtc changes have been merged, do
 this in the tor-browser-build directory before `make`:
{{{
cd git_clones/go-webrtc/
git fetch https://github.com/uumaro/go-webrtc/ branch-heads-64
cd ..
}}}
This branch can be merged independently of the windows code, once the
 go-webrtc pull request goes through.
  https://github.com/uumaro/tor-browser-build/commits/webrtc-win (currently
 [https://github.com/uumaro/tor-browser-
 build/commits/08613622f61c2ece16db1115b14df481c80838a0 08613622f6])::
This branch lets the webrtc build work for windows-i686. To test it,
 first `get fetch` an updated go-webrtc as described above. If have done a
 build in this directory previously, run
{{{
rm gclient/webrtc/.gclient
}}}
The .gclient will be regenerated with the addition of `target_os =
 ['win']`, which will cause `gclient sync` to pull the prebuilt clang
 cross-compiler. If you have not yet done a build in this directory, then
 you will need to do
{{{
make submodule-update
}}}
Then run
{{{
rbm/rbm build webrtc --target testbuild --target torbrowser-windows-
 x86_64
}}}
If you want to test that other targets still work, do
{{{
make testbuild
}}}

 The output of the build is a file, out/webrtc/webrtc-
 88f5d9180eae78a6162cccd78850ff416eb82483-windows-x86_64-ba8356.tar.gz. You
 can compare it against mine:
   https://people.torproject.org/~dcf/pt-bundle/snowflake/webrtc-
 88f5d9180eae78a6162cccd78850ff416eb82483-windows-x86_64-ba8356.tar.gz

 A few comments on the second branch:
  * [https://github.com/uumaro/tor-browser-
 build/commit/7a26f7ae9bde88101f8922c1b340c579a5fd55e6 I compiled my own
 Windows SDK] using the instructions in comment:13 and stashed it in my
 people.torproject.org space. I have [https://github.com/uumaro/tor-
 browser-build/blob/08613622f61c2ece16db1115b14df481c80838a0/TODO.WEBRTC a
 todo] to check if we really need this separate SDK, or if the header files
 in mingw-w64 are enough.
  * The upstream cross-compiling instructions say to put the Windows SDK in
 a case-insensitive [http://www.brain-dump.org/projects/ciopfs/ ciopfs]
 mount, so that, for example, code can `#include ` when the
 file is actually called WinSock2.h. I tried that initially, but I couldn't
 get ciopfs to work inside the container. boklm gave me a hint that I
 haven't tried yet. In the meantime, though, I [https://github.com/uumaro
 /tor-browser-build/commit/d0f6fcbe6cfec380b8cd3612de52e3a5b6dff8e0
 disabled ciopfs] and worked around case sensitivity with a lot of
 symlinks. I left it in the branch history for now.

 I haven't yet tried actually doing anything with the generated libwebrtc-
 windows-amd64-magic.lib.

 I'm not asking for any of this code to be merged right now. But I would
 appreciate some review of the code (this is my first time writing for
 rbm), and a check to see if the commands above work for you.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online

[tor-bugs] #25677 [Core Tor]: Tor startup crash with Sandbox 1 in torrc.d - sandbox_intern_string(): Bug: No interned sandbox parameter found

[Tor Bug Tracker & Wiki]

#25677: Tor startup crash with Sandbox 1 in torrc.d - sandbox_intern_string(): 
Bug:
No interned sandbox parameter found
---+
 Reporter:  adrelanos  |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor   |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 Tor from deb.torproject.org. Inside Whonix 14.

 {{{dpkg -l | grep tor}}}

 {{{
 ii  tor   0.3.2.10-1~d90.stretch+1
 amd64anonymizing overlay network for TCP
 }}}

 {{{
 user@host:~$ cat /etc/tor/torrc
 ## Do not edit this file!
 ## Please create and add modifications to the following file instead:
 ## /usr/local/etc/torrc.d/50_user.conf

 %include /etc/torrc.d/95_whonix.conf
 user@host:~$ cat /etc/torrc.d/95_whonix.conf
 ## Do not edit this file!
 ## Please create and add modifications to the following file instead:
 ## /usr/local/etc/torrc.d/50_user.conf
 %include /usr/local/etc/torrc.d/40_anon_connection_wizard.conf
 %include /usr/local/etc/torrc.d/50_user.conf
 user@host:~$ cat /usr/local/etc/torrc.d/40_anon_connection_wizard.conf
 # This file is generated by and should ONLY be used by anon-connection-
 wizard.
 # User configuration should go to /usr/local/etc/torrc.d/50_user.conf, not
 here. Because:
 #1. This file can be easily overwritten by anon-connection-wizard.
 #2. Even a single character change in this file may cause error.
 # However, deleting this file will be fine since a new plain file will be
 generated the next time you run anon-connection-wizard.
 DisableNetwork 0
 user@host:~$ cat /usr/local/etc/torrc.d/50_user.conf
 Sandbox 1
 }}}

 {{{
 Mar 30 06:14:28 host Tor[5429]: Opening DNS listener on 10.137.11.1:5300
 Mar 30 06:14:28 host Tor[5429]: Opening DNS listener on 127.0.0.1:5400
 Mar 30 06:14:28 host Tor[5429]: Opening Transparent pf/netfilter listener
 on 10.137.11.1:9040
 Mar 30 06:14:28 host Tor[5429]: Opening Transparent pf/netfilter listener
 on 127.0.0.1:9041
 Mar 30 06:14:28 host Tor[5429]: Parsing GEOIP IPv4 file
 /usr/share/tor/geoip.
 Mar 30 06:14:28 host Tor[5429]: Parsing GEOIP IPv6 file
 /usr/share/tor/geoip6.
 Mar 30 06:14:28 host Tor[5429]: Bootstrapped 0%: Starting
 Mar 30 06:14:28 host Tor[5429]: Starting with guard context "default"
 Mar 30 06:14:28 host Tor[5429]: Bootstrapped 80%: Connecting to the Tor
 network
 Mar 30 06:14:28 host Tor[5429]: Signaled readiness to systemd
 Mar 30 06:14:28 host Tor[5429]: Received reload signal (hup). Reloading
 config and resetting internal state.
 Mar 30 06:14:28 host Tor[5429]: Read configuration file "/usr/share/tor
 /tor-service-defaults-torrc".
 Mar 30 06:14:28 host Tor[5429]: Read configuration file "/etc/tor/torrc".
 Mar 30 06:14:29 host Tor[5429]: sandbox_intern_string(): Bug: No interned
 sandbox parameter found for /etc/torrc.d/95_whonix.conf (on Tor 0.3.2.10 )
 Mar 30 06:14:29 host systemd[1]: Started Anonymizing overlay network for
 TCP.
 Mar 30 06:14:29 host Tor[5429]: sandbox_intern_string(): Bug: No interned
 sandbox parameter found for /etc/torrc.d/95_whonix.conf (on Tor 0.3.2.10 )
 Mar 30 06:14:29 host Tor[5429]: Could not open
 "/etc/torrc.d/95_whonix.conf": Permission denied
 Mar 30 06:14:29 host Tor[5429]: Error reading included configuration file
 or directory: "/etc/torrc.d/95_whonix.conf".
 Mar 30 06:14:29 host Tor[5429]: Reading config failed--see warnings above.
 For usage, try -h.
 Mar 30 06:14:29 host Tor[5429]: Restart failed (config error?). Exiting.
 Mar 30 06:14:29 host systemd[1]: tor@default.service: Main process exited,
 code=exited, status=1/FAILURE
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs