Re: [tor-bugs] #24284 [Obfuscation/meek]: meek-amazon does not work

[Tor Bug Tracker & Wiki]

#24284: meek-amazon does not work
--+-
 Reporter:  cypherpunks   |  Owner:  dcf
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by dcf):

 It looks like a problem with the backing bridge. I'll look into 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] #24287 [Metrics/Consensus Health]: Add a "votes for IPv6 ORPorts" flag to authorities in consensus health summary

[Tor Bug Tracker & Wiki]

#24287: Add a "votes for IPv6 ORPorts" flag to authorities in consensus health
summary
--+-
 Reporter:  teor  |  Owner:  tom
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Consensus Health  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by tom):

 Should be easy to add, once I figure out how to detect it. How is it
 exposed in the vote? Is there any flag or anything I can look for or do i
 just need to look for a relay that has a v6 port?

--
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] #24289 [Core Tor/Nyx]: When I go to https://nyx.torproject.org/changelog and click on "git repository" nothing happens.

[Tor Bug Tracker & Wiki]

#24289: When I go to https://nyx.torproject.org/changelog and click on "git
repository" nothing happens.
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Nyx   |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 When I go to https://nyx.torproject.org/changelog/index.html and click on
 "git repository" nothing happens.


 The following are only available within Nyx's''' git repository'''.

--
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] #24284 [Obfuscation/meek]: meek-amazon does not work

[Tor Bug Tracker & Wiki]

#24284: meek-amazon does not work
--+-
 Reporter:  cypherpunks   |  Owner:  dcf
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by Dbryrtfbcbhgf):

 * owner:  (none) => dcf
 * component:  - Select a component => Obfuscation/meek


Comment:

 I also can not use the built in meek-amazon in TBB 7.0.10

 11/14/17, 16:20:29.400 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 11/14/17, 16:20:29.400 [NOTICE] Switching to guard context "bridges" (was
 using "default")
 11/14/17, 16:20:29.400 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 11/14/17, 16:20:29.400 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 11/14/17, 16:20:29.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 11/14/17, 16:20:29.400 [NOTICE] Renaming old configuration file to
 "/Users/jackimoore/Desktop/tor/TorBrowser-Data/Tor/torrc.orig.1"
 11/14/17, 16:20:31.500 [NOTICE] Bootstrapped 5%: Connecting to directory
 server
 11/14/17, 16:20:31.500 [NOTICE] Bootstrapped 10%: Finishing handshake with
 directory server
 11/14/17, 16:21:19.600 [NOTICE] Closing no-longer-configured Socks
 listener on 127.0.0.1:9150
 11/14/17, 16:21:19.600 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 11/14/17, 16:21:19.600 [NOTICE] Closing old Socks listener on
 127.0.0.1:9150
 11/14/17, 16:21:19.600 [WARN] Problem bootstrapping. Stuck at 10%:
 Finishing handshake with directory server. (DONE; DONE; count 1;
 recommendation warn; host B9E7141C594AF25699E0079C1F0146F409495296 at
 0.0.2.0:2)
 11/14/17, 16:21:19.600 [WARN] 1 connections have failed:
 11/14/17, 16:21:19.600 [WARN]  1 connections died in state handshaking
 (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE

--
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] #24288 [Core Tor/Nyx]: install process does not include man page

[Tor Bug Tracker & Wiki]

#24288: install process does not include man page
---+
 Reporter:  stefani|  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Core Tor/Nyx   |Version:
 Severity:  Normal | Resolution:
 Keywords:  manual, configuration  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by atagar):

 Nyx used to. Gentoo wanted something different so I added a '--man-page'
 and '--sample-path' argument to our setup.py. But the custom installer
 caused problems for our latest release...

 https://gitweb.torproject.org/nyx.git/commit/?id=b89f6ca

 I'd be delighted to take a patch that adds them back. Now that we use
 setuptools rather than distutils it might not be so tricky.

 The reason the nyxrc.sample is in the web directory is so folks can
 download it from https://nyx.torproject.org/nyxrc.sample. We can add a
 symlink if you need it elsewhere.

--
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] #24288 [Core Tor/Nyx]: install process does not include man page

[Tor Bug Tracker & Wiki]

#24288: install process does not include man page
---+
 Reporter:  stefani|  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Core Tor/Nyx   |Version:
 Severity:  Normal | Resolution:
 Keywords:  manual, configuration  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by stefani):

 hola.
 I didn't think to look in the /web directory for a nyxrc file, so did not
 see your sample.
 I guess  a /doc  directory might have been more obvious to me. Same for
 the nyx.1 man page. and now that i think of it,  a   myxrc.8 man page

 i'm running on a barebones debian. no web browser there.
 question though:  if setup.py knew default well enough to put nyx in
 /usr/local/bin there must be other similar defaults for  man and doc and
 config examples;  /usr/local/etc/nyxrc

--
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] #24288 [Core Tor/Nyx]: install process does not include man page

[Tor Bug Tracker & Wiki]

#24288: install process does not include man page
---+
 Reporter:  stefani|  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Core Tor/Nyx   |Version:
 Severity:  Normal | Resolution:
 Keywords:  manual, configuration  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by atagar):

 Hi stefani. Nyx provides both a man page and nyxrc.sample [1], but
 installation of them depend on the platform package. Different distros
 differ on where these should go. As such it's up to the deb, rpm, bsd
 port, etc. What platform are you on?

 [1] https://gitweb.torproject.org/nyx.git/tree/web/nyxrc.sample

--
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] #24272 [Core Tor/Tor]: Add a CacheDirectory option

[Tor Bug Tracker & Wiki]

#24272: Add a CacheDirectory option
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, consensus-diff, tor-  |  duplicate
  mobile |  Actual Points:
Parent ID:  #22703   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

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


Comment:

 Closing as duplicate of #22703, which now has code for review

--
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] #22703 [Core Tor/Tor]: Add a KeyDirectory option to override location of $datadir/keys, and/or a cachedir option to override location of cached files.

[Tor Bug Tracker & Wiki]

#22703: Add a KeyDirectory option to override location of $datadir/keys, and/or 
a
cachedir option to override location of cached files.
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  sponsor8-maybe configuration torrc  |  Actual Points:  1
Parent ID:  #7176   | Points:  2
 Reviewer:  |Sponsor:
|  Sponsor8-can
+--
Changes (by nickm):

 * status:  accepted => needs_review


--
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] #22703 [Core Tor/Tor]: Add a KeyDirectory option to override location of $datadir/keys, and/or a cachedir option to override location of cached files.

[Tor Bug Tracker & Wiki]

#22703: Add a KeyDirectory option to override location of $datadir/keys, and/or 
a
cachedir option to override location of cached files.
+--
 Reporter:  nickm   |  Owner:  (none)
 Type:  enhancement | Status:
|  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  sponsor8-maybe configuration torrc  |  Actual Points:  1
Parent ID:  #7176   | Points:  2
 Reviewer:  |Sponsor:
|  Sponsor8-can
+--
Changes (by nickm):

 * status:  new => needs_review
 * actualpoints:   => 1


Comment:

 I've done an implementation of this in a `more_directories` 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

Re: [tor-bugs] #22703 [Core Tor/Tor]: Add a KeyDirectory option to override location of $datadir/keys, and/or a cachedir option to override location of cached files.

[Tor Bug Tracker & Wiki]

#22703: Add a KeyDirectory option to override location of $datadir/keys, and/or 
a
cachedir option to override location of cached files.
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:  accepted
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  sponsor8-maybe configuration torrc  |  Actual Points:  1
Parent ID:  #7176   | Points:  2
 Reviewer:  |Sponsor:
|  Sponsor8-can
+--
Changes (by nickm):

 * status:  needs_review => accepted
 * owner:  (none) => nickm


--
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] #24288 [Core Tor/Nyx]: install process does not include man page

[Tor Bug Tracker & Wiki]

#24288: install process does not include man page
---+
 Reporter:  stefani|  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Core Tor/Nyx   |Version:
 Severity:  Normal | Resolution:
 Keywords:  manual, configuration  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by stefani):

 added possible config file based on nyx  configuration 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] #24288 [Core Tor/Nyx]: install process does not include man page

[Tor Bug Tracker & Wiki]

#24288: install process does not include man page
---+
 Reporter:  stefani|  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Core Tor/Nyx   |Version:
 Severity:  Normal | Resolution:
 Keywords:  manual, configuration  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by stefani):

 * Attachment "config" added.

 possible nyx config file based on web page
 https://nyx.torproject.org/#configuration

--
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] #24288 [Core Tor/Nyx]: install process does not include man page

[Tor Bug Tracker & Wiki]

#24288: install process does not include man page
--+---
 Reporter:  stefani   |  Owner:  atagar
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:
 Severity:  Normal|   Keywords:  manual, configuration
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+---
 installation of nyx could place the nyx.1  man page in
 /usr/local/man/man1/ for example.
 optional would be a nyxrc example file with commented-out defaults

--
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] #23577 [Core Tor/Tor]: Add rendezvous point IPv6 address to client introduce cells

[Tor Bug Tracker & Wiki]

#23577: Add rendezvous point IPv6 address to client introduce cells
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:  2
  ipv6, review-group-25  |
Parent ID:  #23493   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
 |  SponsorV-can
-+-

Comment (by neel):

 I have a revised patch 009-bugfix-r1.patch. Keep in mind that I had to
 make {{{intro1_data}}} a pointer which I use {{{tor_malloc_zero()}}} on,
 and then free it at the {{{done:}}} statement.

--
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] #23577 [Core Tor/Tor]: Add rendezvous point IPv6 address to client introduce cells

[Tor Bug Tracker & Wiki]

#23577: Add rendezvous point IPv6 address to client introduce cells
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:  2
  ipv6, review-group-25  |
Parent ID:  #23493   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
 |  SponsorV-can
-+-
Changes (by neel):

 * Attachment "009-bugfix-r1.patch" added.

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

[tor-bugs] #24287 [Metrics/Consensus Health]: Add a "votes for IPv6 ORPorts" flag to authorities in consensus health summary

[Tor Bug Tracker & Wiki]

#24287: Add a "votes for IPv6 ORPorts" flag to authorities in consensus health
summary
--+-
 Reporter:  teor  |  Owner:  tom
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Consensus Health  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 We'd like to know which authorities vote for IPv6 addresses. It could be
 near or in the known flags table.

 We'd also like to know how many IPv6 addresses they are each voting for,
 like the existing Overlap between vote and consensus table. It could even
 be in that table.

--
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] #24268 [Core Tor/Tor]: Keep parts of data directory in /var/cache instead of /var/lib

[Tor Bug Tracker & Wiki]

#24268: Keep parts of data directory in /var/cache instead of /var/lib
--+
 Reporter:  Sebastian |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #22703| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * parent:  #24272 => #22703


Comment:

 Higher parent

--
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] #24272 [Core Tor/Tor]: Add a CacheDirectory option

[Tor Bug Tracker & Wiki]

#24272: Add a CacheDirectory option
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, consensus-diff, tor-  |  Actual Points:
  mobile |
Parent ID:  #22703   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm


--
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] #24174 [Metrics/ExoneraTor]: Use an embedded Jetty in ExoneraTor

[Tor Bug Tracker & Wiki]

#24174: Use an embedded Jetty in ExoneraTor
+-
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  enhancement | Status:  merge_ready
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-

Comment (by karsten):

 Merged! Also deployed the .jar, but held back deploying the .war until
 tomorrow.

--
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] #24286 [Webpages/Website]: Swap images on hidden services page

[Tor Bug Tracker & Wiki]

#24286: Swap images on hidden services page
--+--
 Reporter:  steph |  Owner:  k5
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #24285| Points:
 Reviewer:|Sponsor:
--+--
Changes (by steph):

 * Attachment "tor-onion-services-steps.zip" added.

 zip of 6 images

--
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] #24286 [Webpages/Website]: Swap images on hidden services page

[Tor Bug Tracker & Wiki]

#24286: Swap images on hidden services page
--+--
 Reporter:  steph |  Owner:  k5
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #24285
   Points:|   Reviewer:
  Sponsor:|
--+--
 Swap hidden services images with onion services images on
 https://www.torproject.org/docs/hidden-services

--
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] #21222 [Webpages/Website]: Main ticket for website redesign project

[Tor Bug Tracker & Wiki]

#21222: Main ticket for website redesign project
--+--
 Reporter:  isabela   |  Owner:  isabela
 Type:  project   | Status:  assigned
 Priority:  Very High |  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team,  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Description changed by isabela:

Old description:

> = Website redesign main ticket introduction =
>
> This is a huge project the UX team is leading and it has a lot of steps
> involved on it. Our goal is for this project to be the base of something
> that can scale while we continue to iterate on it.
>
> = What problems are we trying to fix? =
> This project aims to fix many problems that goes beyond just a redesign
> thing, even though we are calling it 'website redesign'.
>
> Yes, Tor Project website is not the best thing in the world and is a big
> problem that must be fixed. And this is a problem that we can't ignore
> anymore, is hurting many initiatives we have at Tor Project.
>
> Our community is growing and this growth is part of the 'website
> problem'. A lot of information have been added to torproject.org over the
> years leading to what we have now. Is a good problem to have, but right
> now we must reorganize this information to better set ourselves to
> continue grow.
>
> Here is a list of some problems easily recognizable with the current
> site:
>
>  * Not localized
>  * Too much information at the front page
>  * Still hard to find information
>  * Hard to add new information (ends up contributing to the mess) and we
> need to add more information because we are growing :) we have a lot to
> share
>  * inconsistency with the design
>
> And we could go on but the point of this doc is not to have a full
> description of all the problems we have but just an introduction to set
> the stage for explaining what we are thinking for a solution and the
> steps of its implementation.
>
> = How we solve it? =
> Our solution right now is to create new portals to better organize
> information and also at the same time keep torproject.org simple and easy
> for first comers to find their way around into what Tor is and how to
> get/use it.
>
> So we will be building:
>
>  * torproject.org - with 'new user' as our main audience for this portal
> [of course with easy way to navigate to the other portals:
>  * dev.torproject.org - short explanation: "all things related to the
> development of free software projects of Tor Project"
>  * community.torproject.org - short explanation: "a umbrella of things
> that are power by our community, or a portal to 'help people help Tor'.
>  * support.torproject.org - user support website
>
> Are we loosing press? FAQs? Donate page? The Blog? No :) the list above
> are the main entrance to all these things and more.
>
> I invite you to read more about each of this portal and other work
> related to this initiative in the children tickets (and their children
> tickets) associated with this project. Is a big project and the
> information written here is a summary of the summary ;)
>
> = Why now? =
> Right now we are with fund and a team to carry this work. And we need to
> do this to enable many other great work at Tor to have infrastructure to
> support their project. We believe that these portals will help a lot of
> groups inside of Tor Project to better provide information about their
> work and therefore receive help to do so.
>

> =  The short version of the process we will follow for each portal  =
>
> 0. content architecture - map current content related to the portal and
> organize it
>
> 1. whiteboard draw organization of the content into pages
>
> 2. wireframe these pages
>
> 3. create design for these pages [these include design reviews till we
> are happy with what we have]
> 4. [should we do a user test with it now? remember most content won't be
> there this is just draws not even html]
>[we can do a guerrilla user test with printed papers of our mocks]
>
> 5. start organizing content for the pages (with the design already done
> we will be working with that)
>
> 6. start coding the pages
>
> 7. once content is finished we upload them on transifex for translation
> to start
>
> 8. Once coding is done we can start QA by language (as translations get
> complete)
>
> 9. [we could do another user test here too before launch if we want - or
> we can run one after lunch and continue iteration]
>
> = What we will use to build it? =
> Right now we are testing Lektor for the framework to use:
> https://trac.torproject.org/projects/tor/ticket/24275
>
> We are also working on a project that will help us build the themes for
> these portals but also anyone else who would 

Re: [tor-bugs] #23577 [Core Tor/Tor]: Add rendezvous point IPv6 address to client introduce cells

[Tor Bug Tracker & Wiki]

#23577: Add rendezvous point IPv6 address to client introduce cells
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:  2
  ipv6, review-group-25  |
Parent ID:  #23493   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
 |  SponsorV-can
-+-

Comment (by neel):

 Would setting {{{intro1_data}}} to {{{0}}} in
 {{{hs_circ_send_introduce1()}}} be enough? I see that {{{intro1_data}}} is
 not a pointer variable, and it seems the expression 0} }}} is for a
 pointer or array.

 Replying to [comment:28 dgoulet]:
 > Replying to [comment:26 neel]:
 > > I have a patch which (hopefully) should resolve the two issues. The
 filename is 008-bugfix1.patch​.
 >
 > Thanks neel for the patch.
 >
 > Continuing on teor's review, I also would go with a pattern like this
 instead:
 >
 > {{{
 > if (exit_node == NULL) {
 >   log_info(...)
 >   goto done;
 > }
 > setup_intro1()
 > }}}
 >
 > The reason I think we should go with a `log_info()` instead of warning
 is because this is a very very rare race condition so if it occurs, no
 need for a warning because it is a possible "normal behavior" .
 >
 > The SOCKS connection will fail but at that point the application can
 retry and chances are that it will succeed.

--
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] #24277 [Metrics/Website]: header takes up too much space

[Tor Bug Tracker & Wiki]

#24277: header takes up too much space
-+--
 Reporter:  Hello71  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Minor| Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Agreed, the header occupies more space than necessary. You'll notice that
 that changes when you reduce the window height. Maybe we should use that
 header height for all window heights?

 Or do you want to create a quick mockup with those changes and make it
 available here for further discussion?

 By the way, we'll probably want to fully integrate Relay Search into Tor
 Metrics before making these changes, because right now we'd have to make
 them in two separate places. But that shouldn't stop us from planning
 improvements for after that integration.

--
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] #24285 [Webpages/Website]: Change "hidden services" to "onion services" on the website

[Tor Bug Tracker & Wiki]

#24285: Change "hidden services" to "onion services" on the website
--+--
 Reporter:  steph |  Owner:  kat5
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 - Change instances of hidden service(s) to onion service(s)

 - Indicate "formerly known as hidden services" in first instance on main
 page:

 Using Tor "rendezvous points," other Tor users can connect to these onion
 services, formerly known as hidden services, each without knowing the
 other's network identity. [https://www.torproject.org/docs/hidden-
 services]

 - Update and redirect URLS from hidden to 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

Re: [tor-bugs] #24272 [Core Tor/Tor]: Add a CacheDirectory option

[Tor Bug Tracker & Wiki]

#24272: Add a CacheDirectory option
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, consensus-diff, tor-  |  Actual Points:
  mobile |
Parent ID:  #22703   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * parent:   => #22703


--
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] #24230 [Core Tor/Tor]: control: HS_DESC event failed upload sends back the wrong Action

[Tor Bug Tracker & Wiki]

#24230: control: HS_DESC event failed upload sends back the wrong Action
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  easy, tor-control, tor-hs  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

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


Comment:

 ok. sounds persuasive. merging to maint-0.3.2

--
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] #24201 [Core Tor/Tor]: spec: ADD_ONION syntax is not reflecting the code

[Tor Bug Tracker & Wiki]

#24201: spec: ADD_ONION syntax is not reflecting the code
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  closed
 Priority:  Low   |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tor-spec, tor-hs  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 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] #24284 [- Select a component]: meek-amazon does not work

[Tor Bug Tracker & Wiki]

#24284: meek-amazon does not work
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+


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

Re: [tor-bugs] #21222 [Webpages/Website]: Main ticket for website redesign project

[Tor Bug Tracker & Wiki]

#21222: Main ticket for website redesign project
--+--
 Reporter:  isabela   |  Owner:  isabela
 Type:  project   | Status:  assigned
 Priority:  Very High |  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team,  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by isabela):

 * milestone:   => website redesign


--
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] #24279 [Core Tor/Tor]: configure libevent leaks

[Tor Bug Tracker & Wiki]

#24279: configure libevent leaks
--+
 Reporter:  Hello71   |  Owner:  Hello71
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:   => Tor: 0.3.2.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

[tor-bugs] #24283 [Webpages/Website]: create a index page for our styleguide.torproject.org (bootstrap fork)

[Tor Bug Tracker & Wiki]

#24283: create a index page for our styleguide.torproject.org (bootstrap fork)
--+--
 Reporter:  isabela   |  Owner:  isabela
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:  ux-team,
Actual Points:|  Parent ID:  #24280
   Points:|   Reviewer:  antonela, hiro
  Sponsor:|
--+--
 styleguide.torproject.org should have an index page explaining this
 project, how this resources should be used by anyone and how to use it.

 This page will continue to be updated as we make changes to our
 styleguide.

--
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] #24280 [Webpages/Website]: deploy styleguide.tpo (fork of bootstrap following tpo design styleguide)

[Tor Bug Tracker & Wiki]

#24280: deploy styleguide.tpo (fork of bootstrap following tpo design 
styleguide)
--+--
 Reporter:  isabela   |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team,  |  Actual Points:
Parent ID:  #21222| Points:
 Reviewer:|Sponsor:
--+--
Changes (by isabela):

 * milestone:   => website redesign


--
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] #24278 [Internal Services/Tor Sysadmin Team]: VMs to deploy static website at styleguide.tpo

[Tor Bug Tracker & Wiki]

#24278: VMs to deploy static website at styleguide.tpo
-+-
 Reporter:  hiro |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  website
 |  redesign
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #24280   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by isabela):

 * milestone:   => website redesign


--
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] #24282 [Metrics/Atlas]: Implement cache breaker

[Tor Bug Tracker & Wiki]

#24282: Implement cache breaker
---+--
 Reporter:  Sebastian  |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 I gave it an attempt in my repo at git.tpo/user/sebastian/atlas, branch
 cachebreaker

--
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] #24282 [Metrics/Atlas]: Implement cache breaker

[Tor Bug Tracker & Wiki]

#24282: Implement cache breaker
---+--
 Reporter:  Sebastian  |  Owner:  metrics-team
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by Sebastian):

 * status:  new => needs_review


--
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] #24281 [Webpages/Website]: Make css changes to styleguide as per designs

[Tor Bug Tracker & Wiki]

#24281: Make css changes to styleguide as per designs
--+--
 Reporter:  isabela   |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:  ux-team,
Actual Points:|  Parent ID:  #24280
   Points:|   Reviewer:  antonela
  Sponsor:|
--+--
 Here are all the screens done by Antonela for the styleguide.tpo:

 https://marvelapp.com/6c5ce44

--
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] #24278 [Internal Services/Tor Sysadmin Team]: VMs to deploy static website at styleguide.tpo

[Tor Bug Tracker & Wiki]

#24278: VMs to deploy static website at styleguide.tpo
-+-
 Reporter:  hiro |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #24280   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * parent:   => #24280


--
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] #24280 [Webpages/Website]: deploy styleguide.tpo (fork of bootstrap following tpo design styleguide)

[Tor Bug Tracker & Wiki]

#24280: deploy styleguide.tpo (fork of bootstrap following tpo design 
styleguide)
--+--
 Reporter:  isabela   |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:  ux-team,
Actual Points:|  Parent ID:  #21222
   Points:|   Reviewer:
  Sponsor:|
--+--
 == Background ==
 Back in 2015 The Tor Project partner with Simply Secure to create a design
 style guide for us.  Our goal was to bring brand consistency to everything
 Tor related.

 We presented a V2 of this project at Tor Meeting in Seattle (Q3 2016). And
 in 2017 we published a v3 of it with feedback received from the Tor
 Meeting incorporated to it:

 https://media.torproject.org/image/Tor%20Style%20Guide%20v1.3.pdf

 == What we are doing? ==

 We decided to apply these styles to http://getbootstrap.com/

 Here are some mocks of it:


 And build or own version of it that we plan to call:
 styleguide.torproject.org

 This page will have all bootstrap resources already converted to Tor
 styleguide. Together with other information that our styleguide has such
 as logo usage and so on.

 == Why? ==

 By having boostrap resourced already styled following Tor's design
 styleguide will be super handy for anyone building a site related to Tor.

 Specially for our website redesign, but for other projects from the
 community as 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] #24279 [Core Tor/Tor]: configure libevent leaks

[Tor Bug Tracker & Wiki]

#24279: configure libevent leaks
--+--
 Reporter:  Hello71   |  Owner:  Hello71
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by Hello71):

 * status:  assigned => needs_review


Comment:

 
https://cgit.alxu.ca/tor.git/commit/?id=50a98339b9c5e57acdc8355fa52509c9c1cd9497

--
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] #24279 [Core Tor/Tor]: configure libevent leaks

[Tor Bug Tracker & Wiki]

#24279: configure libevent leaks
--+--
 Reporter:  Hello71   |  Owner:  Hello71
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Minor |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 breaks build with "CFLAGS=-fsanitize=address". probably be better just to
 use pkg-config, but...

--
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] #24278 [Internal Services/Tor Sysadmin Team]: VMs to deploy static website at styleguide.tpo

[Tor Bug Tracker & Wiki]

#24278: VMs to deploy static website at styleguide.tpo
-+-
 Reporter:  hiro |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Hi,

 I need a VM to deploy a static website built using jekyll.

 I do not necessary need to build it on the same machine (meaning I can
 build it separately and sync only the static files), although it would be
 nice to have that option (it this case i will need ruby and ruby-build).

 This will need to be placed under the static content rotation.

 Please let me know if you have any other questions or is there anything I
 can help with.

--
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] #24276 [Metrics/Atlas]: Graphs can appear outside their boxes

[Tor Bug Tracker & Wiki]

#24276: Graphs can appear outside their boxes
---+
 Reporter:  irl|  Owner:  irl
 Type:  defect | Status:  closed
 Priority:  High   |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Graphs are now responsive. Fixed in
 9ee2b50672902bb699c235fc1bda59aace18ebb6.

--
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] #24041 [Metrics]: Add Apache Commons Configuration as configuration library

[Tor Bug Tracker & Wiki]

#24041: Add Apache Commons Configuration as configuration library
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Agreed, this is what I meant. No need to add another dependency if we can
 solve the problem with the JDK alone.

 irl, what was the reason that you switched to Apache Commons
 Configuration? What parts do you use that are harder or impossible to do
 with Java properties?

--
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] #24119 [Core Tor/Tor]: channel_rsa_id_group_set_badness spends a lot of time in malloc/free

[Tor Bug Tracker & Wiki]

#24119: channel_rsa_id_group_set_badness spends a lot of time in malloc/free
-+-
 Reporter:  Hello71  |  Owner:  Hello71
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  tor-channel, tor-sched,  |  Actual Points:
  032-backport, review-group-25  |
Parent ID:  #23777   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by Hello71):

 * status:  needs_revision => needs_review


--
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] #24277 [Metrics/Website]: header takes up too much space

[Tor Bug Tracker & Wiki]

#24277: header takes up too much space
-+--
 Reporter:  Hello71  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Minor|   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 including the two navigation bars plus the quote, but excluding the cookie
 bar, it occupies about 32% of my available screen space (compared to a web
 page displaying just text). I suggest that the quote be moved, preferably
 to the bottom, but floated to the top right of the content would work too,
 since usually this area is cleared by a short header. then, the logo could
 be moved to be in line with the top navigation bar. additionally, the
 bottom navigation bar could be moved to the left side of the screen,
 similar to the MediaWiki layout.

--
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] #24174 [Metrics/ExoneraTor]: Use an embedded Jetty in ExoneraTor

[Tor Bug Tracker & Wiki]

#24174: Use an embedded Jetty in ExoneraTor
+-
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  enhancement | Status:  merge_ready
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-
Changes (by karsten):

 * status:  needs_revision => merge_ready


Comment:

 Replying to [comment:15 iwakeh]:
 > Replying to [comment:14 karsten]:
 > > Looks good and works locally!
 >
 > Good, I assume all db access works fine now.
 >
 > > Some comments/questions:
 > >  - Can we use `metrics` and `password` as defaults in
 `src/main/resources/jetty.xml`? That should be as simple as writing
 `` and
 ``. Just in
 case somebody uses those defaults locally for testing, that is.
 >
 > That means, you want your private test environment configuration in
 development code ;-)

 Asking for a friend! ;)

 > I don't feel strongly about it.  Add them, if you like.  Just be aware
 that people looking at the code might think they discovered Tor's secret
 db credentials ;-)

 Well, without defaults, these are mandatory arguments, not options. I
 think it's fair to assume some default values, even if they are not what
 we'd use in a production environment.

 > But, actually, this is part of a bigger discussion cf. my comment to
 #24041 about 'unifying deployment configuration'.  Let's rather continue
 the configuration discussion there.

 Good idea!

 > >  - Is there a particular reason why you suggest bumping to 2.0.0 and
 not 1.1.0? For the Java 8 update we also made a minor version bump.
 Nothing backward-incompatible going on here, right?
 >
 > Isn't it a major change to move away from external tomcat?  The
 deployment changes completely.

 Alright. 2.0.0 it is.

 > >  - Out of curiousity, what's the full command line that you're using
 to start the JAR and the WAR file? Mine is pretty long, and I'm curious
 whether that's just for me or for everyone. Maybe we can start thinking
 about configuration libraries (#24041) after this ticket?
 >
 > Deployment example:
 > `java -Dexonerator.db.user=secretuser -Dexonerator.db.pw=secret -jar
 exonerator-1.0.0-dev.war`
 >
 > Test w/o db:
 > `java -Dexonerator.url=http://127.0.0.1:8080 -jar exonerator-dummy-
 test.war`
 >
 > I did comment on #24041 and I'm not in favor of long command lines (they
 are better than hard-coded parameters), but that's a different ticket.

 Thanks! Let's discuss this more on #24041.

 Alright, I'll add defaults and merge either tonight or tomorrow.

--
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] #12522 [Metrics/Website]: Add sitemap.xml to Globe to make details pages indexed by Google et al.

[Tor Bug Tracker & Wiki]

#12522: Add sitemap.xml to Globe to make details pages indexed by Google et al.
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:  #23518   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * component:  Metrics/Atlas => Metrics/Website


Comment:

 Ah, that would be a background process of metrics-web downloading
 Onionoo's summary document and updating a sitemap file? If so, sure,
 sounds doable. Moving to the Website component. (Feel free to undo, if I
 understood the idea 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] #23796 [Metrics/Onionoo]: Stop rejecting field queries due to capitalisation

[Tor Bug Tracker & Wiki]

#23796: Stop rejecting field queries due to capitalisation
-+--
 Reporter:  teor |  Owner:  metrics-team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 Okay, great, I'm closing this ticket then. 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] #23970 [Applications/Tor Browser]: Printing to a file is broken with Linux content sandboxing enabled

[Tor Bug Tracker & Wiki]

#23970: Printing to a file is broken with Linux content sandboxing enabled
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff59-esr-will-have, AffectsTails,|  Actual Points:
  tbb-regression, GeorgKoppen201711, |
  TorBrowserTeam201711   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 http://www.morbo.org/2017/11/linux-sandboxing-improvements-in.html

--
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] #24276 [Metrics/Atlas]: Graphs can appear outside their boxes

[Tor Bug Tracker & Wiki]

#24276: Graphs can appear outside their boxes
---+--
 Reporter:  irl|  Owner:  irl
 Type:  defect | Status:  accepted
 Priority:  High   |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

 * priority:  Medium => High
 * status:  new => accepted
 * owner:  metrics-team => irl


Comment:

 Somehow I completely missed this, even though it happens in Tor Browser at
 the default resolution.

--
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] #24276 [Metrics/Atlas]: Graphs can appear outside their boxes

[Tor Bug Tracker & Wiki]

#24276: Graphs can appear outside their boxes
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 This is an issue with the responsive design.

--
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] #23243 [Metrics/Website]: Write a specification for Tor web server logs

[Tor Bug Tracker & Wiki]

#23243: Write a specification for Tor web server logs
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  closed
 Priority:  High |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 Okay, great. Closing!

--
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] #23243 [Metrics/Website]: Write a specification for Tor web server logs

[Tor Bug Tracker & Wiki]

#23243: Write a specification for Tor web server logs
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  High |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Closing seems fine, if there are complaints, additions, corrections,
 extensions there should be a new ticket.
 Disclaimer: I provided the latest patch.

--
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] #8725 [Applications/Tor Browser]: resource:// URIs leak information

[Tor Bug Tracker & Wiki]

#8725: resource:// URIs leak information
-+-
 Reporter:  holizz   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:  fixed
 Keywords:  tbb-fingerprinting, tbb-rebase-  |  Actual Points:
  regression, tbb-testcase, tbb-firefox-patch,   |
  TorBrowserTeam201607R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 It has been fixed in Firefox 57
 https://bugzilla.mozilla.org/show_bug.cgi?id=863246

--
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] #24263 [Applications/Tor Browser]: Tor Browser 7.0.9 doesn't run background scripts from Web Extensions

[Tor Bug Tracker & Wiki]

#24263: Tor Browser 7.0.9 doesn't run background scripts from Web Extensions
--+--
 Reporter:  sajolida  |  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 sajolida):

 I tried with the version of our extension published on addons.mozilla.org
 and it works in Tor Browser 7.0.10, so as mcs implied, this is related to
 *local files* only, and Web Extensions seem to work fine when loaded from
 web stores.

 So for us, this is only a problem while developing the extension but not
 for our users → Good news!

--
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] #24269 [Core Tor/Tor]: Raise a FATAL error if the user tried to combine v2 and prop224 hidden service in same directory

[Tor Bug Tracker & Wiki]

#24269: Raise a FATAL error if the user tried to combine v2 and prop224 hidden
service in same directory
+
 Reporter:  cypherpunks |  Owner:  (none)
 Type:  task| Status:  reopened
 Priority:  Medium  |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs prop224  |  Actual Points:
Parent ID:  | Points:  0.3
 Reviewer:  |Sponsor:
+

Comment (by dgoulet):

 Oh we aren't sanitizing the input indeed. Do we have anything in tor to do
 that?

--
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] #24269 [Core Tor/Tor]: Raise a FATAL error if the user tried to combine v2 and prop224 hidden service in same directory

[Tor Bug Tracker & Wiki]

#24269: Raise a FATAL error if the user tried to combine v2 and prop224 hidden
service in same directory
+
 Reporter:  cypherpunks |  Owner:  (none)
 Type:  task| Status:  reopened
 Priority:  Medium  |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs prop224  |  Actual Points:
Parent ID:  | Points:  0.3
 Reviewer:  |Sponsor:
+
Changes (by nickm):

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


Comment:

 You can just specify the same directory in two different ways, I think:

 {{{
 HiddenServiceDir /path/abc
 HiddenServicePort 80
 HiddenServiceDir /path/abc/.
 HiddenServicePort 80
 }}

 Also, symlinks would let you do that.

--
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] #21222 [Webpages/Website]: Main ticket for website redesign project

[Tor Bug Tracker & Wiki]

#21222: Main ticket for website redesign project
--+--
 Reporter:  isabela   |  Owner:  isabela
 Type:  project   | Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team,  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Description changed by isabela:

Old description:

> = Website redesign main ticket introduction =
>
> This is a huge project the UX team is leading and it has a lot of steps
> involved on it. Our goal is for this project to be the base of something
> that can scale while we continue to iterate on it.
>
> = What problems are we trying to fix? =
> This project aims to fix many problems that goes beyond just a redesign
> thing, even though we are calling it 'website redesign'.
>
> Yes, Tor Project website is not the best thing in the world and is a big
> problem that must be fixed. And this is a problem that we can't ignore
> anymore, is hurting many initiatives we have at Tor Project.
>
> Our community is growing and this growth is part of the 'website
> problem'. A lot of information have been added to torproject.org over the
> years leading to what we have now. Is a good problem to have, but right
> now we must reorganize this information to better set ourselves to
> continue grow.
>
> Here is a list of some problems easily recognizable with the current
> site:
>
>  * Not localized
>  * Too much information at the front page
>  * Still hard to find information
>  * Hard to add new information (ends up contributing to the mess) and we
> need to add more information because we are growing :) we have a lot to
> share
>  * inconsistency with the design
>
> And we could go on but the point of this doc is not to have a full
> description of all the problems we have but just an introduction to set
> the stage for explaining what we are thinking for a solution and the
> steps of its implementation.
>
> = How we solve it? =
> Our solution right now is to create new portals to better organize
> information and also at the same time keep torproject.org simple and easy
> for first comers to find their way around into what Tor is and how to
> get/use it.
>
> So we will be building:
>
>  * torproject.org - with 'new user' as our main audience for this portal
> [of course with easy way to navigate to the other portals:
>  * dev.torproject.org - short explanation: "all things related to the
> development of free software projects of Tor Project"
>  * community.torproject.org - short explanation: "a umbrella of things
> that are power by our community, or a portal to 'help people help Tor'.
>  * support.torproject.org - user support website
>
> Are we loosing press? FAQs? Donate page? The Blog? No :) the list above
> are the main entrance to all these things and more.
>
> I invite you to read more about each of this portal and other work
> related to this initiative in the children tickets (and their children
> tickets) associated with this project. Is a big project and the
> information written here is a summary of the summary ;)
>
> = Why now? =
> Right now we are with fund and a team to carry this work. And we need to
> do this to enable many other great work at Tor to have infrastructure to
> support their project. We believe that these portals will help a lot of
> groups inside of Tor Project to better provide information about their
> work and therefore receive help to do so.
>
> = What have we done =
> ''__*'''this part is not done yet'''*
> __''The story of Tor Project website is long! But to cut it short we will
> talk from 2015 - now (EOY 2017)
>
> This work will be funded by
> [https://docs.google.com/document/d/1pmknfCSWGnVNv9fYdF44nIOV4ThiPKBx9rfAKVP3j2w/edit?usp=sharing
> SIDA] and incorporate work from
> [https://trac.torproject.org/projects/tor/wiki/Website/MainSiteRedesign
> past efforts]. We did some work on the
> [https://trac.torproject.org/projects/tor/wiki/doc/UX/SupportPage support
> page] before this site-wide effort.
>
> = What we will use to build it? =
> '__*this part is not done yet*__'
>
> = Are we planing to test things? =
> Yes, not only our framework but everything! We hope to do as many
> research and test we can, it will all depend on our bandwidth and
> resources. Since we have been working on building this 'testing' and
> 'research' steps into our processes we already have some stuff in place
> that can help us carry those on. We hope to continue to add  more
> resources in this front to be able to do even more of those in the
> future!
>
> This project is actually the first year of a 3 years project where we
> hope to build this user feedback / testing process and have it happening
> in large scale for all the projects 

Re: [tor-bugs] #24160 [Metrics/Atlas]: Wrong info about bridges?

[Tor Bug Tracker & Wiki]

#24160: Wrong info about bridges?
---+--
 Reporter:  eduperez   |  Owner:  metrics-team
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by irl):

 Not my top priority, but please keep the ticket around and I'll look into
 updating the explanations around it. I like that Atlas can explain
 concepts to relay operators as well as just provide data and I'd like to
 achieve that.

--
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] #24275 [Webpages/Website]: Testing Lecktor as a possible framework to be used for all portals related to website redesign project

[Tor Bug Tracker & Wiki]

#24275: Testing Lecktor as a possible framework to be used for all portals 
related
to website redesign project
--+--
 Reporter:  isabela   |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:  ux-team,
Actual Points:|  Parent ID:  #21222
   Points:|   Reviewer:
  Sponsor:|
--+--
 = Requirements =
 We are looking for a framework that:
  * makes it easy for folks to update content
  * makes it easy for having mirrored static content
  * the internationalization of it works with Transifex
  * its easy to haver our styleguide bootstrap working with it (for
 building the site theme)

 = How to test it =

 The live test can be accessed here: http://pipeline.torproject.net:9900/

 Here is the git repository: https://oniongit.eu/infra/portal

 Here is the framework home page: https://www.getlektor.com

 Lektor can work as a console tool, like Jekyll. Also, if you have a mac
 though, you do not have to install anything from the console. You can use
 the mac desktop app.

 https://github.com/lektor/lektor/releases/tag/3.0.1

 What the app does is run the local lektor server that will allow you to
 edit the website as you would in a normal cms.

 If you would like to give it a try, you have to clone the git repository
 for the project first and then open the lektor app and browse to the
 repository folder.

 The idea is that once you make your changes you will be able to make a
 push and a merge request to the oniongit repository. I understand a small
 familiarity with git is required in this case.

 Please leave any questions or feedback as a comment on this ticket, if you
 feel working with this framework and if you think it can make your life
 easier.

--
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] #23797 [Metrics/Atlas]: Turn off autocorrect and autocapitalise in Atlas form fields

[Tor Bug Tracker & Wiki]

#23797: Turn off autocorrect and autocapitalise in Atlas form fields
---+--
 Reporter:  teor   |  Owner:  metrics-team
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

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


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

Re: [tor-bugs] #23796 [Metrics/Onionoo]: Stop rejecting field queries due to capitalisation

[Tor Bug Tracker & Wiki]

#23796: Stop rejecting field queries due to capitalisation
-+---
 Reporter:  teor |  Owner:  metrics-team
 Type:  defect   | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by irl):

 * parent:  #23797 =>


Comment:

 I have disabled autocorrect and autocapitalisation in Atlas.

--
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] #24127 [Core Tor/Tor]: Profile a 0.3.2.x fast relay

[Tor Bug Tracker & Wiki]

#24127: Profile a 0.3.2.x fast relay
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-relay, profiling  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by dgoulet):

 FYI, I'll do this again with our release candidate in December.

--
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] #23797 [Metrics/Atlas]: Turn off autocorrect and autocapitalise in Atlas form fields

[Tor Bug Tracker & Wiki]

#23797: Turn off autocorrect and autocapitalise in Atlas form fields
---+--
 Reporter:  teor   |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by irl):

 Fixed in 6647d5ace7408cf682ad16040a2d62cdc4586083.

--
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] #23682 [Metrics/Atlas]: Update Onionoo link on About page

[Tor Bug Tracker & Wiki]

#23682: Update Onionoo link on About page
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

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


Comment:

 There no longer is an about 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] #12522 [Metrics/Atlas]: Add sitemap.xml to Globe to make details pages indexed by Google et al.

[Tor Bug Tracker & Wiki]

#12522: Add sitemap.xml to Globe to make details pages indexed by Google et al.
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-2018   |  Actual Points:
Parent ID:  #23518 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

 * parent:   => #23518


Comment:

 This actually becomes possible when moving to metrics-web as the sitemap
 can be generated independently of the JavaScript application.

--
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] #18048 [Metrics/Atlas]: Update Atlas's jQuery

[Tor Bug Tracker & Wiki]

#18048: Update Atlas's jQuery
---+
 Reporter:  cypherpunks|  Owner:  irl
 Type:  defect | Status:  closed
 Priority:  Low|  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Minor  | Resolution:  fixed
 Keywords:  metrics-2018   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 We're now using jQuery 3.2.1, the same as metrics-web.

--
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] #24164 [Core Tor/Tor]: errors I get after I installed 0.3.2.3 on my relay

[Tor Bug Tracker & Wiki]

#24164: errors I get after I installed 0.3.2.3 on my relay
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  (none)
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by dgoulet):

 Replying to [comment:4 Dbryrtfbcbhgf]:
 > Replying to [comment:2 dgoulet]:
 > > Huh, can you provide your kernel version? Seems that the package was
 compiled with `SYS_getrandom` but yet the system doesn't have
 `getrandom()`.
 > >
 > > Are you using the deb.torproject.org packages or the one from your
 system?
 > Kernel 2.6.32 and I’m using the packages from deb.torproject.org.

 Ok, you must be using some newer Ubuntu packages than 10.04 Lucid which is
 End Of Life btw :S.

 So yeah this is not surprising and unfortunately not much we can do about
 it because the package you use it not meant for Lucid and thus assumes
 things that the system doesn't have.

--
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] #22147 [Metrics/Atlas]: Add Onionoo's exit_addresses field

[Tor Bug Tracker & Wiki]

#22147: Add Onionoo's exit_addresses field
---+
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Fixed in e565a2ea1952901b95ed93c3536652378493a5d8.

 I have not included the presentation patches. If this becomes an issue in
 the future we can take another look at 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] #23662 [Core Tor/Tor]: prop224: Service edge-case where it re-uploads descriptor with same rev counter

[Tor Bug Tracker & Wiki]

#23662: prop224: Service edge-case where it re-uploads descriptor with same rev
counter
-+
 Reporter:  asn  |  Owner:  dgoulet
 Type:  defect   | Status:  merge_ready
 Priority:  Medium   |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+
Changes (by dgoulet):

 * status:  needs_review => merge_ready
 * reviewer:   => dgoulet


Comment:

 lgtm;

--
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] #24164 [Core Tor/Tor]: errors I get after I installed 0.3.2.3 on my relay

[Tor Bug Tracker & Wiki]

#24164: errors I get after I installed 0.3.2.3 on my relay
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  (none)
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by Dbryrtfbcbhgf):

 Replying to [comment:2 dgoulet]:
 > Huh, can you provide your kernel version? Seems that the package was
 compiled with `SYS_getrandom` but yet the system doesn't have
 `getrandom()`.
 >
 > Are you using the deb.torproject.org packages or the one from your
 system?
 Kernel 2.6.32 and I’m using the packages from deb.torproject.org.

--
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] #22037 [Metrics/Atlas]: Rename the Properties subsection

[Tor Bug Tracker & Wiki]

#22037: Rename the Properties subsection
---+---
 Reporter:  cypherpunks|  Owner:  irl
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by irl):

 * status:  accepted => needs_information


Comment:

 Currently the subsection doesn't have a tooltip.

 The flags field has the tooltip "Flags that the directory authorities
 assigned to this relay."

 A possible renaming could be:

 "Additional Flags" : "Flags that have been generated by Relay Search to
 provide extra useful information. These flags do not appear in the
 directory consensus."

--
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] #23662 [Core Tor/Tor]: prop224: Service edge-case where it re-uploads descriptor with same rev counter

[Tor Bug Tracker & Wiki]

#23662: prop224: Service edge-case where it re-uploads descriptor with same rev
counter
-+
 Reporter:  asn  |  Owner:  dgoulet
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by asn):

 * status:  needs_revision => needs_review


Comment:

 Please see my branch `bug23662_032` for the 0.3.2 part as described in
 comment:7 above.

 After merging this, let's keep the ticket open and repurpose it to 0.3.3
 to continue with the comment:7 plan.

--
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] #24164 [Core Tor/Tor]: errors I get after I installed 0.3.2.3 on my relay

[Tor Bug Tracker & Wiki]

#24164: errors I get after I installed 0.3.2.3 on my relay
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  (none)
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by dgoulet):

 * 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] #24164 [Core Tor/Tor]: errors I get after I installed 0.3.2.3 on my relay

[Tor Bug Tracker & Wiki]

#24164: errors I get after I installed 0.3.2.3 on my relay
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by dgoulet):

 Huh, can you provide your kernel version? Seems that the package was
 compiled with `SYS_getrandom` but yet the system doesn't have
 `getrandom()`.

 Are you using the deb.torproject.org packages or the one from your system?

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

Re: [tor-bugs] #22185 [Metrics/Atlas]: Add red unmeasured icon to properties

[Tor Bug Tracker & Wiki]

#22185: Add red unmeasured icon to properties
---+
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Fixed in 743b56b69532a45a3d186f7df9169719a11c.

--
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] #24201 [Core Tor/Tor]: spec: ADD_ONION syntax is not reflecting the code

[Tor Bug Tracker & Wiki]

#24201: spec: ADD_ONION syntax is not reflecting the code
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  merge_ready
 Priority:  Low   |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-spec, tor-hs  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * status:  assigned => merge_ready


Comment:

 Branch: `ticket24201_01`

--
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] #24192 [Applications/Tor Browser]: When I visit a V3 onion that supplies a invalid certificate, torbrowser will lookup the onion when the get certifice button is clicked

[Tor Bug Tracker & Wiki]

#24192: When I visit a V3 onion that supplies a invalid certificate, torbrowser
will lookup the onion when the get certifice button is clicked
--+--
 Reporter:  Dbryrtfbcbhgf |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Dbryrtfbcbhgf):

 Replying to [comment:8 gk]:
 > See: https://blog.mozilla.org/security/2013/07/29/ocsp-stapling-in-
 firefox/ for some info about what OCSP stapling achieves.
  When the button is pressed will Tor browser leak the onion address, to
 some server?

--
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] #23662 [Core Tor/Tor]: prop224: Service edge-case where it re-uploads descriptor with same rev counter

[Tor Bug Tracker & Wiki]

#23662: prop224: Service edge-case where it re-uploads descriptor with same rev
counter
-+
 Reporter:  asn  |  Owner:  dgoulet
 Type:  defect   | Status:  needs_revision
 Priority:  Medium   |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by asn):

 * status:  needs_information => needs_revision


Comment:

 We discussed this with David and came with the following plan:
 1) In 0.3.2 we turn this warning to protocol_warn since we know of natural
 ways that it can be caused (i.e. this ticket)
 2) In 0.3.3 we fix this ticket properly and any other related issues
 found, and turn the warning back to a real warning since it shouldn't be
 caused naturally anymore.

--
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] #24041 [Metrics]: Add Apache Commons Configuration as configuration library

[Tor Bug Tracker & Wiki]

#24041: Add Apache Commons Configuration as configuration library
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Maybe rather summarize this ticket as:  "Unify Metrics' products
 operational configuration"

 The method/process of deployment configuration of Metrics' products should
 be unified.
 Afterwards, we look for the 'tool' or lib helping to achieve a
 simplification.

 ---
 Some thoughts:

 It seems that from all options (hard-coding, command-line parameters, and
 config files) the config file solution is best.  Also, because a
 configuration file can be checked into a local git on the deployment
 machine, i.e., less guessing what parameters are needed/ were used.

 A configuration file should follow a format/standard.
 [https://docs.oracle.com/javase/8/docs/api/java/util/Properties.html Java
 properties] should be first choice because they are easy to understand and
 Java provides the appropriate functionality for accessing them.  Second
 choice to make is between simple key-value properties and XML properties.
 IMO, the simple format ought to be sufficient and is better for 'human
 consumption'.

 CollecTor features the most complex configuration settings of all Metrics'
 products and is still based on simple key-value Java properties.
 All other products (cf. list below) have less configuration demands that
 could all be met by Java properties.

 Tools like commons-configuration provide 99% functionality that is beyond
 the needs of Metrics' products.  Using the functionality from there does
 not really simplify the code compared to using jdk-provided methods.


 Suggestion:

 1) Use key value properties files for configuration.
 2) Use Java provided functionality for accessing the properties.
 3) If there is the need for more sophisticated configuration methods
 throughout several products, look to provide them in a standardized way
 (i.e., in a metrics-lib's util package).




 -
 Overview of the current state as reference:

 - Onionoo: command line settings and hard coded settings
 - CollecTor: configuration file and Metrics' code for configuration checks
 and convenience methods incl. provision of a basic config file.  Using
 Java properties format.
 - ExoneraTor: configuration file read as a file (back end) and system
 properties (web part).
 - Web: mixture off all.
 - Bot: Apache Commons Configuration as configuration library (#23933).

--
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] #24174 [Metrics/ExoneraTor]: Use an embedded Jetty in ExoneraTor

[Tor Bug Tracker & Wiki]

#24174: Use an embedded Jetty in ExoneraTor
+
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  enhancement | Status:  needs_revision
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+

Comment (by iwakeh):

 Replying to [comment:14 karsten]:
 > Looks good and works locally!

 Good, I assume all db access works fine now.

 > Some comments/questions:
 >  - Can we use `metrics` and `password` as defaults in
 `src/main/resources/jetty.xml`? That should be as simple as writing
 `` and
 ``. Just in
 case somebody uses those defaults locally for testing, that is.

 That means, you want your private test environment configuration in
 development code ;-)

 I don't feel strongly about it.  Add them, if you like.  Just be aware
 that people looking at the code might think they discovered Tor's secret
 db credentials ;-)
 But, actually, this is part of a bigger discussion cf. my comment to
 #24041 about 'unifying deployment configuration'.  Let's rather continue
 the configuration discussion there.

 >
 >  - Is there a particular reason why you suggest bumping to 2.0.0 and not
 1.1.0? For the Java 8 update we also made a minor version bump. Nothing
 backward-incompatible going on here, right?

 Isn't it a major change to move away from external tomcat?  The deployment
 changes completely.


 >
 >  - Out of curiousity, what's the full command line that you're using to
 start the JAR and the WAR file? Mine is pretty long, and I'm curious
 whether that's just for me or for everyone. Maybe we can start thinking
 about configuration libraries (#24041) after this ticket?

 Deployment example:
 `java -Dexonerator.db.user=secretuser -Dexonerator.db.pw=secret -jar
 exonerator-1.0.0-dev.war`

 Test w/o db:
 `java -Dexonerator.url=http://127.0.0.1:8080 -jar exonerator-dummy-
 test.war`

 I did comment on #24041 and I'm not in favor of long command lines (they
 are better than hard-coded parameters), but that's a different ticket.

--
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] #24273 [Applications/Tor Browser]: Opening Tor Browser in another Windows User Account where it has been installed

[Tor Bug Tracker & Wiki]

#24273: Opening Tor Browser in another Windows User Account where it has been
installed
---+---
 Reporter:  devoucoux  |  Owner:  tbb-team
 Type:  defect | Status:  closed
 Priority:  High   |  Milestone:  Tor:
   |  unspecified
Component:  Applications/Tor Browser   |Version:  Tor:
   |  unspecified
 Severity:  Major  | Resolution:  not a bug
 Keywords:  Launch Tor in any Windows Account  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by mcs):

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


Comment:

 It might be easiest to install more than one copy of Tor Browser.  The
 user that Tor Browser is running as needs write access to the browser
 profile and Tor data directories that are located within the application
 directory.  You should be able to achieve that by adjusting permissions
 within Windows, but I cannot give you a step-by-step guide.

--
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] #23510 [Metrics/Atlas]: Filters in search results table always return no results

[Tor Bug Tracker & Wiki]

#23510: Filters in search results table always return no results
---+
 Reporter:  irl|  Owner:  irl
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Removed non-functioning filtering. This may be re-added in the future when
 datatables is updated, or if a different framework is used for the table.

 Fixed in 3282bb350addbd95477fb865c299f4bef788d676.

--
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] #24254 [Core Tor/Tor]: There needs to be documentation on what kernel versions the KIST Scheduler will run on

[Tor Bug Tracker & Wiki]

#24254: There needs to be documentation on what kernel versions the KIST 
Scheduler
will run on
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  pastly
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-sched  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by dgoulet):

 * milestone:  Tor: 0.3.3.x-final => Tor: 0.3.2.x-final


Comment:

 Replying to [comment:8 cypherpunks]:
 > Replying to [comment:4 pastly]:
 > > Now __WHERE__ should we document this? Comment in the source? Man
 page? Both? Neither? Looking for input from anyone here.
 > Make a wiki page on trac here?

 I would go with at least the man page for sure. Requirements for an option
 in the man page have to be documented there.

 (Moving it to 032... I think it was a mistake for this to be in 033.)

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

Re: [tor-bugs] #23522 [Metrics/Atlas]: Improve tooltip on DNS name field (and maybe title)

[Tor Bug Tracker & Wiki]

#23522: Improve tooltip on DNS name field (and maybe title)
---+
 Reporter:  irl|  Owner:  irl
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Ok, I read the Java documentation. It didn't help. Then I looked at
 StackOverflow.

 My description is correct.

 Fixed in ce07ca3b784f9b76def9387790731268a5ee4750.

--
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] #23764 [Core Tor/Tor]: hs-v3: No live consensus on client with a bridge

[Tor Bug Tracker & Wiki]

#23764: hs-v3: No live consensus on client with a bridge
-+
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  defect   | Status:  needs_revision
 Priority:  High |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by dgoulet):

 * status:  needs_information => needs_revision
 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.3.x-final


Comment:

 Replying to [comment:6 asn]:
 > BTW here is an example of a thing that might go bad (and the suggested
 tests above would not catch):
 >
 > `get_voting_interval()` and `hs_get_time_period_num()` and
 `hs_in_period_between_tp_and_srv()` all use
 `networkstatus_get_live_consensus()` and are used both by clients and
 services in multiple places. If a live consensus is not found those
 functions have an alternative behavior, and if we do the suggested change
 here we could be using this alternative behavior more frequently. We
 should make sure that this won't cause any reachability issues.

 Good points!

 I've did an investigation and shared random is the problem. We kind of
 bound tightly the HS and SR subsystems with those functions. Dirauth MUST
 use the live consensus for their computation of intervals and time period
 so we can't change `get_voting_interval()` to use "latest consensus". It
 could have consequences on the SR (maybe although I really wonder if a
 dirauth can operate without a live consensus...)

 To pull this off, we would need a function from which we can control which
 `ns` object we pass to the series of functions that we need in the HS
 subsystem from the SR subsystem or tell the function that we do not care
 about live.

 For `hs_get_time_period_num()`, it is OK to stay like this using a live
 consensus because that function returns the time period tor thinks it is
 in and it should be either a live consensus or just wing it with the
 current time which is what we want if we have no live but we'll still try
 to reach the HS.

 For the service, it ONLY uploads descriptors if it has a live consensus,
 this is enforced in `should_service_upload_descriptor()` so no way to go
 around. It means that once a client gets a descriptor, it is for sure a
 live consensus that the service has.

 That being said:

 * `hs_in_period_between_tp_and_srv()` is only used by the service so that
 is fine to keep using live consensus requirement.

 * The problem, as you pointed it out, is the use of the functions from the
 SR subsystem that we can't change that requirement.

 In conclusion, we need a set of functions that do not require a live
 consensus that only the HS client would use where the SR would use
 something else that requires the live consensus.

 I'm unsure about 032 for this. I think we might be OK to postpone this
 until we get a sense of what is the impact on reachability/usablility and
 who knows, maybe 99.9% of tor clients work with a live consensus and maybe
 it is probably good for them to wait for 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] #18342 [Metrics/Onionoo]: Provide more accurate reverse DNS results

[Tor Bug Tracker & Wiki]

#18342: Provide more accurate reverse DNS results
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 Java does indeed check to see that there is an A record that matches the
 PTR record when using InetAddress.getHostName().

 The following would allow us to perform this "manually":
 https://docs.oracle.com/javase/8/docs/technotes/guides/jndi/jndi-dns.html

 We could then flag whether or not the A record matched and return this
 information along 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] #24274 [Metrics/Atlas]: Add a search box at the top right corner of the new Atlas page

[Tor Bug Tracker & Wiki]

#24274: Add a search box at the top right corner of the new Atlas page
---+--
 Reporter:  dgoulet|  Owner:  irl
 Type:  enhancement| Status:  accepted
 Priority:  High   |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

 * owner:  metrics-team => irl
 * status:  new => accepted
 * priority:  Medium => High


Comment:

 I think I have a plan that involves floating the box to the right of the
 "Relay Search" header. It may be hidden on mobile, or maybe I come up with
 a plan for where to put it on mobile.

--
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] #24274 [Metrics/Atlas]: Add a search box at the top right corner of the new Atlas page

[Tor Bug Tracker & Wiki]

#24274: Add a search box at the top right corner of the new Atlas page
---+--
 Reporter:  dgoulet|  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 Now that Atlas has moved to the metrics page, it lost its very useful
 search box at the top right corner.

 If we can bring it back, it would be grand. EXTRA point and beer for a
 small "x" in that box to clear it out of its content :).

--
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] #24273 [Applications/Tor Browser]: Opening Tor Browser in another Windows User Account where it has been installed

[Tor Bug Tracker & Wiki]

#24273: Opening Tor Browser in another Windows User Account where it has been
installed
---+---
 Reporter:  devoucoux  |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  High   |  Milestone:  Tor:
   |  unspecified
Component:  Applications/Tor Browser   |Version:  Tor:
   |  unspecified
 Severity:  Major  | Resolution:
 Keywords:  Launch Tor in any Windows Account  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by devoucoux):

 * Attachment "Bureau W7 14-11-2017.jpg" 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] #23681 [Core Tor/Tor]: prop224: Clients mark intro circs as timed-out within seconds

[Tor Bug Tracker & Wiki]

#23681: prop224: Clients mark intro circs as timed-out within seconds
-+
 Reporter:  asn  |  Owner:  dgoulet
 Type:  defect   | Status:  needs_review
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  mikeperry|Sponsor:
-+
Changes (by dgoulet):

 * priority:  Medium => High
 * reviewer:   => mikeperry
 * status:  needs_revision => needs_review


Comment:

 Branch: `bug23681_032_01`

 Putting Mike has a reviewer since we discussed this and it can be very
 tricky.

--
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] #24273 [Applications/Tor Browser]: Opening Tor Browser in another Windows User Account where it has been installed

[Tor Bug Tracker & Wiki]

#24273: Opening Tor Browser in another Windows User Account where it has been
installed
-+-
 Reporter:  devoucoux|  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor: unspecified
Component:  Applications/Tor |Version:  Tor: unspecified
  Browser|   Keywords:  Launch Tor in any
 Severity:  Major|  Windows Account
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Hello,

 I've installed Tor under my Windows 7 Administrator Account and it is
 working perfectly.

 My problem is that i can't open Tor Browser in any other User Account,
 when trying it i obtain the message you can see on tje screen capture i
 attach to this ticket (Tor Browser n'a pas le droit d'accéder au profil.
 Veuillez ajuster les droits de votre système de fichiers et ressayer).

 How can i use Tor Browser in any User Account on Windows 7 or/and how can
 i copy the Administrator Tor profile in any other User Account?

 Thanks in advance for any help.

 Best regards

 Eric

--
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] #21615 [Metrics/Atlas]: Use hashed fingerprint in all lookups

[Tor Bug Tracker & Wiki]

#21615: Use hashed fingerprint in all lookups
---+
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 I am happy that we're not using any fingerprints that we shouldn't be
 using.

--
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] #23871 [Metrics/Atlas]: Atlas top-10 drop down broken

[Tor Bug Tracker & Wiki]

#23871: Atlas top-10 drop down broken
---+---
 Reporter:  phoul  |  Owner:  Hedylogos
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by irl):

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


Comment:

 Now loading 50 relays instead, so the drop down will work up to 50.

 I really need to update datatables or use a different framework for that
 table.

 Fix in bd2cdcd476ccc01055762e1cf7713fc45d61cba6

--
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] #23890 [Metrics/Atlas]: Drop minutes and seconds from first seen time delta (was: Display >365 as years in relative first seen time and drop hours and seconds)

[Tor Bug Tracker & Wiki]

#23890: Drop minutes and seconds from first seen time delta
---+---
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by irl):

 * status:  needs_review => new


Old description:

> First Seen field shows the relative first seen time in ().
>
> - display >365 days as n years m days ...
> - drop seconds and minutes (first_seen has an hour granularity)

New description:

 First Seen field shows the relative first seen time in ().

 * Minutes and seconds should be dropped from first_seen as this has only a
 granularity of hours.
 * Other fields may have finer granularities, so we shouldn't drop the
 granularity of the human readable version for those

--

Comment:

 I have merged the above in d660d2bdbcf35d1d1ed2158543897c79e04fb3ad.

 Updating the description and title to reflect what still needs to be 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] #23868 [Metrics/Atlas]: Long contactInfo is not properly displayed

[Tor Bug Tracker & Wiki]

#23868: Long contactInfo is not properly displayed
---+---
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by irl):

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


Comment:

 Merged in 261aa0a43b28810b1e90be902fa2c20fc7ba6b6a.

--
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] #23577 [Core Tor/Tor]: Add rendezvous point IPv6 address to client introduce cells

[Tor Bug Tracker & Wiki]

#23577: Add rendezvous point IPv6 address to client introduce cells
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:  2
  ipv6, review-group-25  |
Parent ID:  #23493   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
 |  SponsorV-can
-+-

Comment (by dgoulet):

 Replying to [comment:26 neel]:
 > I have a patch which (hopefully) should resolve the two issues. The
 filename is 008-bugfix1.patch​.

 Thanks neel for the patch.

 Continuing on teor's review, I also would go with a pattern like this
 instead:

 {{{
 if (exit_node == NULL) {
   log_info(...)
   goto done;
 }
 setup_intro1()
 }}}

 The reason I think we should go with a `log_info()` instead of warning is
 because this is a very very rare race condition so if it occurs, no need
 for a warning because it is a possible "normal behavior" .

 The SOCKS connection will fail but at that point the application can retry
 and chances are that it will succeed.

--
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] #23518 [Metrics/Atlas]: Turn Atlas into page on Tor Metrics

[Tor Bug Tracker & Wiki]

#23518: Turn Atlas into page on Tor Metrics
---+--
 Reporter:  karsten|  Owner:  irl
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by irl):

 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