date:20180605

Re: [tor-bugs] #23588 [Core Tor/Tor]: Write fascist_firewall_choose_address_ls() and use it in hs_get_extend_info_from_lspecs()

2018-06-05 Thread Tor Bug Tracker & Wiki

#23588: Write fascist_firewall_choose_address_ls() and use it in
hs_get_extend_info_from_lspecs()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:
  ipv6, 034-triage-20180328, |
  034-removed-20180328   |
Parent ID:  #23493   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by neel):

 * status:  new => assigned
 * cc: neel@… (added)
 * owner:  (none) => neel


--
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] #26197 [Internal Services/Service - git]: Sync git.torproject.org/stem.git to github.com/torproject/stem.git

2018-06-05 Thread Tor Bug Tracker & Wiki

#26197: Sync git.torproject.org/stem.git to github.com/torproject/stem.git
-+
 Reporter:  teor |  Owner:  tor-gitadm
 Type:  task | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by atagar):

 Thanks Isis! Accepted the GitHub invitation and pushed Stem's current head
 to get the new repo caught up.

 Does our wiki have any mirroring instructions? I'm unsure if there's some
 action is needed on my part, or there's someone I need to ask.

--
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] #26317 [- Select a component]: Orfox App is not allowing the users to save images

2018-06-05 Thread Tor Bug Tracker & Wiki

#26317: Orfox App is not allowing the users to save images
--+
 Reporter:  fabiola.mauriceh@…|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Hi,

 We have a couple reports about the "Save Image" option in Orfox, it is
 currently not working.

--
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] #22867 [Applications/Tor Browser]: Some URLs are saved in the Tor Browser places.sqlite database as part of the browsing history

2018-06-05 Thread Tor Bug Tracker & Wiki

#22867: Some URLs are saved in the Tor Browser places.sqlite database as part of
the browsing history
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-disk-leak |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 #26315 is a duplicate.

--
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] #26315 [Applications/Tor Browser]: Strange URL present in Tor Browser

2018-06-05 Thread Tor Bug Tracker & Wiki

#26315: Strange URL present in Tor Browser
--+---
 Reporter:  durbanpoison  |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by cypherpunks):

 * component:  - Select a component => Applications/Tor Browser


--
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] #26315 [- Select a component]: Strange URL present in Tor Browser

2018-06-05 Thread Tor Bug Tracker & Wiki

#26315: Strange URL present in Tor Browser
--+---
 Reporter:  durbanpoison  |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by cypherpunks):

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


Comment:

 Duplicate of: #22867

--
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] #26316 [Core Tor/Tor]: Windows newlines in extrainfo descriptor

2018-06-05 Thread Tor Bug Tracker & Wiki

#26316: Windows newlines in extrainfo descriptor
--+
 Reporter:  atagar|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Hi Network Team, the following extrainfo descriptor is making Stem's
 parser error with "Malformed dirreq-stats-end line: dirreq-stats-end
 2018-06-05 06:11:40 (86400 s)"...

 {{{
 extra-info Jittor E062E8AD9FA8907D140ECFC406D5DAFD4B23F300
 identity-ed25519
 -BEGIN ED25519 CERT-
 AQQABnvMATGms3ONiqeM1KNjSmQQVTcmVFwb7pHjW6b4qB4DhqG/AQAgBACmvl+Y
 QFLCTyOfsf9cL9qL7IDZLOceNdcTJSNGPzevmvgB827O9wO0IDxY4V10wDxHRiNG
 TPy43S5ag5hWvyKzI3hGA/sz7+8NwnGEqFrjg9nlZt/FADvdC0Ow9owIHwU=
 -END ED25519 CERT-
 published 2018-06-05 12:27:03
 geoip-db-digest 765D2F123DDA7DAEA9C9263975E2B4BAFBD2B908
 geoip6-db-digest 2AA568CC898BF9924FBACEA26946AA7ED10E7D87
 dirreq-stats-end 2018-06-05 06:11:40 (86400 s)^M
 dirreq-v3-ips
 
ru=488,us=400,de=264,ua=168,fr=160,gb=128,it=96,br=80,es=80,jp=80,ca=64,in=56,nl=56,pl=56,ar=32,au=32,tw=32,by=24,ch=24,cz=24,fi=24,id=24,ir=24,mx=24,ae=16,at=16,be=16,bg=16,gr=16,hk=16,hu=16,ie=16,il=16,lt=16,lv=16,my=16,no=16,pt=16,ro=16,rs=16,se=16,th=16,vn=16,??=8,ba=8,bd=8,bh=8,bj=8,ci=8,cl=8,cn=8,co=8,cr=8,cw=8,cy=8,dk=8,do=8,dz=8,ec=8,ee=8,et=8,ge=8,gh=8,gp=8,gt=8,gy=8,hr=8,iq=8,is=8,ke=8,kr=8,kw=8,kz=8,lk=8,lu=8,ma=8,md=8,me=8,mg=8,mu=8,mv=8,na=8,nz=8,pe=8,ph=8,pk=8,sd=8,sg=8,si=8,sk=8,sv=8,sy=8,tc=8,td=8,tn=8,tr=8,ug=8,uy=8,ve=8,za=8^M
 dirreq-v3-reqs
 
us=1464,ru=1048,de=752,fr=440,ua=280,gb=200,br=144,ca=136,it=136,jp=136,es=120,nl=120,pl=88,in=80,by=56,tw=56,au=48,ch=48,cz=48,id=48,md=48,se=48,ar=40,ir=40,ae=32,at=32,lt=32,mx=32,no=32,??=24,fi=24,hu=24,ie=24,il=24,lv=24,pt=24,ro=24,sg=24,vn=24,be=16,bg=16,cl=16,co=16,gr=16,hk=16,hr=16,is=16,kr=16,my=16,ph=16,rs=16,th=16,tr=16,ve=16,ba=8,bd=8,bh=8,bj=8,ci=8,cn=8,cr=8,cw=8,cy=8,dk=8,do=8,dz=8,ec=8,ee=8,et=8,ge=8,gh=8,gp=8,gt=8,gy=8,iq=8,ke=8,kw=8,kz=8,lk=8,lu=8,ma=8,me=8,mg=8,mu=8,mv=8,na=8,nz=8,pe=8,pk=8,sd=8,si=8,sk=8,sv=8,sy=8,tc=8,td=8,tn=8,ug=8,uy=8,za=8^M
 dirreq-v3-resp ok=6200,not-enough-sigs=16,unavailable=0,not-found=0,not-
 modified=1120,busy=0^M
 dirreq-v3-direct-dl
 
complete=16,timeout=0,running=0,min=229451,d1=229451,d2=516011,q1=1012307,d3=1012307,d4=1059359,md=1587774,d6=2175000,d7=2758125,q3=3023437,d8=3023437,d9=3105875,max=3332493^M
 dirreq-v3-tunneled-dl
 
complete=6048,timeout=136,running=0,min=360,d1=147601,d2=281819,q1=344834,d3=417296,d4=547425,md=705125,d6=916070,d7=1265607,q3=1371936,d8=1660923,d9=2477000,max=41697000^M
 hidserv-stats-end 2018-06-05 06:11:40 (86400 s)^M
 hidserv-rend-relayed-cells 5973866 delta_f=2048 epsilon=0.30
 bin_size=1024^M
 hidserv-dir-onions-seen 262 delta_f=8 epsilon=0.30 bin_size=8^M
 router-sig-ed25519
 
kZGzsa4k+78QHsyb/0FXWBJYxttV8KvVHV/LiMH1muGAk/f9fj9c+lYusnhK9sql+AB7r5b0j6uaNR7ZTCXLBw
 router-signature
 -BEGIN SIGNATURE-
 WjdbB6hbV9cyHWMqglNNMfjuT+WUvOmqP+IvMgwCke5/cXXEHOzqVXsVFdXmEBsg
 HQOjB4vlmK4n6diTc2O0LkUzZTk1XIQwZOyKjtFNi0OrQye6mJA9gKaCIQUF3CDZ
 XL6dW0QQaXgURTlm3oApAsZ+vRzI/Wfq9YxjTCLc9u4=
 -END SIGNATURE-
 }}}

 You can fetch this descriptor for yourself with...

 {{{
 curl
 http://154.35.175.225:80/tor/extra/fp/E062E8AD9FA8907D140ECFC406D5DAFD4B23F300
 }}}

 Note the "!^M" trailing a handful (but not all) of lines. Those are
 Windows carriage returns (\r\n line endings). There's two issues here,
 first that somehow this is getting published on metric lines and second
 that the dirauths aren't rejecting this descriptor.

 According to its server descriptor this relay
 
([https://metrics.torproject.org/rs.html#details/E062E8AD9FA8907D140ECFC406D5DAFD4B23F300
 Jittor]) is running Tor 0.3.3.6 on Linux.

 That's right. Windows newlines on Linux. Pity we don't note the distro. :P

 Thanks!

--
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] #26315 [- Select a component]: Strange URL present in Tor Browser

2018-06-05 Thread Tor Bug Tracker & Wiki

#26315: Strange URL present in Tor Browser
--+
 Reporter:  durbanpoison  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Hello, I have downloaded the latest Tor Browser. When I open up the
 browser and type "S" into the URL bar I am shown the following option as a
 URL to visit in the immediate dropdown:

 https://accounts.google.com/ServiceLogin?continue=https://www.blogger.com
 /comment-
 
iframe.g?blogID%3D8604365531474097912%26postID%3D5300054375024002%26blogspotRpcToken%3D3210145%26bpli%3D1=https://www.blogger.com
 /comment-
 
iframe.g?blogID%3D8604365531474097912%26postID%3D5300054375024002%26blogspotRpcToken%3D3210145%26bpli%3D1=true=true#{%22color%22%3A%22rgb(51%2C%2051%2C%2051)%22%2C%22backgroundColor%22%3A%22rgb(255%2C%20255%2C%20255)%22%2C%22unvisitedLinkColor%22%3A%22rgb(51%2C%20102%2C%20153)%22%2C%22fontFamily%22%3A%22Arial%2CTahoma%2CHelvetica%2CFreeSans
 %2Csans-serif%22}

 I've never visited this strange URL before and don't know why it's showing
 up in my browser. Please investigate.

--
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] #26309 [Applications/Tor Browser]: Lost previous tabs when updated to 7.5.4

2018-06-05 Thread Tor Bug Tracker & Wiki

#26309: Lost previous tabs when updated to 7.5.4
--+---
 Reporter:  artemik   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Low   |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * priority:  Medium => Low
 * status:  new => needs_information


--
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] #26233 [Applications/Tor Browser]: Rebase Tor Browser patches for FF61

2018-06-05 Thread Tor Bug Tracker & Wiki

#26233: Rebase Tor Browser patches for FF61
--+
 Reporter:  sysrqb|  Owner:  sysrqb
 Type:  enhancement   | Status:
  |  needs_revision
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201806, tbb-mobile  |  Actual Points:
Parent ID:  #25741| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

 * status:  needs_review => needs_revision
 * keywords:  TorBrowserTeam201806R, tbb-mobile => TorBrowserTeam201806,
 tbb-mobile


Comment:

 Okay, here comes the review. I think MAR files and the signing machinery
 we have won't play a role for Android (see: #26242 for our update
 strategy), thus we can ignore all the signing related patches, I agree.
 I've been a bit more agressive when reviewing your changes. Here is all I
 got:

 c7036c883efebaf0ee6d27285e7a5f9d0abe8eb8 -- good (4bdb543b0ae7)
 2078afc6814a8f0303d9a83c050c068bda704ce3 -- not okay (0e8dbb37c450)
 {{{
 > +// Disable window.Components shim (substitue for
 https://bugs.torproject.org/2874)
 > +pref("dom.use_components_shim", false);
 }}}
 "substitue" and could you mention the Mozilla bug number (1448048)? What's
 the relation to https://bugzilla.mozilla.org/1401260?

 f2c4006d0958a61d671ad7ab8e4c097115ece39c -- okay (1cbd34d3b0b8)
 dfca44dbb3011918f1860ff10ddf7fa825b33713 -- okay (837f8e888cf5)
 4df8383599da34d038e47980ce6005f6355d6a43 -- okay (fe1e6ce7f8d8)
 5e9c8426b5d485ecc02c85cbb98d11305310ef79 -- okay (58a737f021b2)

 F e0cb606a47ac Bug 2874: Block Components.interfaces from content <- I was
 confused by that because there is no bug 2874 related patch anymore. So,
 better "O" I guess.

 5de7b7cdcf120b1fcf29f51d2ce2659d317ec445 -- okay (dfd201a96767)
 9abd24dae812b2f3fc2918b2fb22285f9c3b1392 -- okay (ccebcbb95267)
 8657933084abd6cb6745239698b8d24e11d69dc1 -- okay (87cb0833ffdd)
 ef0eee9cb5aa10e338c1979ff51d7fa6b90f6b0b -- okay (10ac5a7be31f)
 c96db008adde9b8f692786ce5dab817eca961507 -- okay (b6d8bf568ba6)
 ec4d2f41b75d3be3c239421fc6e6905d65efe8e7 -- okay (1dc1a4f7fedc)
 a8e5b7264ecf03e4d554d7a5cfead42159144d0d -- not okay (93a8e5d1b523)

 I think that can go as the patch got upstreamed in bug 967812 (it seems I
 overlooked that by the review for ESR60). Or do we want to keep the test
 because the upstreamed patch does not contain tests? In that case I am
 fine with keeping it for now but we should get the test on the uplift
 radar in this case (why is it marked as `tbb-no-uplift`?).

 174ce1dc9a00c7af8fd1019cc30e24903fada4d7 -- okay (6b35333f3a3a)
 1a683a1d1d0079dafa15a4a3957da24182ea1f44 -- okay (c5b57b1bf1df)
 36d44849da69cf008023519cb4bcede18e96c99c -- okay (16a1bcef4e15)
 6da338503b55259c63160c5e24536ff1e77b5184 -- okay (006dffb468ee)
 1b35f4478c904b0990a45d4a5f191fcc62f4b9ba -- okay (6734d99f40b0)
 6300c93066d07ea3fa54c31852c1564992383877 -- okay (48b1c08e1fff)
 184d59cff2b987c608d9746badd7a007f00423b8 -- okay (5823d75f953a)
 c4331c511caf1a2feaa95e6f6bfcbcd3393907b8 -- okay (cc9862c27fd5)
 f3140e62aaa16e05e9202d6dd4e656886bb285fd -- okay (40752ee655eb)
 e09d2897b4d67e3f65212269e6b774047bfe75fe -- okay (27fa6ab6fa2b)
 f1e3011eb042f516c24de3734b42a1e71d8744c1 -- not okay (612aefdabd9b)

 It seems we don't need that test anymore given that the patch is basically
 obsolete (i.e. the fingerprinting defense got "upstreamed").

 cee52946e9d5b16bb0c42d69e6896d7334995f58 -- okay (4da1d08fb2e2)
 ead92b734879ab153db67da293ac9cb6add8a186 -- okay (17367581443f)
 acef0857f3f6aeac13f4e94eb98f8b55d28e1127 -- okay (71a812c584aa)
 79289c71dc16e3064e1ceb17fb1900e0d08273d8 -- not okay (4e0aed04f7f7)

 Where are the changes in nsToolkitProfileService.cpp etc. coming from? I
 fail to find them on m-c. It seems to me we don't want to differe more
 than needed from Mozilla here.

 f4c2dd434d4bb4aa5cbe4937c6f4e5f85eef74f9 -- okay (716067b4c679)
 3f7ac7eb4d1fc0e66b3105fa105c639aea134733 -- not okay (b95e30974e71)

 not needed for android as it is an updater patch

 a5a2ed6a11b3b1042e02f568f61f8de45a715f49 -- not okay (75d6387d)

 not needed for android as it is an updater patch

 999fe945d5c6f7cbc53c5546a11a4284fb2da71d -- okay (cab08be85615)
 ca4a654280c0a04e89a4dc8b926c540cfb9fb554 -- okay (a4ac08e62457)

 6dad47dd282fe46e888c56e3067869bf99cec47f -- not okay (9a3bb35800d5)

 not needed for android as it is an updater patch

 1478cf4bf40f50144ef053d0e27d5e39946c11ba -- not okay (39f10aaa10ef)

 not needed for android as it is an updater patch

 026597a98e8a75442bc59978d7f2b43bc98c0e2d -- okay (7ca562c26856)
 013a9bd751a57e3b2d28adebe4c742b2300624a8 -- not okay

Re: [tor-bugs] #26242 [Applications/Tor Browser]: Implement update strategy for TBA

2018-06-05 Thread Tor Bug Tracker & Wiki

#26242: Implement update strategy for TBA
--+--
 Reporter:  igt0  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 So, to be clear wrt to the basics the general update strategy on Android
 is just to get a new .apk over the old one, right? Or is there a cleverer
 one with just applying diffs?

--
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] #10416 [Core Tor/Tor]: Tor won't start on Windows when path contains non-ascii characters

2018-06-05 Thread Tor Bug Tracker & Wiki

#10416: Tor won't start on Windows when path contains non-ascii characters
-+-
 Reporter:  iktsuarpok   |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.3.25
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, windows, unicode, win32  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 Is this bug causing all Windows users with weird characters in their
 username to have their Tor Browser fail when they try to run it from their
 user directory?

 I haven't heard from any affected users, so maybe it's not so bad -- or
 instead, maybe users like that are less likely to come usefully report a
 bug to us in English.

--
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] #26314 [Webpages/Website]: Create "Learn More" Landing Page for TBA

2018-06-05 Thread Tor Bug Tracker & Wiki

#26314: Create "Learn More" Landing Page for TBA
--+
 Reporter:  sysrqb|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 When TBA is first launched there is a "Learn More" link the user can
 click. We should take advantage of this and create a useful webpage where
 the user can learn more. (Orfox currently has this, too, and the link goes
 to [[https://guardianproject.info/apps/orfox|the Guardian Project's Orfox
 page]].

--
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] #26309 [Applications/Tor Browser]: Lost previous tabs when updated to 7.5.4

2018-06-05 Thread Tor Bug Tracker & Wiki

#26309: Lost previous tabs when updated to 7.5.4
--+--
 Reporter:  artemik   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 Sounds like you're using Tor Browser in an unusual configuration, so you
 could easily be running into bugs that few other people (and no Tor
 Browser devs) run into.

 I don't think Tor Browser is meant to be broken in this way (i.e. discard
 things that you configured it to not discard), but you're going to need to
 provide clear steps to reproduce your problem, before the devs will have a
 chance of figuring out what went wrong. What exactly did you change in the
 configurations? Can you throw out your current Tor Browser, start with the
 old one, retrace those steps, and then see if it happens to you 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] #26309 [Applications/Tor Browser]: Lost previous tabs when updated to 7.5.4

2018-06-05 Thread Tor Bug Tracker & Wiki

#26309: Lost previous tabs when updated to 7.5.4
--+--
 Reporter:  artemik   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by arma):

 * owner:  (none) => tbb-team
 * component:  - Select a component => Applications/Tor Browser


--
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] #26308 [Webpages/Website]: Please add job description to webpage - Fundraising Director

2018-06-05 Thread Tor Bug Tracker & Wiki

#26308: Please add job description to webpage - Fundraising Director
--+-
 Reporter:  ewyatt|  Owner:  (none)
 Type:  task  | Status:  closed
 Priority:  Immediate |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  implemented
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by hiro):

 * status:  new => closed
 * resolution:   => 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

Re: [tor-bugs] #26310 [Core Tor/Tor]: Refusing to apply consensus diff because the base consensus doesn't match the digest as found in the consensus diff header.

2018-06-05 Thread Tor Bug Tracker & Wiki

#26310: Refusing to apply consensus diff because the base consensus doesn't 
match
the digest as found in the consensus diff header.
--+--
 Reporter:  Logforme  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 Well, it's complaining about a bunch of dir auths, not just mine. So that
 does help to reduce some of the possible causes.

 Something else weird: why is it exactly the same set of fingerprints that
 it's complaining about, for more than a day?

 Did this relay get a microdesc consensus that nobody else got?

 I wonder if there are more log entries we could put in, to get better
 hints for the next person who hits this 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] #26233 [Applications/Tor Browser]: Rebase Tor Browser patches for FF61

2018-06-05 Thread Tor Bug Tracker & Wiki

#26233: Rebase Tor Browser patches for FF61
---+---
 Reporter:  sysrqb |  Owner:  sysrqb
 Type:  enhancement| Status:
   |  needs_review
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201806R, tbb-mobile  |  Actual Points:
Parent ID:  #25741 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by sysrqb):

 Initial testing with rebasing this branch on top of my current #25741
 branch is looking good! Thanks!

 I added two fixups on top of my branch[0] that disable (ifdef-out) unused
 code which cause build failure when compiled with -Werror. This allows for
 running Try builds[1][2]. The HEAD commit is needed because it's possible
 mozilla-central and mozilla-beta don't have any commits by ffxbld within
 the last 500 commits (as is currently the situation).

 I'm trying to get the Tor Browser mochitests working - but I won't spend
 too much time on this. I think I'm hitting a local issue.

 [1] https://gitweb.torproject.org/user/sysrqb/tor-
 browser.git/log/?h=26233%2b25741
 [1]
 
https://treeherder.mozilla.org/#/jobs?repo=try=aeeb247553c2d713478083d3f02bb9c9a78bf0a7
 [2]
 
https://treeherder.mozilla.org/#/jobs?repo=try=c26bc84a8caffb2000475016edf5114b4e049193

--
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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---

Comment (by cypherpunks):

 Antonela, please consider #23547 as well for the Tor Browser UI. Thanks!

--
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] #26310 [Core Tor/Tor]: Refusing to apply consensus diff because the base consensus doesn't match the digest as found in the consensus diff header.

2018-06-05 Thread Tor Bug Tracker & Wiki

#26310: Refusing to apply consensus diff because the base consensus doesn't 
match
the digest as found in the consensus diff header.
--+--
 Reporter:  Logforme  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Logforme):

 Regarding old libraries. I should add that the relay runs on a very old
 Debian Wheezy.
 {{{
 uname -a
 Linux  3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.39-1+deb8u1~bpo70+1
 (2017-02-24) x86_64 GNU/Linux
 }}}
 What libraries are of interest? Maybe I can find them (I'm a Linux noob)

--
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] #26310 [Core Tor/Tor]: Refusing to apply consensus diff because the base consensus doesn't match the digest as found in the consensus diff header.

2018-06-05 Thread Tor Bug Tracker & Wiki

#26310: Refusing to apply consensus diff because the base consensus doesn't 
match
the digest as found in the consensus diff header.
--+--
 Reporter:  Logforme  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Logforme):

 No interesting log entries apart from the consensus ones.
 Yesterday:
 {{{
 Jun 04 06:25:02.000 [notice] Tor 0.3.3.6 (git-c9903102c98cd028) opening
 new log file.
 Jun 04 09:17:17.000 [notice] Heartbeat: Tor's uptime is 10 days 23:59
 hours, with 47346 circuits open. I've sent 19943.69 GB and received
 19278.75 GB.
 Jun 04 09:17:17.000 [notice] Circuit handshake stats since last time:
 96649/96649 TAP, 729879/729879 NTor.
 Jun 04 09:17:17.000 [notice] Since startup, we have initiated 0 v1
 connections, 0 v2 connections, 0 v3 connections, and 148897 v4
 connections; and received 481 v1 connections, 127734 v2 connections,
 199468 v3 connections, and 1769367 v4 connections.
 Jun 04 09:17:17.000 [notice] DoS mitigation since startup: 33 circuits
 killed with too many cells. 1297896 circuits rejected, 47 marked
 addresses. 232489 connections closed. 3578 single hop clients refused.
 Jun 04 12:07:20.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:07:20.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:07:20.000 [warn] Could not apply consensus diff received from
 server '193.23.244.244:80'
 Jun 04 12:08:20.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:08:20.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:08:20.000 [warn] Could not apply consensus diff received from
 server '171.25.193.9:443'
 Jun 04 12:09:20.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:09:20.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:09:20.000 [warn] Could not apply consensus diff received from
 server '131.188.40.189:80'
 Jun 04 12:10:20.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:10:20.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:10:20.000 [warn] Could not apply consensus diff received from
 server '199.58.81.140:80'
 Jun 04 12:11:21.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:11:21.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:11:21.000 [warn] Could not apply consensus diff received from
 server '86.59.21.38:80'
 Jun 04 12:12:20.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:12:20.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:12:20.000 [warn] Could not apply consensus diff received from
 server '128.31.0.34:9131'
 Jun 04 12:13:20.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:13:20.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:13:20.000 [warn] Could not apply consensus diff received from
 server '194.109.206.212:80'
 Jun 04 12:15:20.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 04 12:15:20.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 04 12:15:20.000 [warn] Could not apply consensus diff received from
 server

Re: [tor-bugs] #25957 [Core Tor/Tor]: Tor 0.3.3.5-rc died: Caught signal 11

2018-06-05 Thread Tor Bug Tracker & Wiki

#25957: Tor 0.3.3.5-rc died: Caught signal 11
+---
 Reporter:  Pine64ARMv8 |  Owner:  (none)
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:  Tor: 0.3.3.5-rc
 Severity:  Normal  | Resolution:
 Keywords:  crash, openssl  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---

Comment (by arma):

 See also #26311 for what might be a related 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] #26255 [Internal Services/Service - git]: Please make sbws git repo for pastly

2018-06-05 Thread Tor Bug Tracker & Wiki

#26255: Please make sbws git repo for pastly
-+-
 Reporter:  arma |  Owner:  tor-gitadm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by GreenPeace):

 sbws

--
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] #26255 [Internal Services/Service - git]: Please make sbws git repo for pastly

2018-06-05 Thread Tor Bug Tracker & Wiki

#26255: Please make sbws git repo for pastly
-+-
 Reporter:  arma |  Owner:  tor-gitadm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * status:  reopened => closed
 * resolution:   => 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

Re: [tor-bugs] #26310 [Core Tor/Tor]: Refusing to apply consensus diff because the base consensus doesn't match the digest as found in the consensus diff header.

2018-06-05 Thread Tor Bug Tracker & Wiki

#26310: Refusing to apply consensus diff because the base consensus doesn't 
match
the digest as found in the consensus diff header.
--+--
 Reporter:  Logforme  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by arma):

 * reporter:  cypherpunks => Logforme


--
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] #26310 [Core Tor/Tor]: Refusing to apply consensus diff because the base consensus doesn't match the digest as found in the consensus diff header.

2018-06-05 Thread Tor Bug Tracker & Wiki

#26310: Refusing to apply consensus diff because the base consensus doesn't 
match
the digest as found in the consensus diff header.
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 Hm! (128.31.0.34 is me!)

 I was going to wonder if maybe moria1 has old libraries so it is
 generating consensus diffs that other relays don't like to apply.

 But your last comment is interesting too, in that it sounds like your
 relay is having trouble staying up to date with its consensus documents in
 general. I wonder why.

 Do you have any other interesting log messages?

--
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] #26313 [Community/Relays]: Recommend exits to use Cloudflare's Onion Service for their DNS resolver (1.1.1.1)?

2018-06-05 Thread Tor Bug Tracker & Wiki

#26313: Recommend exits to use Cloudflare's Onion Service for their DNS resolver
(1.1.1.1)?
--+---
 Reporter:  cypherpunks   |  Owner:  Nusenu
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Community/Relays  |Version:
 Severity:  Normal| Resolution:  not a bug
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by cypherpunks):

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


Comment:

 this is primarily supposed to be used by tor clients not by relays, so the
 relay guide would be the wrong place for 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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "25693-TorBrowser UI.png" 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] #26255 [Internal Services/Service - git]: Please make sbws git repo for pastly

2018-06-05 Thread Tor Bug Tracker & Wiki

#26255: Please make sbws git repo for pastly
-+
 Reporter:  arma |  Owner:  tor-gitadm
 Type:  task | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by hiro):

 * status:  closed => reopened
 * resolution:  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

Re: [tor-bugs] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "25693-TorBrowser Icon.png" 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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "25693-TorBrowser Installer.png" 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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "25693-TorBrowser Icon.png" removed.


--
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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "25693-TorBrowser UI.png" 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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "25693-TorBrowser Installer.png" 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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

2018-06-05 Thread Tor Bug Tracker & Wiki

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "25693-TorBrowser Icon.png" 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] #26309 [- Select a component]: Lost previous tabs when updated to 7.5.4

2018-06-05 Thread Tor Bug Tracker & Wiki

#26309: Lost previous tabs when updated to 7.5.4
--+
 Reporter:  artemik   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by artemik):

 My tabs are back. But it's weird. Because:
 1. I decided, since I can never restore my tabs back, I opened new ones.
 2. Finished working, closed the browser.
 3. Opened the browser again, it restored the tabs I opened at step 1.
 4. Again, finished working, closed the browser.
 5. Open the browser, and now it restored not the tabs from step 1, but
 those that I lost when updated to the new versions. I'm actually happy
 with that, but still it's weird it hasn't restored the tabs that are
 really last session tabs, i.e. from step 1.

 Between all the steps several minutes passed. So it eliminates any RAM
 caching problem possibilities or browser not being able to exit
 completely.

--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 > rnuter
 'n' \x6E
 'o' \x6F <- valid
 > PUBMIC
 'L' \x4C <- valid
 'M' \x4D

 LSB flips
 Hardware 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

Re: [tor-bugs] #25957 [Core Tor/Tor]: Tor 0.3.3.5-rc died: Caught signal 11

2018-06-05 Thread Tor Bug Tracker & Wiki

#25957: Tor 0.3.3.5-rc died: Caught signal 11
+---
 Reporter:  Pine64ARMv8 |  Owner:  (none)
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:  Tor: 0.3.3.5-rc
 Severity:  Normal  | Resolution:
 Keywords:  crash, openssl  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
Description changed by arma:

Old description:

> from tor.log (tor server: devuan
> 8A00CE9638BDB4686B91F1F0B229DB3F8C9B8415):
> .../...
> Apr 28 00:58:53.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with
> 9698 circuits open. I've sent 556.38 GB and received 553.75 GB.
> Apr 28 00:58:53.000 [notice] Circuit handshake stats since last time:
> 21677/21677 TAP, 252349/252349 NTor.
> Apr 28 00:58:53.000 [notice] Since startup, we have initiated 0 v1
> connections, 0 v2 connections, 1 v3 connections, and 16330 v4
> connections; and received 36 v1 connections, 8546 v2 connections, 13955
> v3 connections, and 12846 v4 connections.
> Apr 28 00:58:53.000 [notice] DoS mitigation since startup: 0 circuits
> rejected, 0 marked addresses. 0 connections closed. 294 single hop
> clients refused.
>
>  T=
> 1524879769
> Tor 0.3.3.5-rc died: Caught signal 11
> tor(+0x189059)[0x558d01f7c059]
> /lib/x86_64-linux-gnu/libc.so.6(+0x791d5)[0x7f201753e1d5]
> /lib/x86_64-linux-gnu/libc.so.6(+0x791d5)[0x7f201753e1d5]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f201753ff64]
> /usr/local/lib/libssl.so.1.1(+0x24f40)[0x7f2018ca4f40]
> /usr/local/lib/libssl.so.1.1(+0x24b25)[0x7f2018ca4b25]
> /usr/local/lib/libssl.so.1.1(+0x2baec)[0x7f2018cabaec]
> /usr/local/lib/libssl.so.1.1(+0x374d0)[0x7f2018cb74d0]
> /usr/local/lib/libssl.so.1.1(SSL_read+0x15)[0x7f2018cb76b5]
> tor(tor_tls_read+0x52)[0x558d01fae7a2]
> tor(buf_read_from_tls+0xac)[0x558d01fa01dc]
> tor(+0x10b9e1)[0x558d01efe9e1]
> tor(+0x5367e)[0x558d01e4667e]
> /usr/lib/x86_64-linux-
> gnu/libevent-2.0.so.5(event_base_loop+0x6a0)[0x7f2018f1f5a0]
> tor(do_main_loop+0x264)[0x558d01e47694]
> tor(tor_run_main+0x275)[0x558d01e48c95]
> tor(tor_main+0x3a)[0x558d01e422aa]
> tor(main+0x19)[0x558d01e42019]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f20174e52e1]
> tor(_start+0x2a)[0x558d01e4206a]

New description:

 from tor.log (tor server: devuan
 8A00CE9638BDB4686B91F1F0B229DB3F8C9B8415):
 .../...
 Apr 28 00:58:53.000 [notice] Heartbeat: Tor's uptime is 23:59 hours, with
 9698 circuits open. I've sent 556.38 GB and received 553.75 GB.
 Apr 28 00:58:53.000 [notice] Circuit handshake stats since last time:
 21677/21677 TAP, 252349/252349 NTor.
 Apr 28 00:58:53.000 [notice] Since startup, we have initiated 0 v1
 connections, 0 v2 connections, 1 v3 connections, and 16330 v4 connections;
 and received 36 v1 connections, 8546 v2 connections, 13955 v3 connections,
 and 12846 v4 connections.
 Apr 28 00:58:53.000 [notice] DoS mitigation since startup: 0 circuits
 rejected, 0 marked addresses. 0 connections closed. 294 single hop clients
 refused.

 {{{
  T= 1524879769
 Tor 0.3.3.5-rc died: Caught signal 11
 tor(+0x189059)[0x558d01f7c059]
 /lib/x86_64-linux-gnu/libc.so.6(+0x791d5)[0x7f201753e1d5]
 /lib/x86_64-linux-gnu/libc.so.6(+0x791d5)[0x7f201753e1d5]
 /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7f201753ff64]
 /usr/local/lib/libssl.so.1.1(+0x24f40)[0x7f2018ca4f40]
 /usr/local/lib/libssl.so.1.1(+0x24b25)[0x7f2018ca4b25]
 /usr/local/lib/libssl.so.1.1(+0x2baec)[0x7f2018cabaec]
 /usr/local/lib/libssl.so.1.1(+0x374d0)[0x7f2018cb74d0]
 /usr/local/lib/libssl.so.1.1(SSL_read+0x15)[0x7f2018cb76b5]
 tor(tor_tls_read+0x52)[0x558d01fae7a2]
 tor(buf_read_from_tls+0xac)[0x558d01fa01dc]
 tor(+0x10b9e1)[0x558d01efe9e1]
 tor(+0x5367e)[0x558d01e4667e]
 /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x6a0)[0x7f2018f1f5a0]
 tor(do_main_loop+0x264)[0x558d01e47694]
 tor(tor_run_main+0x275)[0x558d01e48c95]
 tor(tor_main+0x3a)[0x558d01e422aa]
 tor(main+0x19)[0x558d01e42019]
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f20174e52e1]
 tor(_start+0x2a)[0x558d01e4206a]
 }}}

--

--
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] #26255 [Internal Services/Service - git]: Please make sbws git repo for pastly

2018-06-05 Thread Tor Bug Tracker & Wiki

#26255: Please make sbws git repo for pastly
-+-
 Reporter:  arma |  Owner:  tor-gitadm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * status:  new => closed
 * resolution:   => 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

Re: [tor-bugs] #26197 [Internal Services/Service - git]: Sync git.torproject.org/stem.git to github.com/torproject/stem.git

2018-06-05 Thread Tor Bug Tracker & Wiki

#26197: Sync git.torproject.org/stem.git to github.com/torproject/stem.git
-+
 Reporter:  teor |  Owner:  tor-gitadm
 Type:  task | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by arma):

 What still needs to be done here?

 I ask because it seems easy for the github people to say "I dunno, the
 git.tpo folks need to take the next step" and for the git.tpo folks to say
 the opposite.

 In particular, isis's comment above seems to imply that git.tpo needs to
 enable some mirroring thing?

 But hiro just now said that without github permissions, there's nothing to
 do on the git.tpo side yet.

--
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] #26196 [Core Tor/Tor]: Abort in test_bridges.c

2018-06-05 Thread Tor Bug Tracker & Wiki

#26196: Abort in test_bridges.c
-+-
 Reporter:  gvanem   |  Owner:  rl1987
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  crash, tests, 029-backport,  |  Actual Points:
  031-backport 032-backport 033-backport |
  034-backport fast-fix  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gvanem):

 Replying to [comment:6 rl1987]:

 > Now that `DEBUG_SMARTLIST` is enabled when fragile hardening is on,
 there are more places in
 > the codebase where we're using smartlist in a way that's not exactly
 right:

 Your patch to {{{test/tor_bridges.c}}} do indeed fix my original
 assertion. But as you've discovered, new {{{assert()}}} have surfaced.
 I'll leave that to you to 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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 > The file Reboot_Tor contain a more detail log.

 > Jun 04 01:33:20 mkuktra Tor[28659]: descriptor at 0x564bc61006b0 begins
 with unexpected string "rnuter N0nam3 78.120.51.57 30556 0 30555
 \nidentity-ed25519\n-B".  Is anothe

 > Jun 04 01:33:42 mkuktra Tor[14966]: parse error: Malformed object:
 mismatched end tag RSA PUBMIC KEY
 > Jun 04 01:33:42 mkuktra Tor[14966]: Error tokenizing router descriptor.
 > Jun 04 01:33:58 mkuktra Tor[14966]: parse error: Malformed object:
 mismatched end tag RSA PUBLIC KEY
 > Jun 04 01:33:58 mkuktra Tor[14966]: Error tokenizing router descriptor.
 > Jun 04 01:33:58 mkuktra Tor[14966]: couldn't find start of hashed
 material "router "
 > Jun 04 01:33:58 mkuktra Tor[14966]: No router keyword found.

--
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] #26313 [Community/Relays]: Recommend exits to use Cloudflare's Onion Service for their DNS resolver (1.1.1.1)?

2018-06-05 Thread Tor Bug Tracker & Wiki

#26313: Recommend exits to use Cloudflare's Onion Service for their DNS resolver
(1.1.1.1)?
--+
 Reporter:  cypherpunks   |  Owner:  Nusenu
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Relays  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 Still not sure if this is a good idea. Maybe it's a bad idea actually
 (Cloudflare gets to record all DNS requests made through Tor--very
 valuable 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] #26313 [Community/Relays]: Recommend exits to use Cloudflare's Onion Service for their DNS resolver (1.1.1.1)?

2018-06-05 Thread Tor Bug Tracker & Wiki

#26313: Recommend exits to use Cloudflare's Onion Service for their DNS resolver
(1.1.1.1)?
--+
 Reporter:  cypherpunks   |  Owner:  Nusenu
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Relays  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 `https://dns4torpnlfs2ifuz2s2yf3fc7rdmsbhm6rw75euj35pac6ap25zgqad.onion`

--
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] #26313 [Community/Relays]: Recommend exits to use Cloudflare's Onion Service for their DNS resolver (1.1.1.1)?

2018-06-05 Thread Tor Bug Tracker & Wiki

#26313: Recommend exits to use Cloudflare's Onion Service for their DNS resolver
(1.1.1.1)?
--+
 Reporter:  cypherpunks   |  Owner:  Nusenu
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Relays  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 https://blog.cloudflare.com/welcome-hidden-resolver/

--
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] #25909 [Applications/Tor Browser]: disable updater telemetry

2018-06-05 Thread Tor Bug Tracker & Wiki

#25909: disable updater telemetry
+--
 Reporter:  mcs |  Owner:  tbb-team
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  ff60-esr, TorBrowserTeam201805  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by mcs):

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


Comment:

 I created https://bugzilla.mozilla.org/show_bug.cgi?id=1466857 to track
 this on the Mozilla side.

--
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] #25386 [Core Tor/Tor]: Link Rust Tests to C Dependencies in Tor (allow integration testing from Rust to C)

2018-06-05 Thread Tor Bug Tracker & Wiki

#25386: Link Rust Tests to C Dependencies in Tor (allow integration testing from
Rust to C)
-+-
 Reporter:  Hello71  |  Owner:  Hello71
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-test, 033-backport,|  Actual Points:
  review-group-34, 034-triage-20180328,  |
  034-included-20180401  |
Parent ID:   | Points:  3
 Reviewer:  isis |Sponsor:
 |  SponsorQ
-+-
Changes (by Hello71):

 * status:  needs_revision => new


Comment:

 for sanitizers, whoever works on it, it may or may not help to pass gcc
 `-static-libasan -static-libubsan`. try that if you have issues.

 I'm too frustrated dealing with this, so someone else can deal with 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

Re: [tor-bugs] #26312 [Applications/Tor Browser]: Tor Browser silently fails to start if gtk2 is not installed

2018-06-05 Thread Tor Bug Tracker & Wiki

#26312: Tor Browser silently fails to start if gtk2 is not installed
--+--
 Reporter:  Hello71   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Hello71):

 heh, I copied that and then forgot to actually paste it.

 XPCOMGlueLoad error for file [snip]/Browser/libxul.so:
 libgtk-x11-2.0.so.0: cannot open shared object file: No such file or
 directory
 Couldn't load XPCOM.

--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by pascal.levasseur):

 I have moved to 0.3.4.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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by pascal.levasseur):

 The file Reboot_Tor contain a more detail log.

--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by pascal.levasseur):

 * Attachment "Reboot_Tor" added.

 Detail Tor log

--
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] #26310 [Core Tor/Tor]: Refusing to apply consensus diff because the base consensus doesn't match the digest as found in the consensus diff header.

2018-06-05 Thread Tor Bug Tracker & Wiki

#26310: Refusing to apply consensus diff because the base consensus doesn't 
match
the digest as found in the consensus diff header.
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Logforme):

 After another round of "refusing to apply ..." messages in the log file
 this appeared:
 {{{
 Jun 05 14:00:02.000 [warn] Our microdesc consensus is too old, so we will
 not serve it to clients. It was valid until 2018-06-04 14:00:00 local time
 and we continued to serve it for up to 24 hours after it expired.
 Jun 05 14:00:46.000 [notice] Our directory information is no longer up-to-
 date enough to build circuits: We have no recent usable consensus.
 Jun 05 14:17:24.000 [notice] We now have enough directory information to
 build circuits.
 }}}

--
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] #26312 [Applications/Tor Browser]: Tor Browser silently fails to start if gtk2 is not installed

2018-06-05 Thread Tor Bug Tracker & Wiki

#26312: Tor Browser silently fails to start if gtk2 is not installed
--+--
 Reporter:  Hello71   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 What is the output of `./Browser/start-tor-browser --verbose`?

--
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] #26312 [Applications/Tor Browser]: Tor Browser silently fails to start if gtk2 is not installed

2018-06-05 Thread Tor Bug Tracker & Wiki

#26312: Tor Browser silently fails to start if gtk2 is not installed
--+--
 Reporter:  Hello71   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 more annoyingly, this issue can only be diagnosed by running `Browser
 /start-tor-browser --verbose`. `./start-tor-browser.desktop` and `Browser
 /start-tor-browser` simply output nothing.

 I downloaded stock Firefox ESR 52.8.0 and ran it with `-P
 non_default_profile -no-remote` and it started with no issues. it comes
 with both "libmozgtk.so" and "gtk2/libmozgtk.so" which I assume helps.

--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 > Both serving DirPort
 IPv6 OrPort too

--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 Both serving DirPort

 > Zlib 1.2.8
 What about libs for lzma, zstd, .. ?

--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 the heap corruption is out there
 #25957

--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by cypherpunks):

 * version:  Tor: 0.3.3.6 => Tor: 0.3.3.5-rc


--
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] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

2018-06-05 Thread Tor Bug Tracker & Wiki

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x55ed468598d0
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 https://lists.torproject.org/pipermail/tor-relays/2018-June/015353.html

 "
 My very stable Tor relay 16102E458460349EE45C0901DAA6C30094A9BBEA is now
 rebooting every two days since May 31, 2018.

 Running Tor 0.3.3.5-rc (git-4fe9670741478750) on Linux
  with Libevent 2.0.21-stable, OpenSSL 1.1.0f, Zlib 1.2.8

 You will find a short extract of the Tor log below :

 May 31 23:12:27 mkuktra systemd[1]: tor@default.service: Main process
 exited, code=killed, status=7/BUS
 May 31 23:12:27 mkuktra systemd[1]: tor@default.service: Unit entered
 failed state.
 May 31 23:12:27 mkuktra systemd[1]: tor@default.service: Failed with
 result 'signal'.
 May 31 23:12:28 mkuktra systemd[1]: tor@default.service: Service
 hold-off time over, scheduling restart.

 Jun 05 03:17:59 mkuktra tor[23419]: *** Error in `/usr/bin/tor': free():
 invalid next size (normal): 0x55ed468598d0 ***
 Jun 05 03:17:59 mkuktra tor[23419]: === Backtrace: =
 Jun 05 03:17:59 mkuktra tor[23419]:
 /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fbb01af9bfb]
 Jun 05 03:17:59 mkuktra tor[23419]:
 /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fbb01afffc6]
 "


 trac search found also #15776

--
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] #26222 [Core Tor/Tor]: Add a bandwidth-file line to votes in dir-spec.txt

2018-06-05 Thread Tor Bug Tracker & Wiki

#26222: Add a bandwidth-file line to votes in dir-spec.txt
--+
 Reporter:  teor  |  Owner:  juga
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-spec, tor-bwauth  |  Actual Points:
Parent ID:  #3723 | Points:
 Reviewer:|Sponsor:
--+
Changes (by juga):

 * keywords:  tor-spec, tor-dirauth => tor-spec, tor-bwauth


--
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] #3723 [Core Tor/Tor]: Report version of bwscanners in votes

2018-06-05 Thread Tor Bug Tracker & Wiki

#3723: Report version of bwscanners in votes
--+
 Reporter:  mikeperry |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-bwauth|  Actual Points:
Parent ID:  #25925| Points:
 Reviewer:|Sponsor:
--+
Changes (by juga):

 * keywords:  tor-dirauth => tor-bwauth


--
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] #25960 [Core Tor/Tor]: Allow additional header lines in bandwidth measurements documents

2018-06-05 Thread Tor Bug Tracker & Wiki

#25960: Allow additional header lines in bandwidth measurements documents
-+-
 Reporter:  juga |  Owner:  juga
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  035-proposed, bwauth, 034-backport,  |  Actual Points:
  029-backport, 031-backport, 032-backport,  |
  033-backport, tor-bwauth   |
Parent ID:  #25925   | Points:
 Reviewer:  asn  |Sponsor:
-+-
Changes (by juga):

 * keywords:
 035-proposed, bwauth, 034-backport, 029-backport, 031-backport,
 032-backport, 033-backport
 =>
 035-proposed, bwauth, 034-backport, 029-backport, 031-backport,
 032-backport, 033-backport, tor-bwauth


--
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] #25947 [Core Tor/Tor]: Create unit test for dirserv_read_measured_bandwidths

2018-06-05 Thread Tor Bug Tracker & Wiki

#25947: Create unit test for dirserv_read_measured_bandwidths
--+
 Reporter:  juga  |  Owner:  juga
 Type:  enhancement   | Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  bwauth, test, tor-bwauth  |  Actual Points:
Parent ID:  #25925| Points:
 Reviewer:  asn   |Sponsor:
--+
Changes (by juga):

 * keywords:  bwauth, test => bwauth, test, tor-bwauth


--
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] #26004 [Core Tor/Tor]: Allow Tor to accept node_id at the end of a bandwidth file line

2018-06-05 Thread Tor Bug Tracker & Wiki

#26004: Allow Tor to accept node_id at the end of a bandwidth file line
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  fast-fix, 034-backport-maybe, 033|  Actual Points:
  -backport-maybe, 032-backport-maybe, 031   |
  -backport-maybe, 029-backport-maybe, tor-  |
  bwauth |
Parent ID:  #25925   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by juga):

 * keywords:
 fast-fix, 034-backport-maybe, 033-backport-maybe, 032-backport-maybe,
 031-backport-maybe, 029-backport-maybe, tor-dirauth
 =>
 fast-fix, 034-backport-maybe, 033-backport-maybe, 032-backport-maybe,
 031-backport-maybe, 029-backport-maybe, tor-bwauth


--
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] #26200 [Core Tor/Tor]: Bandwidth List format specification: add KeyValues counting errors in Bandwidth Lines

2018-06-05 Thread Tor Bug Tracker & Wiki

#26200: Bandwidth List format specification: add KeyValues counting errors in
Bandwidth Lines
-+-
 Reporter:  juga |  Owner:  (none)
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, bwauth, specification,   |  Actual Points:
  tor-spec   |
Parent ID:  #25925   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by juga):

 * keywords:  tor-dirauth, bwauth, specification, tor-spec => tor-bwauth,
 bwauth, specification, tor-spec


--
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] #22453 [Core Tor/Tor]: Relays should regularly do a larger bandwidth self-test

2018-06-05 Thread Tor Bug Tracker & Wiki

#22453: Relays should regularly do a larger bandwidth self-test
-+-
 Reporter:  arma |  Owner:  juga
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:
  034-removed-20180328, tor-bwauth   |
Parent ID:  #25925   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by juga):

 Diving into the code i found that the function where the relay bandwidth
 is compared with `options->AuthDirGuardBWGuarantee` is in
 `set_routerstatus_from_routerinfo` [0].

 To obtain the relay bandwidth, that function calls
 `dirserv_get_credible_bandwidth_kb` [1] which seems to be using either the
 measured bandwidth (by bwauths) or the self advertised bandwidth, but not
 any self measured bandwidth.

 If i understand it correctly, the self measured bandwidth
 (`bandwidthcapacity`) is obtained by `rep_hist_bandwidth_assess` [2].

 The function that is making use of the circuits to test the bandwidth is
 `router_perform_bandwidth_test` [3] but i don't see how it is storing the
 results or how is related with the previous.

 So, should `dirserv_get_credible_bandwidth_kb` make use of the bandwidth
 calculated by self tests?, which are the self tests here to be used?

 Where in the code should go the `times out after 30-60`?, and the `12-24
 hours, at random`?

 [0] https://gitweb.torproject.org/tor.git/tree/src/or/dirserv.c#n2058
 [1] https://gitweb.torproject.org/tor.git/tree/src/or/dirserv.c#n1780
 [2] https://gitweb.torproject.org/tor.git/tree/src/or/rephist.c#n1207
 [3] https://gitweb.torproject.org/tor.git/tree/src/or/router.c#n1626

--
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] #26310 [Core Tor/Tor]: Refusing to apply consensus diff because the base consensus doesn't match the digest as found in the consensus diff header.

2018-06-05 Thread Tor Bug Tracker & Wiki

#26310: Refusing to apply consensus diff because the base consensus doesn't 
match
the digest as found in the consensus diff header.
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 from: https://lists.torproject.org/pipermail/tor-
 relays/2018-June/015352.html

 "
 I run the non-exit relay 855BC2DABE24C861CD887DB9B2E950424B49FC34

 Two days now I've seen this in my log file:

 Jun 05 06:25:02.000 [warn] Refusing to apply consensus diff because the
 base consensus doesn't match the digest as found in the consensus diff
 header.
 Jun 05 06:25:02.000 [warn] Expected:
 2E3DACFB12051F4A45F7F4DC062F6D47DC75DBA85EB72F8E5D43DF134940F2DA; found:
 1573CFF458492B70BFDD4E91A594521C4DDD801B11936B8C148BF27F67736713
 Jun 05 06:25:02.000 [warn] Could not apply consensus diff received from
 server '128.31.0.34:9131'

 (Repeated for 204.13.164.118, 131.188.40.189, 154.35.175.225,
 194.109.206.212, 171.25.193.9, 199.58.81.140)

 First time I assumed it was just a glitch. Now I'm wondering if there is
 something I should do on my side?
 "

--
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] #26192 [Internal Services/Service - git]: Grant tommyc access to tor-browser/user-manual git

2018-06-05 Thread Tor Bug Tracker & Wiki

#26192: Grant tommyc access to tor-browser/user-manual git
-+-
 Reporter:  phoul|  Owner:  tor-gitadm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * status:  new => closed
 * resolution:   => 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

Re: [tor-bugs] #22453 [Core Tor/Tor]: Relays should regularly do a larger bandwidth self-test

2018-06-05 Thread Tor Bug Tracker & Wiki

#22453: Relays should regularly do a larger bandwidth self-test
-+-
 Reporter:  arma |  Owner:  juga
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:
  034-removed-20180328, tor-bwauth   |
Parent ID:  #25925   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by juga):

 * cc: juga (removed)
 * owner:  (none) => juga
 * status:  new => assigned
 * keywords:  034-triage-20180328, 034-removed-20180328 =>
 034-triage-20180328, 034-removed-20180328, tor-bwauth


--
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] #26309 [- Select a component]: Lost previous tabs when updated to 7.5.4

2018-06-05 Thread Tor Bug Tracker & Wiki

#26309: Lost previous tabs when updated to 7.5.4
--+
 Reporter:  artemik   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by artemik):

 Correction - the setting is there, I managed to revert it back.
 But the tabs are gone anyway, and the setting shouldn't have reset to the
 default, it should've been the one I had before, i.e. keep history and
 tabs.

--
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] #26309 [- Select a component]: Lost previous tabs when updated to 7.5.4

2018-06-05 Thread Tor Bug Tracker & Wiki

#26309: Lost previous tabs when updated to 7.5.4
--+
 Reporter:  artemik   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 In my previous Tor version (don't know what it was), I set Tor to open
 tabs from previous session on startup, keep history, etc.

 Today I've updated to Tor 7.5.4. All my tabs, the history **are gone**.
 The setting isn't available anymore.

 Why didn't I get **ANY** warning on such destructive behavior?

 I know, privacy and all that stuff, but you shouldn't limit the users.
 Make it the default and allow customization. But anyway, you should at
 least notify about it. I don't use the browser for "dark" stuff - I use it
 just as something that allows me to open websites not available in my
 country.

 Now I lost all my tabs. How am I supposed to restore them?

--
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] #26305 [Core Tor/Tor]: Can not set up a hidden service on Windows 10

2018-06-05 Thread Tor Bug Tracker & Wiki

#26305: Can not set up a hidden service on Windows 10
-+
 Reporter:  teruterubouzu1024@…  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by gk):

 * component:  - Select a component => Core Tor/Tor


--
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] #26306 [Core Tor/Tor]: HTTPS proxy doesn't use TLS

2018-06-05 Thread Tor Bug Tracker & Wiki

#26306: HTTPS proxy doesn't use TLS
--+--
 Reporter:  sf|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.6
 Severity:  Major | Resolution:
 Keywords:  https, proxy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * component:  - Select a component => Core Tor/Tor


Comment:

 (Guessing Core/Tor for 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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #22176, #26045, #18925, #20254, ...

2018-06-05 Thread Tor Bug Tracker & Wiki

Batch modification to #22176, #26045, #18925, #20254, #20648, #22451, #24622, 
#25030 by gk:


Comment:
Moving my tickets to June 2018.

--
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] #2846 [Archived/general]: Patch GPG to support SOCKS proxies

2018-06-05 Thread Tor Bug Tracker & Wiki

#2846: Patch GPG to support SOCKS proxies
--+---
 Reporter:  rransom   |  Owner:  mikeperry
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Archived/general  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by irl):

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


Comment:

 I agree with cypherpunks in comment:52, plus no other activity for 3
 years.

--
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] #5994 [Archived/Ponies]: Acquire torproject.secure

2018-06-05 Thread Tor Bug Tracker & Wiki

#5994: Acquire torproject.secure
-+-
 Reporter:  phobos   |  Owner:  (none)
 Type:  project  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Archived/Ponies  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by irl):

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


Comment:

 The http://nic.secure/ website has the following text:

 > Amazon Registry Services is excited to present .SECURE — a new TLD
 >
 > Information on the .SECURE space, registration policies, and launch
 dates will be forthcoming.

 The copyright date on that webpage is 2016 with no indication the page has
 seen updates since.

 Wikipedia has no further information on this TLD.

 https://www.amazonregistry.com/ does not mention .secure at all.

 I am closing this ticket, as the goal of it is currently unachievable.
 There are probably many gTLDs that Tor would fit into, but we don't need
 to collect them all.

--
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] #26256 [Internal Services/Tor Sysadmin Team]: New PGP key for isabela

2018-06-05 Thread Tor Bug Tracker & Wiki

#26256: New PGP key for isabela
-+
 Reporter:  dgoulet  |  Owner:  tpa
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by weasel):

 * 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

77 matches

Mail list logo