[tor-bugs] #20056 [Archived/Development Progress]: Organize Shelves For House Storage Prior To You Move In

[Tor Bug Tracker & Wiki]

#20056: Organize Shelves For House Storage Prior To You Move In
-+-
 Reporter:  SherrillPremo|  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Very Low |  Milestone:  Tor: 0.2.8.x-final
Component:   |Version:  Tor: 0.2.8.5-rc
  Archived/Development Progress  |   Keywords:  nichrome wire nichrome
 Severity:  Critical |  wire suppliers insulated nichrome
 |  wire
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 I have to say, following performing tons of research on electronic
 cigarettes, V2 Cigs received the best overall comments throughout the
 board for all Digital Cigarette companies. Everybody seemed to be pleased
 with the item, with the speediness of the shipping, and when they did have
 concerns or issues, customer service was fast to assist.

 The white wire is also referred as the floor and it is also called as the
 neutral wire. The black wire or [https://Atomizerwick.com/products
 /nichrome-resistance-wire Insulated Nichrome Wire] is intended for
 providing electricity. But be careful before getting rid of any wire and
 you require to consider a not on the old outlet so that it can be changed
 with the new one.

 [https://atomizerwick.com/products/nichrome-resistance-wire
 atomizerwick.com]

 It all arrives down to balancing. Most tyre companies aren't extremely
 good at balancing wire wheels as they don't always have the right cones to
 make sure they fit on the balancing devices correctly. If any of the
 spokes are broken or loose, then this makes them even tougher to
 stability. But the new alloy Minilites well balanced perfectly - hence the
 transformation. And no hazard of spokes coming free or getting broken or
 bent.

 This is exactly where the Fifty One charger arrives in. The charger
 arrives for both Duo and Trio cigarettes. As the Fifty 1 cigar is
 disposable, so they do not need the Fifty 1 charger. The Fifty 1 charger
 is available for both car and home functions. In this variety, you also
 get USB adapters to recharge your nichrome resistance wire for e-cigarette
 battery from other ports as well.

 Long tale short; after battling that darkish, black rain cloud that
 hovered over my head and controlled each element of my life nichrome
 resistance wire for e-cigarette years, I can say that I'm smoke free and a
 a lot much better guy because of it.

 A third line is supplied called the "neutral" line and is usually colored
 white in the box. When 1 or two of the "hot" legs of energy are mixed with
 the neutral line.something in between creating get in touch with with
 these wires is "energized or powered".

 With digital cigarette starter package, you also get to choose flavors.
 Though you get flavors with some normal cigs, they nonetheless create the
 awful smell in your mouth, hands and even garments. With Fifty One digital
 cigarette kits, you get flavors like clove, menthol, vanilla, pina colada,
 Camel, Marlboro, coffee and even cherry. In case you still favor to inhale
 the smell of tobacco, there is the tobacco totally free taste with the
 title "original". It preferences like what your ordinary cigs would have
 tasted, but is nonetheless completely free of the harms. The flavors make
 sure that what the individuals scent is the faint smell of the taste, and
 not anything pungent.

 [https://Atomizerwick.com/products/nichrome-resistance-wire Insulated
 Nichrome Wire]

--
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] #7164 [Core Tor/Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1

[Tor Bug Tracker & Wiki]

#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still 
referenced
1 node(s); held_by_nodes == 1
-+-
 Reporter:  jaj123   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.19
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, 025-backport, nickm- |  Actual Points:
  should-review, review-group-7  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => needs_revision


Comment:

 Replying to [comment:84 cypherpunks]:
 > Another problem, there are dozens relays (last time checked it was
 around 40 relays) that never rotate onion keys for some reason.

 Split off #20055 for this issue.

 The rest of this ticket seems to need a revision, based on the cypherpunks
 comments.
 (Next time, please PGP encrypt an email for vulnerabilities, or make
 plain-text comments otherwise. It helps us fix all the issues at the same
 time.)

--
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] #20055 [Core Tor/Tor]: Remove relays that fail to rotate onion keys from the consensus

[Tor Bug Tracker & Wiki]

#20055: Remove relays that fail to rotate onion keys from the consensus
--+---
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  torspec, 030-proposed
Actual Points:|  Parent ID:
   Points:  2 |   Reviewer:
  Sponsor:|
--+---
 On #7164, a cypherpunks notes that ~40 relays fail to rotate their onion
 keys. This should be addressed by identifying these relays, and adding
 them to the DirAuths' AuthDirInvalid or AuthDirReject lists.

 First, we need to update torspec/dir-spec.txt to say that relays SHOULD
 rotate their onion keys every 7 days, and MUST rotate them every N days.
 (I suggest 14 or 28.)

 Then we can modify DocTor to check for relays in the consensus that have
 had the same onion key for N days. (I think DocTor is the right place for
 this check.)

 This won't catch cases where relays repeat onion keys, but it will suffice
 to catch the most obvious misconfiguration - a read-only onion key file.

--
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] #14881 [Core Tor/Tor]: incorrect defaults when producing bandwidth-weights line in directory footer

[Tor Bug Tracker & Wiki]

#14881: incorrect defaults when producing bandwidth-weights line in directory
footer
-+-
 Reporter:  robgjansen   |  Owner:
 |  robgjansen
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7
 Severity:  Normal   | Resolution:
 Keywords:  027-triaged-1-in, 028-triaged,   |  Actual Points:
  pre028-patch, tor-sponsorU-orphan, |
  TorCoreTeam-postponed-201604   |
Parent ID:   | Points:  3
 Reviewer:  mikeperry|Sponsor:
 |  SponsorU-can
-+-

Comment (by teor):

 [comment:25 My previous comment] still applies, if we merge this latest
 patch, it will break the chutney "mixed" version target. Even if it only
 breaks test networks, it's still breakage. To merge it into Tor, we need a
 new consensus method.

 We might also want to resolve [comment:22 mikeperry's concerns] before we
 merge:
 "for full correctness I think we need to initialize T to 4 here, if we
 initialize all other weights to 1".

--
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] #19459 [Applications/Tor Browser]: Write (C++) patch for window resizing parts

[Tor Bug Tracker & Wiki]

#19459: Write (C++) patch for window resizing parts
-+-
 Reporter:  gk   |  Owner:
 |  arthuredelstein
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-torbutton-conversion,|  Actual Points:
  TorBrowserTeam201609R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  SponsorU
-+-
Changes (by arthuredelstein):

 * keywords:  tbb-torbutton-conversion, TorBrowserTeam201608 => tbb-
 torbutton-conversion, TorBrowserTeam201609R
 * status:  needs_revision => needs_review


Comment:

 Here's my new version:
 https://github.com/arthuredelstein/tor-browser/commit/19459+5
 I no longer need to use a MutationObserver or anything too nasty.
 Basically I found that if we set the tabBrowser's flex attribute to 0,
 then the XULWindow adjusts its size to conform with whatever tabBrowser
 width and height we specify. Then we can set flex back to 1 when the
 window is first painted.

 And here's the new window sizing code removed from torbutton:
 https://github.com/arthuredelstein/torbutton/commit/19459

--
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] #20054 [Internal Services/Tor Sysadmin Team]: Electric Float Switch Related Concerns

[Tor Bug Tracker & Wiki]

#20054: Electric Float Switch Related Concerns
-+-
 Reporter:  SherrillPremo|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Low  |  Milestone:  CollecTor 1.1.0
Component:  Internal |Version:  Tor: 0.2.6.2-alpha
  Services/Tor Sysadmin Team |   Keywords:  nichrome wire vape
 Severity:  Trivial  |  insulated nichrome wire nichrome
 |  ribbon
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 You've most likely listened to of the latest item known
 [https://atomizerwick.com/products/nichrome-resistance-wire nichrome Wire
 suppliers] as e-cig, however you might not know what it is all about.
 There are a number of advantages of this item over standard smoking
 cigarettes. Here's what is getting individuals to transfer to this new
 invention.

 [https://atomizerwick.com/products/nichrome-resistance-wire
 atomizerwick.com]

 The nichrome resistance wire for e-cigarette is the only way out. It has
 now been launched to control smoking behavior. After years of study and
 experimentation, the e-cig has entered the marketplace. This is great
 information for all smokers. The e-cigarettes have no tar and are nearly
 100%twenty five totally free of chemicals. If you are looking to stylize
 your package or look chic, then you need to go in for the subsequent best
 factor that is nichrome resistance wire for e-cigarettes.

 Aside from the lack of smoke, that's the greatest distinction in between a
 conventional cigarette and its electric counterpart. The electronic
 version doesn't contain any tobacco to burn. In fact, an ecig doesn't burn
 something nichrome resistance wire for e-cigarette .

 The toxic chemical substances is not threatening for you only, but it can
 be unsafe for these about you also. Secondhand smoke isn't a be concerned
 with this gadget. As you allow out your breath, really the only thing that
 you blow absent at most is water vapor and a small amount of nicotine.
 It's because the liquid in the device only has flavoring, nicotine and
 water. There's actually absolutely nothing in the gadget to harm any
 person near you. You could begin cigarette smoking this about a kid and
 they won't be impacted.

 We merely don't say it's a handy option. Just study on and you'll know
 why. This Danby wine cooler arrives with three
 [https://atomizerwick.com/products/nichrome-resistance-wire Insulated
 Nichrome Wire] cabinets. So you can neatly display bottles in such a way
 that your visitor can have a glimpse at the bottles and select the 1 they
 want.

 How much will this help save? Nicely, the quantity of cash you can save
 with the e-cig can vary, however results are usually some financial
 savings. If you purchase 1 which you throw away every couple of days say
 in 3-5 times. These product generally cost you about $10 each. You'll save
 around $20 a week with this particular kind.

 I am not afraid of electricity, I give it the healthy regard I would any
 other type of power source whether or not it is all-natural gasoline,
 fire, a hot stove, or even a spinning fan. Any one of these sources of
 power or programs of power can hurt you if you are not careful and it
 usually helps to be relatively knowledgeable to make sure that you are
 cautious.

 Don't only think of your kids when you safety evidence your house. Keep in
 mind that your personal safety is just as essential. Do yourself a favor
 and make your rest room security proof for grownups to stop any future
 injuries on your component.

--
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] #16645 [Core Tor/Tor]: Write guide about using offline ed25519 keys on relays

[Tor Bug Tracker & Wiki]

#16645: Write guide about using offline ed25519 keys on relays
+--
 Reporter:  asn |  Owner:  s7r
 Type:  task| Status:  closed
 Priority:  Very High   |  Milestone:  Tor:
|  0.2.8.x-final
Component:  Core Tor/Tor|Version:  Tor: 0.2.7
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tor-relay, doc, review-group-7  |  Actual Points:
Parent ID:  | Points:  3
 Reviewer:  |Sponsor:  SponsorU-can
+--
Changes (by s7r):

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


Comment:

 @dgoulet yes, it's resolved. Had to remove #16680 as child ticket so we
 can close this. They are not so related and #16680 can wait a little more.

--
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] #16680 [Core Tor/Tor]: make Ed25519 master key, signing key and cert ascii-armored on disk by default

[Tor Bug Tracker & Wiki]

#16680: make Ed25519 master key, signing key and cert ascii-armored on disk by
default
--+
 Reporter:  s7r   |  Owner:  nickm
 Type:  defect| Status:  assigned
 Priority:  Low   |  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.2.7.2-alpha
 Severity:  Normal| Resolution:
 Keywords:  ed25519, keys, ascii-armored  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by s7r):

 * parent:  #16645 =>


--
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] #20049 [Metrics/Metrics website]: Adapt legacy module to accept bridge network statuses from two authorities

[Tor Bug Tracker & Wiki]

#20049: Adapt legacy module to accept bridge network statuses from two 
authorities
-+-
 Reporter:  karsten  |  Owner:
 Type:  defect   | Status:  merge_ready
 Priority:  Very High|  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by iwakeh):

 I opened #20059 as a planning ticket. This can be closed when all is
 merged.

--
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] #20053 [Metrics/Metrics website]: Plan refactoring of metrics-web modules

[Tor Bug Tracker & Wiki]

#20053: Plan refactoring of metrics-web modules
-+---
 Reporter:  iwakeh   |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Metrics 1.0.0
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+---
 many modules are very old and should be modernized and refactured

 this is a bigger task ticket is for planning the first steps.


 depends on #19730
 see also #20049

--
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] #18935 [Applications/Tor Browser]: MS bugs - Danger! Windows updates break everything on their way!

[Tor Bug Tracker & Wiki]

#18935: MS bugs - Danger! Windows updates break everything on their way!
--+---
 Reporter:  bugzilla  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  duplicate
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by bugzilla):

 So, as MS stated, [https://support.microsoft.com/en-us/kb/3172605 July
 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1] is
 enough to fix issues with EAF, but
 {{{
 Faulting application name: firefox.exe, version: 45.3.0.0, time stamp:
 0x
 Faulting module name: KERNELBASE.dll, version: 6.1.7601.23392, time stamp:
 0x56eb2fb9
 Exception code: 0x8004
 Fault offset: 0x6840
 }}}
 TBB 6.5a2 rare startup crash (EMET 5.5 max).

--
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] #18935 [Applications/Tor Browser]: MS bugs - Danger! Windows updates break everything on their way!

[Tor Bug Tracker & Wiki]

#18935: MS bugs - Danger! Windows updates break everything on their way!
--+---
 Reporter:  bugzilla  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  duplicate
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by bugzilla):

 Well, MS started to fix its bugs in a specific way. It's called Monthly
 update rollup.
 > This update includes quality improvements. No new operating system
 features are being introduced and no new security updates are included.
 It is optional! But
 > We recommend that you apply this update rollup as part of your regular
 maintenance routines.
 It was treated as a joke at first, but it still continues...

 So, the needed updates are:
 [https://support.microsoft.com/kb/3161647 KB3161647 Windows Update Client
 for Windows 7 and Windows Server 2008 R2: June 2016]
 [https://support.microsoft.com/kb/3163644 KB3163644 Microsoft Office 2010
 doesn't start when EMET is enabled in Windows 7 or Windows Server 2008 R2]
 > This issue occurs when the Enhanced Mitigation Experience Toolkit (EMET)
 is enabled and security update 3146706 or convenience rollup update
 3125574 is installed.
 Have you guessed that it's about Windoze (not EMET) bug with EAF? :)
 Don't try to download them because, yes, they are in the first Monthly
 update rollup:
 [https://support.microsoft.com/en-us/kb/3161608 June 2016 update rollup
 for Windows 7 SP1 and Windows Server 2008 R2 SP1]
 But don't try to find it in your Optional updates because update rollups
 are cumulative, and this one was superseded by:
 [https://support.microsoft.com/en-us/kb/3172605 July 2016 update rollup
 for Windows 7 SP1 and Windows Server 2008 R2 SP1]
 But to find out info about it you need https://support.microsoft.com/en-
 us/help/22801/windows-7-and-windows-server-2008-r2-update-history
 And, surprise, update rollups are no longer cumulative, so don't use
 [https://support.microsoft.com/ru-ru/kb/3179573 August 2016 update rollup
 for Windows 7 SP1 and Windows Server 2008 R2 SP1]
 > This update doesn't replace any previously released update.
 Funny? No? Don't worry, welcome Monthly Rollups!
 https://arstechnica.com/business/2016/08/windows-7-8-1-moving-to-windows-
 10s-cumulative-update-model/?comments=1=200
 > October 2016's Patch Tuesday will see the release of the first Monthly
 Rollup for Windows 7 and 8.1.
 and, yes,
 > Subsequent months will have new Monthly Rollups, and these will be
 cumulative, incorporating the content of all previous Monthly Rollups.
 but
 > Initially, these Monthly Rollups will only contain new patches released
 from October 2016 onward.
 but
 > Over the next year, Microsoft says that it will extend them to go back
 in time, slowly integrated all the patches released since the last
 "baseline."
 So MS will get you sooner or later ;)

--
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] #20049 [Metrics/Metrics website]: Adapt legacy module to accept bridge network statuses from two authorities

[Tor Bug Tracker & Wiki]

#20049: Adapt legacy module to accept bridge network statuses from two 
authorities
-+-
 Reporter:  karsten  |  Owner:
 Type:  defect   | Status:  merge_ready
 Priority:  Very High|  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by karsten):

 Thanks for the quick review!  I made the changes you suggested and pushed
 to master.  And I totally agree that this module should be refactored
 soon.  I started doing that a while ago, but as most things, it quickly
 turned into a mid-size project that I wasn't able to complete yet.  I
 suggest we close this ticket and create a new one for rewriting this
 module as soon as we get to that.  Okay?

--
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] #19690 [Core Tor/DirAuth]: Tonga (Bridge Authority) Permanent Shutdown Notice

[Tor Bug Tracker & Wiki]

#19690: Tonga (Bridge Authority) Permanent Shutdown Notice
---+
 Reporter:  shamrock   |  Owner:  isis
 Type:  task   | Status:  assigned
 Priority:  Very High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/DirAuth   |Version:  Tor: 0.2.8.5-rc
 Severity:  Critical   | Resolution:
 Keywords:  TorCoreTeam201608  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by bugzilla):

 Replying to [comment:14 karsten]:
 Hmm, mandatory auto-update mechanism (take or die) from Tor consensus is
 required.
 > 421 Tor 0.2.7.6 on Linux
 Maybe, Tor should warn/info when the repository is different from the
 recommended.
 > 124 Tor 0.2.8.6 on Linux
 Suspiciously. But people that check manually for a new version can be
 aware since Aug 24 only...
 > 44 Tor 0.2.8.2-alpha on Linux
 What's the reason to allow alphas to be bridges? Separate "alpha bridges"
 category for clients who like experiments is preferable.
 > 94 Tor 0.2.4.23 on Windows 7
 There are no reasons not to update on Windows except that Expert Bundle
 lacks auto-updater. But it has 0.2.8.6 version now, so your data shows
 that all Windows bridges, except those 0.2.4.x highly outdated, are
 maintained by up-to-date rebuilding from source. Is it plausible?

--
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] #14881 [Core Tor/Tor]: incorrect defaults when producing bandwidth-weights line in directory footer

[Tor Bug Tracker & Wiki]

#14881: incorrect defaults when producing bandwidth-weights line in directory
footer
-+-
 Reporter:  robgjansen   |  Owner:
 |  robgjansen
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7
 Severity:  Normal   | Resolution:
 Keywords:  027-triaged-1-in, 028-triaged,   |  Actual Points:
  pre028-patch, tor-sponsorU-orphan, |
  TorCoreTeam-postponed-201604   |
Parent ID:   | Points:  3
 Reviewer:  mikeperry|Sponsor:
 |  SponsorU-can
-+-

Comment (by pastly):

 Replying to [comment:27 mikeperry]:
 > Rob, do you think you can merge my mock-up patch with the consensus
 method check and create a new proper patch? I am juggling a few too many
 things this week.

 I've run into this issue working on KIST stuff like Rob probably did a
 while ago.

 I'm uploading a merge of your mock-up patch and Rob's "testing network
 only" patch. This doesn't add a new consensus version, it should just sets
 the weights to 1 if testing.

 I'll be testing this patch shortly

--
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] #7164 [Core Tor/Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1

[Tor Bug Tracker & Wiki]

#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still 
referenced
1 node(s); held_by_nodes == 1
-+-
 Reporter:  jaj123   |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.19
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, 025-backport, nickm- |  Actual Points:
  should-review, review-group-7  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 Another problem, there are dozens relays (last time checked it was around
 40 relays) that never rotate onion keys for some reason.

--
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] #20049 [Metrics/Metrics website]: Adapt legacy module to accept bridge network statuses from two authorities

[Tor Bug Tracker & Wiki]

#20049: Adapt legacy module to accept bridge network statuses from two 
authorities
-+-
 Reporter:  karsten  |  Owner:
 Type:  defect   | Status:  merge_ready
 Priority:  Very High|  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 Some findings below; this is difficult to review b/c of the ancient code
 base.
 I assume it does what is intended.

 * build.xml still references descriptor-1.2.0

 * It could be useful to consider enums for authority listings and EnumMap,
 as these might be faster than hash-maps, but ok for the moment.

 * In the existing code `bw.append(line + "\n");` should be replaced by the
 two statements  `bw.append(line); bw.newLine();`.

 * I would place a comment differently and leave out the empty else.  Minor
 change suggestion w/o enum change:
 {{{
 diff --git
 
a/modules/legacy/src/org/torproject/ernie/cron/network/ConsensusStatsFileHandler.java
 
b/modules/legacy/src/org/torproject/ernie/cron/network/ConsensusStatsFileHandler.java
 index 631839d..8d51d5d 100644
 ---
 
a/modules/legacy/src/org/torproject/ernie/cron/network/ConsensusStatsFileHandler.java
 +++
 
b/modules/legacy/src/org/torproject/ernie/cron/network/ConsensusStatsFileHandler.java
 @@ -139,6 +139,8 @@ public class ConsensusStatsFileHandler {
  + "! Aborting to read this file!");
  break;
}
 +  /* Assume that all lines without authority nickname are based
 on
 +   * Tonga's network status, not Bifroest's. */
String key = parts[0] + "," + (parts.length < 4 ? "Tonga" :
 parts[1]);
String value = null;
if (parts.length == 2) {
 @@ -147,11 +149,8 @@ public class ConsensusStatsFileHandler {
  value = key + "," + parts[1] + "," + parts[2];
} else if (parts.length == 4) {
  value = key + "," + parts[2] + "," + parts[3];
 -  } else {
 -/* Impossible, we already checked the range above. */
 -  }
 -  /* Assume that all lines without authority nickname are based
 on
 -   * Tonga's network status, not Bifroest's. */
 +  } /* No more cases as we already checked the range above. */
 +
this.bridgesRaw.put(key, value);
  }
  br.close();
 @@ -308,7 +307,8 @@ public class ConsensusStatsFileHandler {
new FileWriter(this.bridgeConsensusStatsRawFile));
bw.append("datetime,authority,brunning,brunningec2\n");
for (String line : this.bridgesRaw.values()) {
 -bw.append(line + "\n");
 +bw.append(line);
 +bw.newLine();
}
bw.close();
this.logger.fine("Finished writing file "
 @@ -404,7 +404,7 @@ public class ConsensusStatsFileHandler {
+ "old: " + this.bridgesRaw.lastKey());
  }
} catch (ParseException e) {
 - /* Can't parse the timestamp? Whatever. */
 +logger.warning("Can't parse the timestamp? Reason: " + e);
}
  }
  logger.info(dumpStats.toString());
 }}}


 --
 This module should be refactored very soon! But, that's a different
 ticket.

 Should there also be a follow-up ticket for accommodating future authority
 changes/additions more elegantly?

 Ready for merge as hot-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

Re: [tor-bugs] #7164 [Core Tor/Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1

[Tor Bug Tracker & Wiki]

#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still 
referenced
1 node(s); held_by_nodes == 1
-+-
 Reporter:  jaj123   |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.19
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, 025-backport, nickm- |  Actual Points:
  should-review, review-group-7  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 > Okay. A consensus arrives

 Your case happens if consensus were set by
 networkstatus_note_certs_arrived(), it miss all update_*() functions.

 Alas, it's not last edge case that trigger thus warnings.
 nodelist_set_consensus() must to clear all node->md like it does for
 node->rs to fix all remain cases.

--
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] #7164 [Core Tor/Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1

[Tor Bug Tracker & Wiki]

#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still 
referenced
1 node(s); held_by_nodes == 1
-+-
 Reporter:  jaj123   |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.19
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, 025-backport, nickm- |  Actual Points:
  should-review, review-group-7  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 Replying to [comment:74 cypherpunks]:
 > U2FsdGVkX19xU5DZ+k76OvKVNZbPzyTLeVU3rQslY+Bz8xq+mXT59freOTt4KDRQ
 > ScTaE9PCTdMED5CkBlXJuTJfOCJNEO69AskcLeDTRRFT1w9W3QWgxZshpgc8T5qD
 > GwweQ02CWm/bdq0NW070xUHuno10nLbIBAO8a/bzcfSbyquibM+FIZlQTA0n0Fda
 > Qey6pv3d9y7v/Lc8OHfZUD1Vvbe9v9P5xqrpwcwkdT0klI5B5Vgaike7m25P1hDh
 > MBzO6gX3NNnA1ST5pP0qpuFgZMK79uJmbXUj0iECLs6sGD/HgY19p9Vw/T6Pt7P4
 > 8+mh5lUOzcLAX2Lc1yKZEBYIJmSnYwgWYensAepobKH785iuij/a6X4YLdJ39BCz
 > nvkKCfm4cLCLGEG+4MkrRClBN7YtpZ57K9LSyWnxTHKJinFYLpGMc9VYViScYq3E
 > Qm9xVYisuET5bD7tBjgbXCJdF67++7w=
 >
 > (openssl enc -aes-256-xts -d -base64
 > sha256(password) =
 62493873306edef2c14c567d252b5b029d67fe3119c703486209a93bb9e4117e)
 >
 > EDIT: function name copy/paste typo

 Found password
 > echo "the report of my death was an exaggeration" | openssl sha256

 Deciphered
 > get_microdesc_cache() is being called for the first time by
 nodelist_set_consensus(). md->held_by_nodes incremented by
 nodelist_set_consensus() too (nodelist_add_microdesc skip that part as no
 any nodes created yet). microdesc_cache_clean() is being called for the
 first time without held_by_nodes for any md. if no held_by_nodes then no
 bug.

--
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] #14271 [Applications/Tor Browser]: Make Torbutton work with Unix Domain Socket option

[Tor Bug Tracker & Wiki]

#14271: Make Torbutton work with Unix Domain Socket option
-+-
 Reporter:  gk   |  Owner:  brade
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-torbutton, tbb-security, |  Actual Points:
  TorBrowserTeam201609   |
Parent ID:  #14270   | Points:
 Reviewer:   |Sponsor:
 |  SponsorU
-+-
Changes (by mcs):

 * status:  needs_revision => needs_information


Comment:

 Replying to [comment:12 gk]:
 > Here are some comments:
 >
 > 1)
 > {{{
 > +// given sockFile or host and port.
 > }}}
 > s/sockFile/socketFile/

 Good catch.


 > 2)
 > {{{
 > let tlps = Cc["@torproject.org/torlauncher-protocol-service;1"]
 >  .getService(Ci.nsISupports).wrappedJSObject;
 > }}}
 > We should do that once and not twice in `torbutton_init()`.

 Agreed.


 > 3) Checking whether we should call `torbutton_local_tor_check()` should
 check for
 > `m_tb_control_socket_file` as well (not only for `m_tb_control_port`) I
 guess?

 We did add that check, although if you look at the patch with git's
 default of three lines of context it is not so obvious.


 > 4) I am not so sure about
 > {{{
 > +} catch(e) {
 > +  m_tb_control_port = 9151;
 > +}
 > }}}
 > What was your rationale for adding that now (given you omitted it
 earlier)? For one, the logs might be misleading showing a probably wrong
 port (I mean the setup is seriously troubling if we need to assign `9151`
 in the catch clause at all) in an error with respect to the control
 connection. On the other hand, we might want to show that something is
 wrong with the help of `torbutton_do_tor_check()` which would update the
 toolbar button in this case (if we get that far at all with a broken setup
 like the one in question).

 Kathy and I added the 9151 default to be consistent with how
 m_tb_control_host is handled (it was already defaulting to 127.0.0.1).
 Thinking about this some more and looking at the existing Torbutton code,
 it seems like there is some effort to disable features (e.g., New
 Identity, the local Tor check) when the port is missing. So maybe we
 should put things back how there were and make sure we consistently check
 for port, password, etc. before trying to do things in Torbutton that
 require authenticated control port access?

 The circuit display code also includes code that defaults the port to
 9151, so if we decide to continue with the concept that a lack of port can
 be used to disable code, we should remove the `|| 9151` from this line in
 tor-circuit-display.js:
 `myController = controller(socketFile, host, port || 9151, password,`
 We can also add a check to skip the call to createTorCircuitDisplay() if
 port, password, etc. are missing (the existing code will log an error if
 initialization fails).

 What do you think?

--
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] #20040 [Applications/Tor Browser]: fix MAR file generation to account for packed HTTPS Everywhere

[Tor Bug Tracker & Wiki]

#20040: fix MAR file generation to account for packed HTTPS Everywhere
--+
 Reporter:  mcs   |  Owner:  mcs
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201608R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by gk):

 Okay, this is commit f800760546f5912d5aef5ca4e56b9e3fd62df8f9 on tor-
 browser-45.3.0esr-6.0-1.

--
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] #19690 [Core Tor/DirAuth]: Tonga (Bridge Authority) Permanent Shutdown Notice

[Tor Bug Tracker & Wiki]

#19690: Tonga (Bridge Authority) Permanent Shutdown Notice
---+
 Reporter:  shamrock   |  Owner:  isis
 Type:  task   | Status:  assigned
 Priority:  Very High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/DirAuth   |Version:  Tor: 0.2.8.5-rc
 Severity:  Critical   | Resolution:
 Keywords:  TorCoreTeam201608  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by karsten):

 Replying to [comment:13 bugzilla]:
 > Replying to [comment:12 karsten]:
 > > [https://people.torproject.org/~karsten/volatile/running-
 bridges-2016-09-01.png New graph] shows that transition has stopped.
 Guess we'll lose 1.3k bridges in two days from now.
 > Windoze bridges?

 Not Windows bridges, but Linux bridges for the most part:

 {{{
  421 Tor 0.2.7.6 on Linux
  151 Tor 0.2.5.12 on Linux
  124 Tor 0.2.8.6 on Linux
  106 Tor 0.2.4.23 on Windows 8
   94 Tor 0.2.4.23 on Windows 7
   79 Tor 0.2.4.27 on Linux
   59 Tor 0.2.6.10 on Linux
   44 Tor 0.2.8.2-alpha on Linux
   40 Tor 0.2.5.10 on Linux
   22 Tor 0.2.4.22 on Windows 7
 }}}

--
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] #15059 [Core Tor/Tor]: Allow UI to identify servers by Ed25519 keys

[Tor Bug Tracker & Wiki]

#15059: Allow UI to identify servers by Ed25519 keys
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Low  |  Milestone:  Tor:
 |  0.3.0.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, prop220, |  Actual Points:
  027-triaged-1-in, 028-triaged, tor-|
  ed25519-proto  |
Parent ID:  #15054   | Points:  3
 Reviewer:   |Sponsor:
 |  SponsorU-can
-+-
Changes (by nickm):

 * severity:   => Normal
 * milestone:  Tor: 0.2.9.x-final => Tor: 0.3.0.x-final


--
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] #16645 [Core Tor/Tor]: Write guide about using offline ed25519 keys on relays

[Tor Bug Tracker & Wiki]

#16645: Write guide about using offline ed25519 keys on relays
+--
 Reporter:  asn |  Owner:  s7r
 Type:  task| Status:
|  needs_revision
 Priority:  Very High   |  Milestone:  Tor:
|  0.2.8.x-final
Component:  Core Tor/Tor|Version:  Tor: 0.2.7
 Severity:  Normal  | Resolution:
 Keywords:  tor-relay, doc, review-group-7  |  Actual Points:
Parent ID:  | Points:  3
 Reviewer:  |Sponsor:  SponsorU-can
+--

Comment (by dgoulet):

 This tickets seems resolved to me. @s7r, are you satisfied with it. Do we
 consider this done?

--
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] #19767 [Core Tor/Tor]: Solaris, compile warning: "_FILE_OFFSET_BITS" redefined and core dump

[Tor Bug Tracker & Wiki]

#19767: Solaris, compile warning: "_FILE_OFFSET_BITS" redefined and core dump
-+-
 Reporter:  RainerSchmidt|  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.5-rc
 Severity:  Major| Resolution:
 Keywords:  Solaris, regression, crash, review-  |  Actual Points:  .3
  group-7|
Parent ID:   | Points:  0.2
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => merge_ready


Comment:

 The fix does look OK to me but it's just impossible for me to confirm.

 As for the trunnel commit, +9k! I actually need that one :).

--
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] #7164 [Core Tor/Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1

[Tor Bug Tracker & Wiki]

#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still 
referenced
1 node(s); held_by_nodes == 1
-+-
 Reporter:  jaj123   |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.19
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, 025-backport, nickm- |  Actual Points:
  should-review, review-group-7  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => merge_ready


Comment:

 lgtm;

 Note that I can't really test this, I do not have a old data set of tor :S
 and using CollecTor files makes it a bit complicated since the archive of
 microdescriptors are ordered by ID and not in one single fat file.

--
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] #19743 [Core Tor/Tor]: VirtualAddrNetworkIPv6 manpage entry correction

[Tor Bug Tracker & Wiki]

#19743: VirtualAddrNetworkIPv6 manpage entry correction
-+
 Reporter:  cypherpunks  |  Owner:
 Type:  defect   | Status:  closed
 Priority:  Low  |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Trivial  | Resolution:  fixed
 Keywords:  isaremoved nickwants029  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by nickm):

 * milestone:  Tor: 0.2.8.x-final => Tor: 0.2.9.x-final


--
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] #20040 [Applications/Tor Browser]: fix MAR file generation to account for packed HTTPS Everywhere

[Tor Bug Tracker & Wiki]

#20040: fix MAR file generation to account for packed HTTPS Everywhere
--+
 Reporter:  mcs   |  Owner:  mcs
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201608R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by mcs):

 Replying to [comment:3 gk]:
 > Looks good to me. This is commit
 082d1c5e03617458f366b597256597bbde079889 on tor-browser-45.3.0esr-6.5-1.

 Thanks.

 > I guess we want to have that for the stable as well? Did you test that
 and verified that the fix worked properly in that particular case?

 I think we want this on stable. Kathy and I tested by running through all
 of the scenarios and verifying that the MAR table of contents plus
 manifest looked correct.

--
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] #19450 [Core Tor/Tor]: Rip out --enable-bufferevents

[Tor Bug Tracker & Wiki]

#19450: Rip out --enable-bufferevents
--+
 Reporter:  arma  |  Owner:  U+039b
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:  Tor:
  |  0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  review-group-7 TorCoreTeam201608  |  Actual Points:
Parent ID:| Points:
 Reviewer:  U+039b|Sponsor:
--+
Changes (by nickm):

 * keywords:  review-group-7 => review-group-7 TorCoreTeam201608


--
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] #19743 [Core Tor/Tor]: VirtualAddrNetworkIPv6 manpage entry correction

[Tor Bug Tracker & Wiki]

#19743: VirtualAddrNetworkIPv6 manpage entry correction
-+
 Reporter:  cypherpunks  |  Owner:
 Type:  defect   | Status:  closed
 Priority:  Low  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Trivial  | Resolution:  fixed
 Keywords:  isaremoved nickwants029  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by nickm):

 * milestone:  Tor: 0.2.9.x-final => Tor: 0.2.8.x-final


--
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] #19947 [Core Tor/Tor]: NULL %s in fmt string (dir_server_new() - routerlist.c)

[Tor Bug Tracker & Wiki]

#19947: NULL %s in fmt string (dir_server_new() - routerlist.c)
-+-
 Reporter:  rubiate  |  Owner:
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  regression?, 028-backport|  Actual Points:
  TorCoreTeam201608  |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  regression?, 028-backport => regression?, 028-backport
 TorCoreTeam201608


--
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] #19904 [Core Tor/Tor]: evutil_secure_rng_add_bytes() not present in openbsd libevent 2

[Tor Bug Tracker & Wiki]

#19904: evutil_secure_rng_add_bytes() not present in openbsd libevent 2
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  openbsd, TorCoreTeam201608  |  Actual Points:  0
Parent ID:  | Points:  0
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * keywords:  openbsd, TorCoreTeam201609 => openbsd, TorCoreTeam201608


--
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] #8625 [Core Tor/Tor]: Do not call networkstatus_reset_download_failures() hourly

[Tor Bug Tracker & Wiki]

#8625: Do not call networkstatus_reset_download_failures() hourly
-+-
 Reporter:  nickm|  Owner:  andrea
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, tor-dos, |  implemented
  TorCoreTeam201608, review-group-6  |  Actual Points:  3
Parent ID:   | Points:  3
 Reviewer:  nickm|Sponsor:
 |  SponsorU-can
-+-
Changes (by nickm):

 * keywords:  tor-client, tor-dos, TorCoreTeam201607, review-group-6 => tor-
 client, tor-dos, TorCoreTeam201608, review-group-6


--
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] #19973 [Core Tor/Tor]: ReachableAddresses applied too broadly

[Tor Bug Tracker & Wiki]

#19973: ReachableAddresses applied too broadly
---+---
 Reporter:  nickm  |  Owner:
 Type:  defect | Status:  closed
 Priority:  High   |  Milestone:  Tor:
   |  0.2.8.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.2.8.2-alpha
 Severity:  Major  | Resolution:  fixed
 Keywords:  regression path TorCoreTeam201608  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * keywords:  regression path => regression path TorCoreTeam201608


--
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] #19728 [Core Tor/Tor]: Pick, and deploy, a new bridge authority

[Tor Bug Tracker & Wiki]

#19728: Pick, and deploy, a new bridge authority
---+
 Reporter:  arma   |  Owner:
 Type:  task   | Status:  needs_review
 Priority:  Immediate  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Critical   | Resolution:
 Keywords:  TorCoreTeam201608  |  Actual Points:
Parent ID: | Points:  6
 Reviewer: |Sponsor:
---+
Changes (by nickm):

 * keywords:   => TorCoreTeam201608


--
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] #20041 [Core Tor/Tor]: Test failure when running with --debug

[Tor Bug Tracker & Wiki]

#20041: Test failure when running with --debug
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  TorCoreTeam201608  |  Actual Points:  0
Parent ID: | Points:  0
 Reviewer: |Sponsor:  SponsorS-can
---+
Changes (by nickm):

 * keywords:   => TorCoreTeam201608


--
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] #19977 [Core Tor/Tor]: testsuite fails on mips, powerpc, s390x

[Tor Bug Tracker & Wiki]

#19977: testsuite fails on mips, powerpc, s390x
+--
 Reporter:  weasel  |  Owner:  dgoulet
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:  Tor:
|  0.2.9.2-alpha
 Severity:  Major   | Resolution:  fixed
 Keywords:  tor-sr, test TorCoreTeam201608  |  Actual Points:  0.5
Parent ID:  | Points:  0.2
 Reviewer:  |Sponsor:  SponsorR-
|  must
+--
Changes (by nickm):

 * keywords:  tor-sr, test => tor-sr, test TorCoreTeam201608


--
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] #19905 [Core Tor/Tor]: make-test-network-all has never detected IPv6 on linux

[Tor Bug Tracker & Wiki]

#19905: make-test-network-all has never detected IPv6 on linux
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7.3-rc
 Severity:  Normal   | Resolution:  fixed
 Keywords:  029-proposed, easy, intro,   |  Actual Points:  0.1
  TorCoreTeam201608  |
Parent ID:   | Points:  0.2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  029-proposed, easy, intro, TorCoreTeam201609 => 029-proposed,
 easy, intro, TorCoreTeam201608


--
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] #18640 [Core Tor/Tor]: Use smarter algorithms to handle socket exhaustion

[Tor Bug Tracker & Wiki]

#18640: Use smarter algorithms to handle socket exhaustion
-+-
 Reporter:  nickm|  Owner:  andrea
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-dos, TorCoreTeam201608, review-  |  implemented
  group-5, review-group-7|  Actual Points:  4
Parent ID:  #17293   | Points:  3
 Reviewer:  nickm|Sponsor:
 |  SponsorU-can
-+-
Changes (by nickm):

 * keywords:  tor-dos, TorCoreTeam201606, review-group-5, review-group-7 =>
 tor-dos, TorCoreTeam201608, review-group-5, review-group-7


Comment:

 This was finished in August

--
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] #20052 [Core Tor/Tor]: REPORT AS DIRECTED

[Tor Bug Tracker & Wiki]

#20052: REPORT AS DIRECTED
--+---
 Reporter:  baitatestor7  |  Owner:
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by dgoulet):

 * status:  new => closed
 * component:  - Select a component => Core Tor/Tor
 * resolution:   => duplicate


Comment:

 Duplicate of #7164.

--
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] [Tor Bug Tracker & Wiki] Batch modify: #13752, #17779, #19020, #19155, ...

[Tor Bug Tracker & Wiki]

Batch modification to #13752, #17779, #19020, #19155, #19156, #19157, #19158, 
#19159, #19160, #20027 by nickm:


Action: resolve

Comment:
These are implemented in 15055_wip; folding them into #15055 as their parent 
ticket.

--
Tickets 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] #15055 [Core Tor/Tor]: Implement ed25519 link handshake

[Tor Bug Tracker & Wiki]

#15055: Implement ed25519 link handshake
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, prop-220, |  Actual Points:
  027-triaged-1-in, 028-triaged, |
  201511-deferred, 201512-deferred, tor-crypto-  |
  identity, tor-ed25519-proto TorCoreTeam201609  |
Parent ID:  #15054   | Points:  parent
 Reviewer:   |Sponsor:
 |  SponsorU-must
-+-
Changes (by nickm):

 * keywords:
 tor-relay, prop-220, 027-triaged-1-in, 028-triaged, 201511-deferred,
 201512-deferred, tor-crypto-identity, tor-ed25519-proto
 =>
 tor-relay, prop-220, 027-triaged-1-in, 028-triaged, 201511-deferred,
 201512-deferred, tor-crypto-identity, tor-ed25519-proto
 TorCoreTeam201609


Comment:

 Implementation is done here; more testing needed, though.

--
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] [Tor Bug Tracker & Wiki] Batch modify: #17238, #18571, #18572, #19899, ...

[Tor Bug Tracker & Wiki]

Batch modification to #17238, #18571, #18572, #19899, #19024, #19205, #19642 by 
dgoulet:
keywords to TorCoreTeam201609

Comment:
Review and merge will happen in September.

--
Tickets 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] #20052 [- Select a component]: REPORT AS DIRECTED

[Tor Bug Tracker & Wiki]

#20052: REPORT AS DIRECTED
--+-
 Reporter:  baitatestor7  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 microdesc_free(): Bug: microdesc_free() called, but md was still
 referenced 1 node(s); held_by_nodes == 1

--
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] #20051 [Core Tor/Tor]: Unit tests for ed25519 link handshake code

[Tor Bug Tracker & Wiki]

#20051: Unit tests for ed25519 link handshake code
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  task   | Status:  accepted
 Priority:  High   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201609  |  Actual Points:
Parent ID:  #15055 | Points:  3
 Reviewer: |Sponsor:  SponsorU-must
---+
Changes (by nickm):

 * owner:   => nickm
 * status:  new => accepted


--
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] #20051 [Core Tor/Tor]: Unit tests for ed25519 link handshake code

[Tor Bug Tracker & Wiki]

#20051: Unit tests for ed25519 link handshake code
---+
 Reporter:  nickm  |  Owner:
 Type:  task   | Status:  new
 Priority:  High   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:  TorCoreTeam201609
Actual Points: |  Parent ID:  #15055
   Points:  3  |   Reviewer:
  Sponsor:  SponsorU-must  |
---+
 We can't do a halfway job on unit tests for the link handshake; we need to
 make sure everything invalid fails.  So I can't put 15055_wip into
 needs_review until the test coverage is much higher, and we really test
 all the different ways a handshake can go wrong.

--
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] #15087 [Core Tor/Tor]: Move timeliness check out of tor_cert_checksig, or into tor_cert_get_checkable_sig

[Tor Bug Tracker & Wiki]

#15087: Move timeliness check out of tor_cert_checksig, or into
tor_cert_get_checkable_sig
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7
 Severity:  Normal   | Resolution:
 Keywords:  027-triaged-1-in, 028-triaged tor-   |  implemented
  ed25519-proto TorCoreTeam201608|  Actual Points:
Parent ID:  #15054   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorU-can
-+-
Changes (by nickm):

 * status:  assigned => closed
 * resolution:   => implemented


Comment:

 Folding this back into #15055 , where it is implemented.

--
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] [Tor Bug Tracker & Wiki] Batch modify: #19301, #19302, #19303

[Tor Bug Tracker & Wiki]

Batch modification to #19301, #19302, #19303 by nickm:
keywords to TorCoreTeam201609

--
Tickets 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] [Tor Bug Tracker & Wiki] Batch modify: #19869, #16387, #19760, #19769

[Tor Bug Tracker & Wiki]

Batch modification to #19869, #16387, #19760, #19769 by nickm:
keywords to TorCoreTeam201609

Comment:
Move unassigned items in August to September.

--
Tickets 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] [Tor Bug Tracker & Wiki] Batch modify: #19292, #19293, #19303, #19904

[Tor Bug Tracker & Wiki]

Batch modification to #19292, #19293, #19303, #19904 by nickm:
keywords to TorCoreTeam201609

Comment:
Move unfinished items assigned to me to september.

--
Tickets 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] #20004 [Core Tor/Tor]: prop224: Add a trunnel subdirectory specifically for HS

[Tor Bug Tracker & Wiki]

#20004: prop224: Add a trunnel subdirectory specifically for HS
-+
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:  0.5
Parent ID:  #17241   | Points:  1
 Reviewer:   |Sponsor:  SponsorR-must
-+
Changes (by dgoulet):

 * status:  needs_revision => needs_review


Comment:

 I fixed both issues above that is the missing end mac fields pointer. I
 renamed it to the above. Note that the `union` is gone though because not
 needed.

 Linking issues should be resolved: `ticket20004_029_02`

 (This required some changes to the commits so I had to rebase squash else
 it wouldn't have merged together nor fixup commit worked.)

--
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] #19690 [Core Tor/DirAuth]: Tonga (Bridge Authority) Permanent Shutdown Notice

[Tor Bug Tracker & Wiki]

#19690: Tonga (Bridge Authority) Permanent Shutdown Notice
---+
 Reporter:  shamrock   |  Owner:  isis
 Type:  task   | Status:  assigned
 Priority:  Very High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/DirAuth   |Version:  Tor: 0.2.8.5-rc
 Severity:  Critical   | Resolution:
 Keywords:  TorCoreTeam201608  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by bugzilla):

 Replying to [comment:12 karsten]:
 > [https://people.torproject.org/~karsten/volatile/running-
 bridges-2016-09-01.png New graph] shows that transition has stopped.
 Guess we'll lose 1.3k bridges in two days from now.
 Windoze bridges?

 @shamrock:
 Who is guilty of it?

--
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] #20050 [Core Tor/Tor]: Testing: add a controller feature to generate paths without building circuits

[Tor Bug Tracker & Wiki]

#20050: Testing: add a controller feature to generate paths without building
circuits
--+--
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 For finding problems like #19973, it would be good to have a way to run
 our path generation code without actually building a circuit.  Then we
 could make thousands of paths and make sure they have the right
 properties.

 I started a `sample_path` branch for this, but it doesn't actually work so
 well.

--
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] #20049 [Metrics/Metrics website]: Adapt legacy module to accept bridge network statuses from two authorities

[Tor Bug Tracker & Wiki]

#20049: Adapt legacy module to accept bridge network statuses from two 
authorities
-+--
 Reporter:  karsten  |  Owner:
 Type:  defect   | Status:  needs_review
 Priority:  Very High|  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  new => needs_review


Comment:

 Please review [https://gitweb.torproject.org/karsten/metrics-
 web.git/log/?h=task-20049 this 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] #20049 [Metrics/Metrics website]: Adapt legacy module to accept bridge network statuses from two authorities

[Tor Bug Tracker & Wiki]

#20049: Adapt legacy module to accept bridge network statuses from two 
authorities
-+-
 Reporter:  karsten  |  Owner:
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 There are currently two bridge authorities in the network, each of them
 seeing a distinct set of bridges.  We should adapt network size statistics
 to add up set sizes for the daily number of bridges.

--
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] #5291 [Applications/Quality Assurance and Testing]: Re-test TBB on dual-stacked IPv6 machine

[Tor Bug Tracker & Wiki]

#5291: Re-test TBB on dual-stacked IPv6 machine
-+-
 Reporter:  mikeperry|  Owner:  boklm
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #5292| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by bugzilla):

 * owner:  cypherpunks => boklm
 * severity:   => Normal
 * milestone:  TorBrowserBundle 2.3.x-stable =>


Comment:

 Seems to be the right ticket for UDPv6 leaks (ticket:18937#comment:24).

--
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] #20048 [Core Tor/Tor]: Introduce `smartlist_add_strdup()` function

[Tor Bug Tracker & Wiki]

#20048: Introduce `smartlist_add_strdup()` function
--+--
 Reporter:  asn   |  Owner:
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:  0.3
 Reviewer:|Sponsor:
--+--

Comment (by nickm):

 An (untested) coccinelle script to transform the code here might look
 something like this. (If it works.)

 {{{
 @@
 expression a;
 expression b;
 @@
 - smartlist_add
 + smartlist_add_strdup
(a,
 - tor_strdup(
b
 - )
   )
 @@
 }}}

--
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] #20043 [Applications/Tor Browser]: SharedWorker uses catchall circuit

[Tor Bug Tracker & Wiki]

#20043: SharedWorker uses catchall circuit
--+--
 Reporter:  bugzilla  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-linkability   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by bugzilla):

 It's not funny at all. What is able to change prefs? Do Workers have more
 permissions than needed?
 TBB is 6.5a2 from 6.5a1 from 6.0a5 (reproducing in clean environment = no
 pref).

--
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] #20048 [Core Tor/Tor]: Introduce `smartlist_add_strdup()` function

[Tor Bug Tracker & Wiki]

#20048: Introduce `smartlist_add_strdup()` function
--+--
 Reporter:  asn   |  Owner:
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:  0.3
 Reviewer:|Sponsor:
--+--

Comment (by nickm):

 yes; please do; would merge.

--
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] #20048 [Core Tor/Tor]: Introduce `smartlist_add_strdup()` function

[Tor Bug Tracker & Wiki]

#20048: Introduce `smartlist_add_strdup()` function
--+--
 Reporter:  asn   |  Owner:
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  easy
Actual Points:|  Parent ID:
   Points:  0.3   |   Reviewer:
  Sponsor:|
--+--
 There are many places in the code (and the tests) where we do the
 following pattern:
 `smartlist_add(sl, tor_strdup(str))`

 Some examples:
 {{{
 routerparse.c:smartlist_add(ns->package_lines,
 tor_strdup(t->args[0])));
 routerparse.c:smartlist_add(ns->known_flags,
 tor_strdup(tok->args[i]));
 routerparse.c:  smartlist_add(ns->net_params,
 tor_strdup(tok->args[i]));
 routerparse.c:  smartlist_add(ns->weight_params,
 tor_strdup(tok->args[i]));
 routerparse.c:smartlist_add(md->family, tor_strdup(tok->args[i]));
 routerset.c:smartlist_add(set->country_names, tor_strdup("??"));
 routerset.c:smartlist_add(set->list, tor_strdup("{??}"));
 routerset.c:smartlist_add(set->country_names, tor_strdup("a1"));
 routerset.c:smartlist_add(set->list, tor_strdup("{a1}"));
 }}}

 One could imagine a `smartlist_add_strdup()` function that does this for
 the developer, and can be used in places where this pattern is used
 repeatedly.

 It might simplify logic in a few places, or maybe it will confuse peole
 who grep for `tor_strdup` searching for allocations.

 If people think this is worth doing, let's do it!

--
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] [Tor Bug Tracker & Wiki] Batch modify: #8799, #19282, #19822, #19828, ...

[Tor Bug Tracker & Wiki]

Batch modification to #8799, #19282, #19822, #19828, #19831 by iwakeh:


Action: reassign

Comment:
assigning these issues.

--
Tickets 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] #19778 [Metrics/CollecTor]: Bridge descriptor sanitizer runs out of memory after 13.5 days

[Tor Bug Tracker & Wiki]

#19778: Bridge descriptor sanitizer runs out of memory after 13.5 days
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * owner:   => iwakeh
 * 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] #19623 [Metrics/ExoneraTor]: use java 8 for Exonerator

[Tor Bug Tracker & Wiki]

#19623: use java 8 for Exonerator
+--
 Reporter:  iwakeh  |  Owner:
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  ExoneraTor 2.0.0
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #19617  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * milestone:   => ExoneraTor 2.0.0


--
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] #19624 [Metrics/ExoneraTor]: Exonerator should comply to Metrics Java style guide

[Tor Bug Tracker & Wiki]

#19624: Exonerator should comply to Metrics Java style guide
+--
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  task| Status:  assigned
 Priority:  Medium  |  Milestone:  ExoneraTor 1.0.0
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #19611  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * milestone:   => ExoneraTor 1.0.0


--
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] #19016 [Metrics/CollecTor]: add shutdown hook

[Tor Bug Tracker & Wiki]

#19016: add shutdown hook
---+---
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_information
 Priority:  Low|  Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by iwakeh):

 * status:  new => needs_information


Comment:

 With the scheduler functionality it makes sense to revisit this ticket.

 Tasks for the shutdown-hook:
 * start a regular scheduler shutdown, which lets all running tasks finish
 and exits.
 * this is written to the logs in order to make the operator aware that a
 shutdown is running.

 What else?

--
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] #19934 [Metrics/CollecTor]: CollecTor should use new metrics-lib json classes

[Tor Bug Tracker & Wiki]

#19934: CollecTor should use new metrics-lib json classes
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * 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] #19169 [Metrics/CollecTor]: verify, correct and extend runtime statistics

[Tor Bug Tracker & Wiki]

#19169: verify, correct and extend runtime statistics
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:  CollecTor 1.2.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * milestone:  CollecTor 1.1.0 => CollecTor 1.2.0


Comment:

 This should be tackled when synchronization is in place.

--
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] #20037 [Metrics/CollecTor]: Add support for Bifroest's bridge descriptor tarballs

[Tor Bug Tracker & Wiki]

#20037: Add support for Bifroest's bridge descriptor tarballs
---+-
 Reporter:  karsten|  Owner:
 Type:  enhancement| Status:  merge_ready
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 added reminder to #19755 for additional tests; this could be closed after
 merge then.

--
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] #19755 [Metrics/CollecTor]: improve code quality of bridgedescs module

[Tor Bug Tracker & Wiki]

#19755: improve code quality of bridgedescs module
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 add tests also for new code from #20037.

--
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] #20043 [Applications/Tor Browser]: SharedWorker uses catchall circuit

[Tor Bug Tracker & Wiki]

#20043: SharedWorker uses catchall circuit
--+--
 Reporter:  bugzilla  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-linkability   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * cc: arthuredelstein (added)
 * keywords:  tbb-linkability, tbb-pref => tbb-linkability
 * severity:  Normal => Major
 * priority:  Medium => High


Comment:

 That pref does not exist anymore in 6.5a2. Not sure what Tor Browser you
 are using. Maybe it is somehow a left-over? In any case that pref does not
 do anything anymore.

 That said, I can see a similar log output on the command line.

--
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] #20004 [Core Tor/Tor]: prop224: Add a trunnel subdirectory specifically for HS

[Tor Bug Tracker & Wiki]

#20004: prop224: Add a trunnel subdirectory specifically for HS
-+
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:  needs_revision
 Priority:  Medium   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:  0.5
Parent ID:  #17241   | Points:  1
 Reviewer:   |Sponsor:  SponsorR-must
-+
Changes (by asn):

 * status:  needs_review => needs_revision


--
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] #20004 [Core Tor/Tor]: prop224: Add a trunnel subdirectory specifically for HS

[Tor Bug Tracker & Wiki]

#20004: prop224: Add a trunnel subdirectory specifically for HS
-+
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:  0.5
Parent ID:  #17241   | Points:  1
 Reviewer:   |Sponsor:  SponsorR-must
-+

Comment (by asn):

 I think there is a problem with the linking as well. I'm getting the
 following errors when I try to compile my code on top of your branch:
 {{{
 src/or/libtor.a(hs_intropoint.o): In function
 `get_auth_key_from_establish_intro_cell':
 /home/tor/src/or/hs_intropoint.c:34: undefined reference to
 `hs_cell_establish_intro_getarray_auth_key'
 src/or/libtor.a(hs_intropoint.o): In function `handle_establish_intro':
 /home/tor/src/or/hs_intropoint.c:155: undefined reference to
 `hs_cell_establish_intro_parse'
 src/or/libtor.a(hs_intropoint.o): In function
 `verify_establish_intro_cell':
 /home/tor/src/or/hs_intropoint.c:74: undefined reference to
 `hs_cell_establish_intro_getarray_sig'
 }}}

 If I explicitly include the `src/trunnel/hs/libor-trunnel-hs.a` library in
 the gcc command it works. So maybe there is an issue with the `LIBADD`?

 Did you manage to compile fine with this 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] #20047 [Metrics/Onionoo]: automatically surround an ipv6 address with [] in the search field

[Tor Bug Tracker & Wiki]

#20047: automatically surround an ipv6 address with [] in the search field
-+-
 Reporter:  toralf   |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 this supports lazy users like me

--
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] #5837 [Applications/Quality Assurance and Testing]: Use IDA Pro and/or BinDiff to inspect releases

[Tor Bug Tracker & Wiki]

#5837: Use IDA Pro and/or BinDiff to inspect releases
-+-
 Reporter:  mikeperry|  Owner:
 |  cypherpunks
 Type:  project  | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing| Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  volunteer|  Actual Points:
Parent ID:  #5292| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * cc: g.koppen@… (removed)
 * cc: gk (added)
 * status:  new => closed
 * resolution:   => worksforme
 * severity:   => Normal


Comment:

 I think this can indeed get closed thanks to our reproducible builds.

--
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] #5290 [Applications/Quality Assurance and Testing]: Collect+write test pages for JavaScript hooks

[Tor Bug Tracker & Wiki]

#5290: Collect+write test pages for JavaScript hooks
-+-
 Reporter:  mikeperry|  Owner:  boklm
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:  #5292| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 This is an old and cluttered bug, we don't have JS hooks anymore and we
 don't use Mozmill anymore. Time for closing this I guess.

--
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] #20040 [Applications/Tor Browser]: fix MAR file generation to account for packed HTTPS Everywhere

[Tor Bug Tracker & Wiki]

#20040: fix MAR file generation to account for packed HTTPS Everywhere
--+
 Reporter:  mcs   |  Owner:  mcs
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201608R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

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


Comment:

 Looks good to me. This is commit 082d1c5e03617458f366b597256597bbde079889
 on tor-browser-45.3.0esr-6.5-1.

 I guess we want to have that for the stable as well? Did you test that and
 verified that the fix worked properly in that particular case?

--
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] #20033 [HTTPS Everywhere/EFF-HTTPS Everywhere]: httpseverywhere too many files very slow to make usb stick

[Tor Bug Tracker & Wiki]

#20033: httpseverywhere too many files very slow to make usb stick
-+-
 Reporter:  keb  |  Owner:  jsha
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:  HTTPS-E
  Everywhere |  3.4.3
 Severity:  Normal   | Resolution:  not a
 |  bug
 Keywords:  tbb l10n https-e usb ux  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  new => closed
 * resolution:   => not a bug


Comment:

 Seems to be not an HTTPS-Everywhere bug then anymore. We'll solve that on
 the Tor Browser side with the next update (#20040 takes care of this).

--
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] #20004 [Core Tor/Tor]: prop224: Add a trunnel subdirectory specifically for HS

[Tor Bug Tracker & Wiki]

#20004: prop224: Add a trunnel subdirectory specifically for HS
-+
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:  0.5
Parent ID:  #17241   | Points:  1
 Reviewer:   |Sponsor:  SponsorR-must
-+
Changes (by asn):

 * status:  needs_revision => needs_review


Comment:

 Another issue with ESTABLISH_INTRO:

 In the spec we say:
 {{{
The HANDSHAKE_AUTH field contains the MAC of all earlier fields in
the cell using as its key the shared per-circuit material ("KH")
generated during the circuit extension protocol; see tor-spec.txt
section 5.2, "Setting circuit keys". It prevents replays of
ESTABLISH_INTRO cells.
 }}}

 In this case, `end_mac_data` should be right before the `handshake_mac`
 field and not in the end. Also, there should probably be another `ptr`
 called `end_sig_data` right before the sig. Or do you think the spec is
 wrong?

 Here is how Alex had his pointers, and that's how I have it in my code.
 Let's keep the same ptr position if possible:

 {{{
 struct hs_establish_intro_cell {
   @ptr start_cell;
   u8 auth_key_type;
   u16 auth_key_len;
   u8 auth_key[auth_key_len];
   u8 n_extensions;
   struct extension extensions[n_extensions];
   @ptr end_mac_fields;
   /* Modify if any new handshake types are added */
   union handshake[auth_key_type] {
 2: u8 sha3_256[SHA3_256_MAC_LEN];
 default: fail;
   };
   u16 siglen;
   @ptr end_sig_fields;
   u8 sig[siglen];
 };
 }}}

--
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] #14271 [Applications/Tor Browser]: Make Torbutton work with Unix Domain Socket option

[Tor Bug Tracker & Wiki]

#14271: Make Torbutton work with Unix Domain Socket option
-+-
 Reporter:  gk   |  Owner:  brade
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-torbutton, tbb-security, |  Actual Points:
  TorBrowserTeam201609   |
Parent ID:  #14270   | Points:
 Reviewer:   |Sponsor:
 |  SponsorU
-+-
Changes (by gk):

 * keywords:  tbb-torbutton, tbb-security, TorBrowserTeam201608R => tbb-
 torbutton, tbb-security, TorBrowserTeam201609
 * status:  needs_review => needs_revision


Comment:

 Here are some comments:

 1)
 {{{
 +// given sockFile or host and port.
 }}}
 s/sockFile/socketFile/

 2)
 {{{
 let tlps = Cc["@torproject.org/torlauncher-protocol-service;1"]
  .getService(Ci.nsISupports).wrappedJSObject;
 }}}
 We should do that once and not twice in `torbutton_init()`.

 3) Checking whether we should call `torbutton_local_tor_check()` should
 check for
 `m_tb_control_socket_file` as well (not only for `m_tb_control_port`) I
 guess?

 4) I am not so sure about
 {{{
 +} catch(e) {
 +  m_tb_control_port = 9151;
 +}
 }}}
 What was your rationale for adding that now (given you omitted it
 earlier)? For one, the logs might be misleading showing a probably wrong
 port (I mean the setup is seriously troubling if we need to assign `9151`
 in the catch clause at all) in an error with respect to the control
 connection. On the other hand, we might want to show that something is
 wrong with the help of `torbutton_do_tor_check()` which would update the
 toolbar button in this case (if we get that far at all with a broken setup
 like the one in question).

--
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] #19690 [Core Tor/DirAuth]: Tonga (Bridge Authority) Permanent Shutdown Notice

[Tor Bug Tracker & Wiki]

#19690: Tonga (Bridge Authority) Permanent Shutdown Notice
---+
 Reporter:  shamrock   |  Owner:  isis
 Type:  task   | Status:  assigned
 Priority:  Very High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/DirAuth   |Version:  Tor: 0.2.8.5-rc
 Severity:  Critical   | Resolution:
 Keywords:  TorCoreTeam201608  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by karsten):

 [https://people.torproject.org/~karsten/volatile/running-
 bridges-2016-09-01.png New graph] shows that transition has stopped.
 Guess we'll lose 1.3k bridges in two days from now.

--
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] #14272 [Applications/Tor Launcher]: Make Tor Launcher work with Unix Domain Socket option

[Tor Bug Tracker & Wiki]

#14272: Make Tor Launcher work with Unix Domain Socket option
-+-
 Reporter:  gk   |  Owner:  brade
 Type:  enhancement  | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Tor Launcher|Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-security, TorBrowserTeam201608R  |  Actual Points:
Parent ID:  #14270   | Points:
 Reviewer:   |Sponsor:
 |  SponsorU
-+-
Changes (by gk):

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


Comment:

 Thanks, this is commit 8871259c966755233b134a5ddb2b4926539d25c6 on master.
 I'll get that onto the proper maint branch for the alphas later. I added a
 typo-fix-commit as well (commit 32ddac7015be571c336be686b4f901103d0d36f6)
 to save us one round-trip.

--
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] #19966 [Core Tor/Tor]: torproxy goes south with more than 1 connection attempt per second to a hidden service

[Tor Bug Tracker & Wiki]

#19966: torproxy goes south with more than 1 connection attempt per second to a
hidden service
---+
 Reporter:  Alan   |  Owner:
 Type:  defect | Status:  new
 Priority:  High   |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor   |Version:  Tor: 0.2.8.6
 Severity:  Major  | Resolution:
 Keywords:  hidden service client  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by Alan):

 * milestone:  Tor: 0.2.9.x-final => Tor: 0.2.8.x-final


--
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