Re: [tor-bugs] #19824 [Core Tor/Tor]: /var/run/tor/control socket not created because of /var/run/tor permission issue

[Tor Bug Tracker & Wiki]

#19824: /var/run/tor/control socket not created because of /var/run/tor 
permission
issue
--+--
 Reporter:  adrelanos |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by adrelanos):

 I emptied my torrc for testing purposes, restarted tor, still getting
 this. (Didn't happen with earlier Tor versions.) Still trying to figure
 what makes the difference on my system.

 {{{
 Aug 03 21:56:34.000 [warn] Permissions on directory /var/run/tor are too
 permissive.
 Aug 03 21:56:34.000 [warn] Before Tor can create a control socket in
 "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and
 to be accessible only by the user and group account that is running Tor.
 (On some Unix systems, anybody who can list a socket can connect to it, so
 Tor is being careful.)
 }}}

 -

 In {{{tor.postinst}}} you are using {{{chmod 02750 /var/run/tor}}} but for
 systemd you are using {{{02755}}}. Is that supposed to be like 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] #19737 [Applications/Tor Browser]: gpg/gk.gpg and gpg/torbutton.gpg are expired since 2016-07-19

[Tor Bug Tracker & Wiki]

#19737: gpg/gk.gpg and gpg/torbutton.gpg are expired since 2016-07-19
---+---
 Reporter:  dcf|  Owner:  tbb-team
 Type:  defect | Status:
 Priority:  Medium |  needs_review
Component:  Applications/Tor Browser   |  Milestone:
 Severity:  Normal |Version:
 Keywords:  tbb-gitian, TorBrowserTeam201607R  | Resolution:
Parent ID: |  Actual Points:
 Reviewer: | Points:
   |Sponsor:
---+---

Comment (by serene):

 Confirming that applying boklm's patch seems to have fixed the gpg expiry
 issues at least on my end when I try to build.

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

Re: [tor-bugs] #19812 [Applications/Tor Browser]: onion everywhere

[Tor Bug Tracker & Wiki]

#19812: onion everywhere
--+--
 Reporter:  ilf   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  onion, https everywhere   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 This was the goal of [https://github.com/chris-barry/darkweb-everywhere
 Darkweb-Everywhere] but as mentioned in its README file the introduction
 of extension signing finished it. Its rules are still usable so maybe it
 can be somehow be merged into HTTPS Everywhere?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19819 [Core Tor/Tor]: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6

[Tor Bug Tracker & Wiki]

#19819: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6
--+
 Reporter:  hacktic   |  Owner:
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by hacktic):

 * component:  Core Tor => Core Tor/Tor


Comment:

 Update 2: dug a bit deeper, checked
 /lib/systemd/system/tor@default.service which has TimeoutStartSec=120

 I assume if this gets bumped to TimeoutStartSec=500 we might not run into
 the above issue any longer.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19720 [Metrics/CollecTor]: CollecTor should be re-configurable without restart

[Tor Bug Tracker & Wiki]

#19720: CollecTor should be re-configurable without restart
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 Just amended some checkstyle corrections to new code.
 All still ready for review.

 This code is now running on the mirror.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18871 [Core Tor/Tor]: deb.torproject.org-keyring needs gnupg, not gnupg2

[Tor Bug Tracker & Wiki]

#18871: deb.torproject.org-keyring needs gnupg, not gnupg2
--+-
 Reporter:  ilf   |  Owner:
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by dkg):

 * cc: dkg@… (added)
 * status:  new => merge_ready


Comment:

 The patch above should resolve the dependency on gnupg, and should also
 make the package uninstall cleanly.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19824 [Core Tor/Tor]: /var/run/tor/control socket not created because of /var/run/tor permission issue

[Tor Bug Tracker & Wiki]

#19824: /var/run/tor/control socket not created because of /var/run/tor 
permission
issue
--+--
 Reporter:  adrelanos |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by weasel):

 What does your torrc look like?  I suspect you are using a non-standard
 configuration for your control socket.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19824 [Core Tor/Tor]: /var/run/tor/control socket not created because of /var/run/tor permission issue

[Tor Bug Tracker & Wiki]

#19824: /var/run/tor/control socket not created because of /var/run/tor 
permission
issue
--+--
 Reporter:  adrelanos |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Using Tor {{{0.2.8.6}}} from deb.torproject.org,
 {{{/var/run/tor/control}}} is no longer created because of a permission
 issue. As a manual workaround, {{{sudo chmod --recursive 700
 /var/run/tor}}} works.

 The symptom in Tor's log is the following:

 {{{
 Aug 03 17:36:33.000 [warn] Permissions on directory /var/run/tor are too
 permissive.
 }}}

 Rather than {{{755}}} Tor's {{{/lib/systemd/system/tor@default.service}}}
 should use {{{700}}}. I.e. rather than using:

 {{{
 ExecStartPre=/usr/bin/install -Z -m 02755 -o debian-tor -g debian-tor -d
 /var/run/tor
 }}}

 {{{/lib/systemd/system/tor@default.service}}} should use:

 {{{
 ExecStartPre=/usr/bin/install -Z -m 02700 -o debian-tor -g debian-tor -d
 /var/run/tor
 }}}

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

Re: [tor-bugs] #19755 [Metrics/CollecTor]: improve code quality of bridgedescs module

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

 Okay, I incorporated more feedback from this ticket, though I didn't fix
 all bugs yet.  I also didn't start going through the findings from
 Findbugs et al.  I might not get back to this before Friday, so I figured
 I could push progress for now.  Feel free to review now or wait for more
 progress in the next couple of days.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19823 [Core Tor/Stem]: pwd not available on Windows

[Tor Bug Tracker & Wiki]

#19823: pwd not available on Windows
---+
 Reporter:  trodun |  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by atagar):

 Great catch, thanks! I'll try to get a fix out for this in the next day or
 so.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19823 [Core Tor/Stem]: pwd not available on Windows

[Tor Bug Tracker & Wiki]

#19823: pwd not available on Windows
---+
 Reporter:  trodun |  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 The commit below breaks Windows support, the pwd module is only available
 on Unix.

 
https://gitweb.torproject.org/stem.git/commit/?id=4082270d068338fa01a433a9006a1073fc4d087b

 {{{
 ImportError: No module named 'pwd'
   File "run.py", line 141, in run_process
 start_app()
   File "run.py", line 39, in start_app
 from app.main import run_app
   File "E:\dev\prs\test\app\main.py", line 86, in 
 from app.network import net
   File "E:\dev\prs\test\app\network.py", line 13, in 
 from stem.control import Controller as StemCtrl
   File "e:\dev\prs\stem\stem\control.py", line 261, in 
 import stem.descriptor.microdescriptor
   File "e:\dev\prs\stem\stem\descriptor\__init__.py", line 51, in 
 import stem.util.system
   File "e:\dev\prs\stem\stem\util\system.py", line 62, in 
 import stem.util.proc
   File "e:\dev\prs\stem\stem\util\proc.py", line 53, in 
 import pwd
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19822 [Metrics/CollecTor]: set up a CollecTor mirror for synchronization with the main CollecTor

[Tor Bug Tracker & Wiki]

#19822: set up a CollecTor mirror for synchronization with the main CollecTor
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+-
 This depends on #18910.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19821 [Core Tor/Tor]: --expensive-hardening makes configure check for curve25519-donna-c64 to fail

[Tor Bug Tracker & Wiki]

#19821: --expensive-hardening makes configure check for curve25519-donna-c64 to
fail
--+--
 Reporter:  yurivict271   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by yurivict271):

 This might be the bug in clang as as well, I am reporting it here because
 I see it on the tor project.

 Did you test this option with clang compiler on linux?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19821 [Core Tor/Tor]: --expensive-hardening makes configure check for curve25519-donna-c64 to fail

[Tor Bug Tracker & Wiki]

#19821: --expensive-hardening makes configure check for curve25519-donna-c64 to
fail
--+--
 Reporter:  yurivict271   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by yurivict271):

 Command line is from config.log:
 {{{
 cc -o conftest -O2 -pipe  -fstack-protector -fno-strict-aliasing -static
 -fsanitize=address -fsanitize=undefined -fno-omit-frame-pointer
 -fasynchronous-unwind-tables  -Is
 rc/common  -Wl,-rpath,/usr/local/lib -fstack-protector x.c -lpthread
 -lexecinfo
 }}}

 x.c is the corresponding failed program from config.log:

 {{{
 /* confdefs.h */
 #define PACKAGE_NAME "tor"
 #define PACKAGE_TARNAME "tor"
 #define PACKAGE_VERSION "0.2.8.6"
 #define PACKAGE_STRING "tor 0.2.8.6"
 #define PACKAGE_BUGREPORT ""
 #define PACKAGE_URL ""
 #define PACKAGE "tor"
 #define VERSION "0.2.8.6"
 #define FLEXIBLE_ARRAY_MEMBER /**/
 #define STDC_HEADERS 1
 #define HAVE_SYS_TYPES_H 1
 #define HAVE_SYS_STAT_H 1
 #define HAVE_STDLIB_H 1
 #define HAVE_STRING_H 1
 #define HAVE_MEMORY_H 1
 #define HAVE_STRINGS_H 1
 #define HAVE_INTTYPES_H 1
 #define HAVE_STDINT_H 1
 #define HAVE_UNISTD_H 1
 #define HAVE_ACCEPT4 1
 #define HAVE_BACKTRACE 1
 #define HAVE_CLOCK_GETTIME 1
 #define HAVE_FLOCK 1
 #define HAVE_GETADDRINFO 1
 #define HAVE_GETIFADDRS 1
 #define HAVE_GETPASS 1
 #define HAVE_GETRLIMIT 1
 #define HAVE_GETTIMEOFDAY 1
 #define HAVE_GMTIME_R 1
 #define HAVE_INET_ATON 1
 #define HAVE_IOCTL 1
 #define HAVE_ISSETUGID 1
 #define HAVE_LOCALTIME_R 1
 #define HAVE_MEMMEM 1
 #define HAVE_PIPE 1
 #define HAVE_PIPE2 1
 #define HAVE_READPASSPHRASE 1
 #define HAVE_SIGACTION 1
 #define HAVE_SOCKETPAIR 1
 #define HAVE_STATVFS 1
 #define HAVE_STRLCAT 1
 #define HAVE_STRLCPY 1
 #define HAVE_STRNLEN 1
 #define HAVE_STRPTIME 1
 #define HAVE_STRTOK_R 1
 #define HAVE_STRTOULL 1
 #define HAVE_SYSCONF 1
 #define HAVE_SYSCTL 1
 #define HAVE_UNAME 1
 #define HAVE_USLEEP 1
 #define HAVE_VASPRINTF 1
 #define HAVE_PTHREAD_H 1
 #define HAVE_PTHREAD_CREATE 1
 #define HAVE_PTHREAD_CONDATTR_SETCLOCK 1
 #define HAVE_EVENT_GET_VERSION_NUMBER 1
 #define HAVE_EVUTIL_SECURE_RNG_SET_URANDOM_DEVICE_FILE 1
 #define HAVE_EVUTIL_SECURE_RNG_INIT 1
 #define HAVE_EVENT2_EVENT_H 1
 #define HAVE_EVENT2_DNS_H 1
 #define HAVE_EVENT2_BUFFEREVENT_SSL_H 1
 #define USE_BUFFEREVENTS 1
 #define HAVE_STRUCT_SSL_METHOD_ST_GET_CIPHER_BY_CHAR 1
 #define HAVE_SSL_CIPHER_FIND 1
 /* end confdefs.h.  */
   #include 
   typedef unsigned uint128_t __attribute__((mode(TI)));
   int func(uint64_t a, uint64_t b) {
uint128_t c = ((uint128_t)a) * b;
int ok = ((uint64_t)(c>>96)) == 522859 &&
  (((uint64_t)(c>>64))&0xL) == 3604448702L &&
  (((uint64_t)(c>>32))&0xL) == 2351960064L &&
  (((uint64_t)(c))&0xL) == 0;
return ok;
   }

 int
 main ()
 {
 int ok = func( ((uint64_t)20) * 10,
((uint64_t)1234567890) << 24);
 return !ok;

   ;
   return 0;
 }
 }}}

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

Re: [tor-bugs] #19821 [Core Tor/Tor]: --expensive-hardening makes configure check for curve25519-donna-c64 to fail

[Tor Bug Tracker & Wiki]

#19821: --expensive-hardening makes configure check for curve25519-donna-c64 to
fail
--+--
 Reporter:  yurivict271   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by nickm):

 Can you tell what's in x.c ? And what's around that command line?

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

Re: [tor-bugs] #19821 [Core Tor/Tor]: --expensive-hardening makes configure check for curve25519-donna-c64 to fail

[Tor Bug Tracker & Wiki]

#19821: --expensive-hardening makes configure check for curve25519-donna-c64 to
fail
--+--
 Reporter:  yurivict271   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by yurivict271):

 This is the command line that I picked from config.log in OP.
 When -fsanitize=address -fsanitize=undefined is removed it succeeds.
 Otherwise I don't know much about sanitizer.

 Compiler is clang 3.4.1

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

Re: [tor-bugs] #19821 [Core Tor/Tor]: --expensive-hardening makes configure check for curve25519-donna-c64 to fail

[Tor Bug Tracker & Wiki]

#19821: --expensive-hardening makes configure check for curve25519-donna-c64 to
fail
--+--
 Reporter:  yurivict271   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by nickm):

 Hm. Are you able to look through config.log to see why this is happening?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19819 [Core Tor]: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6

[Tor Bug Tracker & Wiki]

#19819: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6
--+
 Reporter:  hacktic   |  Owner:
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor  |Version:  Tor: 0.2.8.6
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by hacktic):

 Update: couldnt get systemd timeout increased somehow (TimeoutSec=infinity
 etc.)

 ended up deleting cached-descriptors  cached-descriptors.new cached-
 microdescs cached-microdescs.new, restarted and now its running again.

 My theory is that once my box runs for a couple of days (it was running
 for about 1 week earlier) it builds up enough of a cache that on restart
 it will hit the systemd service timeout, is there a way to limit the cache
 created ?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19821 [Core Tor/Tor]: --expensive-hardening makes configure check for curve25519-donna-c64 to fail

[Tor Bug Tracker & Wiki]

#19821: --expensive-hardening makes configure check for curve25519-donna-c64 to
fail
--+--
 Reporter:  yurivict271   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 On FreeBSD 10.3 the error message is:

 {{{
 # cc -o conftest -O2 -pipe  -fstack-protector -fno-strict-aliasing -static
 -fsanitize=address -fsanitize=undefined -fno-omit-frame-pointer
 -fasynchronous-unwind-tables  -Is
 rc/common  -Wl,-rpath,/usr/local/lib -fstack-protector x.c -lpthread
 -lexecinfo
 /tmp/x-85cb71.o: In function `asan.module_ctor':
 x.c:(.text+0x65): undefined reference to `__asan_init_v3'
 cc: error: linker command failed with exit code 1 (use -v to see
 invocation)
 }}}

 Another failure in configure phase 'checking size of int8_t... 0' makes it
 to fail entirely.

 Sanitizer options are causing this.

 expensive-hardening isn't normally enabled by the port. I tried to enable
 it and ran into this problem.

 To reproduce: in FreeBSD port security/tor add this line 'CONFIGURE_ARGS
 +=--enable-expensive-hardening' and run make.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19170 [Metrics/CollecTor]: make parsing more robust (extra-info)

[Tor Bug Tracker & Wiki]

#19170: make parsing more robust (extra-info)
---+--
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 Replying to [comment:11 karsten]:
 > ...
 > Regarding the `LenientParser` idea, I wonder whether we should just skip
 the metrics-lib check to see whether we can parse a descriptor before
 writing it to disk.  See `ArchiveWriter#store()`.  At that point we
 already parsed all relevant fields that we need for storing the descriptor
 without using metrics-lib, and that check is only there to make sure that
 metrics-lib will be able parse the descriptor later.  But if we want to
 take that check out, which I think we should, then let's just change that
 code to print out an informational log statement and store the file
 anyway.  What do you think?

 I agree, removing the metrics-lib check and informing known clients that
 do not use metrics-lib for parsing seems to be the simplest option here.
 It will decrease the number of missing descriptors immediately and is a
 'minimal-invasive' code change.

 Summary:

 CollecTor should not require parsability - except for the fields necessary
 - of descriptors when downloading/storing and only logs a warning if
 metrics-lib complains. (Eventually CollecTor could verify the signature.
 But, that's a different thing.)
  Without adapting metrics-lib these descriptors would trigger an exception
 during parsing in a metrics-lib dependent client, which handles parser
 exception already in some way (probably drop the descriptor). Clients
 without metrics-lib might have additional problems now and should be
 warned before such a change is deployed.

  Possible future option: When augmenting metrics-lib with a LenientParser
 the decision has to be made for the various clients, if they also want to
 use that parser option. If the client keeps the strict parser this will be
 like case 1.  If the client uses the LenientParser, it might provide
 unreadable characters (didn't we have tickets about that in Onionoo
 somewhere?).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19820 [Core Tor/Tor]: Add deprecation facility, and deprecate some old options

[Tor Bug Tracker & Wiki]

#19820: Add deprecation facility, and deprecate some old options
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .5
Parent ID:  #18857| Points:  1
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * points:  .5 => 1


Comment:

 Oh!  I do have a ticket that does part of this. assigning as 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] #19820 [Core Tor/Tor]: Add deprecation facility, and deprecate some old options

[Tor Bug Tracker & Wiki]

#19820: Add deprecation facility, and deprecate some old options
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201608  |  Actual Points:  .5
Parent ID:  #18857 | Points:  1
 Reviewer: |Sponsor:
---+
Changes (by nickm):

 * keywords:   => TorCoreTeam201608


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

Re: [tor-bugs] #18857 [Core Tor/Tor]: Add a soft-deprecation mechanism for configuration options

[Tor Bug Tracker & Wiki]

#18857: Add a soft-deprecation mechanism for configuration options
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  parent
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  new => needs_review
 * points:  1 => parent


Comment:

 #19820 does 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] #19820 [Core Tor/Tor]: Add deprecation facility, and deprecate some old options

[Tor Bug Tracker & Wiki]

#19820: Add deprecation facility, and deprecate some old options
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .5
Parent ID:  #18857| Points:  .5
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * parent:   => #18857


Comment:

 Oh!  I do have a ticket that does part of this. assigning as 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] #19820 [Core Tor/Tor]: Add deprecation facility, and deprecate some old options

[Tor Bug Tracker & Wiki]

#19820: Add deprecation facility, and deprecate some old options
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .5
Parent ID:| Points:  .5
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 My deprecation_v2 branch marks a bunch of options and sub-options as in
 need of removal. Please 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] #19820 [Core Tor/Tor]: Add deprecation facility, and deprecate some old options

[Tor Bug Tracker & Wiki]

#19820: Add deprecation facility, and deprecate some old options
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .5
Parent ID:| Points:  .5
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * owner:   => nickm
 * status:  new => accepted
 * component:  - Select a component => Core Tor/Tor


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

[tor-bugs] #19820 [- Select a component]: Add deprecation facility, and deprecate some old options

[Tor Bug Tracker & Wiki]

#19820: Add deprecation facility, and deprecate some old options
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:  .5|  Parent ID:
   Points:  .5|   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] #19819 [Core Tor]: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6

[Tor Bug Tracker & Wiki]

#19819: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6
--+
 Reporter:  hacktic   |  Owner:
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor  |Version:  Tor: 0.2.8.6
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by hacktic):

 debug log, last line:[debug] router_parse_list_from_string(): Read router
 etc.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19815 [Internal Services/Tor Sysadmin Team]: Create https://aus2.torproject.org/ for Tor Messenger updates

[Tor Bug Tracker & Wiki]

#19815: Create https://aus2.torproject.org/ for Tor Messenger updates
-+-
 Reporter:  boklm|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #14388   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 For the timeline, we plan to have a new Tor Messenger release with this
 updater in something like 2 months.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19819 [Core Tor]: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6

[Tor Bug Tracker & Wiki]

#19819: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6
--+
 Reporter:  hacktic   |  Owner:
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor  |Version:  Tor: 0.2.8.6
 Severity:  Major |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Upgraded from Tor 0.2.8.5-rc to 0.2.8.6 on a pi2 using
 http://deb.torproject.org/torproject.org/dists/jessie/

 on start-up it goes to 100% CPU usage and after about 3 minutes default
 service kills and restarts tor, this goes into a loop, last message in tor
 log:  Bootstrapped 0%: Starting

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19818 [Applications/Tor Browser]: The update_responses script should use a config.yml option for the releases directory path

[Tor Bug Tracker & Wiki]

#19818: The update_responses script should use a config.yml option for the 
releases
directory path
--+
 Reporter:  boklm |  Owner:  boklm
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #19817
   Points:|   Reviewer:
  Sponsor:|
--+
 The directory containing the releases is currently set in the
 `update_responses` script to `../../gitian`. This directory will be
 different for Tor Messenger.

 In order to be able to share the `update_responses` script between Tor
 Browser and Tor Messenger without modification, we should add a
 `releases_dir` option in the `config.yml` file.

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

[tor-bugs] #19817 [Applications/Tor Messenger]: Import script to generate update responses and incremental mars in Tor Messenger

[Tor Bug Tracker & Wiki]

#19817: Import script to generate update responses and incremental mars in Tor
Messenger
+
 Reporter:  boklm   |  Owner:  boklm
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  |   Keywords:
Actual Points:  |  Parent ID:  #14388
   Points:  |   Reviewer:
  Sponsor:  |
+
 In Tor Browser, the script `tools/update-responses/update_responses` is
 used to generate incremental mar files and update manifests.

 We should import this script into the Tor Messenger repository and adapt
 its configuration file.

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

Re: [tor-bugs] #19816 [Applications/Tor Messenger]: The Tor Messenger build process should generate mar files

[Tor Bug Tracker & Wiki]

#19816: The Tor Messenger build process should generate mar files
+-
 Reporter:  boklm   |  Owner:
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #14388  | Points:
 Reviewer:  |Sponsor:
+-
Changes (by boklm):

 * type:  project => task


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19816 [Applications/Tor Messenger]: The Tor Messenger build process should generate mar files

[Tor Bug Tracker & Wiki]

#19816: The Tor Messenger build process should generate mar files
+
 Reporter:  boklm   |  Owner:
 Type:  project | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  |   Keywords:
Actual Points:  |  Parent ID:  #14388
   Points:  |   Reviewer:
  Sponsor:  |
+
 The Tor Messenger build process should produce mar files.

 This can be done using the `make_full_update.sh` script:
 https://gitweb.torproject.org/builders/tor-browser-
 bundle.git/tree/gitian/descriptors/linux/gitian-
 bundle.yml?id=tbb-6.0.3-build2#n285

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19815 [Internal Services/Tor Sysadmin Team]: Create https://aus2.torproject.org/ for Tor Messenger updates

[Tor Bug Tracker & Wiki]

#19815: Create https://aus2.torproject.org/ for Tor Messenger updates
-+
 Reporter:  boklm|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:  #14388
   Points:   |   Reviewer:
  Sponsor:   |
-+
 We are using https://aus1.torproject.org/ to host the Tor Browser update
 manifests.

 Tor Messenger is going to have an updater similar to the updater from Tor
 Browser, and needs a place to host its update manifests. I think
 https://aus2.torproject.org/ could be created for that.

 The `tormessenger` group can be used for the write access to the
 directory.

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

Re: [tor-bugs] #19809 [Applications/Tor Messenger]: Update verification failed but update still applies on Linux and OS X

[Tor Bug Tracker & Wiki]

#19809: Update verification failed but update still applies on Linux and OS X
+-
 Reporter:  sukhbir |  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #14388  | Points:
 Reviewer:  |Sponsor:
+-
Changes (by boklm):

 * parent:   => #14388


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19809 [Applications/Tor Messenger]: Update verification failed but update still applies on Linux and OS X

[Tor Bug Tracker & Wiki]

#19809: Update verification failed but update still applies on Linux and OS X
+-
 Reporter:  sukhbir |  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-

Comment (by sukhbir):

 Update: I realized I was copying the DER file to just
 release_secondary.der; I changed it to copy to both release_primary and
 release_secondary. So maybe the error in the above case was because
 release_primary failed but release_secondary worked. I no longer have this
 issue on Linux and OS X.

 On Windows, I still get the update failed with error code 19. Is the
 Windows update verification different from Linux and OS X?

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

Re: [tor-bugs] #19710 [Metrics/Ooni]: Update debian/ubuntu packages of ooniprobe to 1.6.1

[Tor Bug Tracker & Wiki]

#19710: Update debian/ubuntu packages of ooniprobe to 1.6.1
--+
 Reporter:  hellais   |  Owner:  irl
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Metrics/Ooni  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by irl):

 * status:  accepted => 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] #19300 [Core Tor/Tor]: Document miscellaneous things in src/common in tor-guts

[Tor Bug Tracker & Wiki]

#19300: Document miscellaneous things in src/common in tor-guts
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
Component:  Core Tor/Tor |  0.2.9.x-final
 Severity:  Normal   |Version:
 Keywords:  tor-docs-dev, tor-doc-lowlevel,  | Resolution:  fixed
  TorCoreTeam201608  |  Actual Points:
Parent ID:  #17294   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorU-can
-+-
Changes (by nickm):

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


Comment:

 I'd say this is pretty well taken care of.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19793 [Core Tor/Torsocks]: Torsocks - only torify .onion domains

[Tor Bug Tracker & Wiki]

#19793: Torsocks - only torify .onion domains
---+--
 Reporter:  klexx  |  Owner:  dgoulet
 Type:  enhancement| Status:  accepted
 Priority:  Low|  Milestone:
Component:  Core Tor/Torsocks  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by dgoulet):

 * status:  new => accepted
 * version:  Tor: unspecified =>
 * severity:  Trivial => Normal


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

Re: [tor-bugs] #19700 [Core Tor/Torsocks]: torsocks does not work with "connectx" (in netcat / nc)

[Tor Bug Tracker & Wiki]

#19700: torsocks does not work with "connectx" (in netcat / nc)
---+---
 Reporter:  egonline   |  Owner:  dgoulet
 Type:  defect | Status:  needs_information
 Priority:  High   |  Milestone:
Component:  Core Tor/Torsocks  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by dgoulet):

 * priority:  Medium => High
 * keywords:  torify torsocks =>
 * version:  Tor: unspecified =>
 * status:  new => needs_information


Comment:

 I do not have a OS X to debug nor test unfortunately... Any chance you can
 provide a `strace` output? I can't find much about `connectx()` online or
 in the OS X documentation... Do you have a man page about it? (man
 connectx)

 The more you can tell me about the syscall, the better else I can't
 support it :S.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19294 [Core Tor/Tor]: Have tor-guts cover how to use OS functionality from Tor

[Tor Bug Tracker & Wiki]

#19294: Have tor-guts cover how to use OS functionality from Tor
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
Component:  Core Tor/Tor |  0.2.9.x-final
 Severity:  Normal   |Version:
 Keywords:  tor-docs-dev, tor-doc-lowlevel,  | Resolution:  fixed
  TorCoreTeam201608  |  Actual Points:  .2
Parent ID:  #17294   | Points:  2
 Reviewer:   |Sponsor:
 |  SponsorU-can
-+-
Changes (by nickm):

 * status:  assigned => closed
 * resolution:   => fixed
 * actualpoints:   => .2


Comment:

 ok, done-enough here, covering the most important parts.  I decided that
 the most critical area to cover was the how-to-find-it stuff and the what-
 you-might-find-there stuff.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19814 [Community]: Tor Browser User Manual points users to the helpdesk

[Tor Bug Tracker & Wiki]

#19814: Tor Browser User Manual points users to the helpdesk
---+---
 Reporter:  boklm  |  Owner:  phoul
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Community  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+---
 The troubleshooting page is telling users to send an email to
 h...@rt.torproject.org:
 https://tb-manual.torproject.org/windows/en-US/troubleshooting.html

 However, I think we don't have anybody answering the help desk emails at
 the moment.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19024 [Core Tor/Tor]: prop224: Refactor rend_data_t so be able to use multiple HS version

[Tor Bug Tracker & Wiki]

#19024: prop224: Refactor rend_data_t so be able to use multiple HS version
-+
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224  |  Actual Points:
Parent ID:  #17238   | Points:  4
 Reviewer:  asn  |Sponsor:  SponsorR-must
-+

Comment (by asn):

 Replying to [comment:6 dgoulet]:
 > Replying to [comment:3 asn]:
 > > Replying to [comment:2 dgoulet]:
 > > > https://gitlab.com/dgoulet/tor/merge_requests/8
 > >
 > > I did an initial review here just to keep things rolling.
 > >
 > > I will do more review here in the future.
 >
 > Thanks for this. I've addressed your comments. See 3 new commits on top
 I pushed to the merge request. In particular, the addition of a new file
 for `rend_data_t` stuff.

 Great stuff. I did another review on that same merge request. The merge
 request has been polluted with various unrelated changes from master, but
 hopefully it's still readable.

 Code looks good here! I guess the next step here would be testing it with
 the current HS 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] #18041 [User Experience/Website]: www.torproject.org serves outdated content

[Tor Bug Tracker & Wiki]

#18041: www.torproject.org serves outdated content
-+---
 Reporter:  cypherpunks  |  Owner:  Sebastian
 Type:  defect   | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by cypherpunks):

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


Comment:

 Current www.torproject.org index.html has 2 days outdated blog list:

 {{{
 
   
   Recent Blog Posts
   Debian and
 Tor Services availabl...
   Mon, 01 Aug 2016
   Posted by: weasel
   
   Statement
   Wed, 27 Jul 2016
   Posted by: ssteele
   
   The New
 Research from Northeaste...
   Mon, 25 Jul 2016
   Posted by: arma
   
   A Quick, Simple Guide to Tor and...
   Wed, 20 Jul 2016
   Posted by: ailanthus
   
   The Tor
 Project Elects New Board...
   Wed, 13 Jul 2016
   Posted by: ailanthus
   
   
 
 }}}

 blog.torproject.org has current content:
 {{{
  Recent blog posts 
 
   Tor Browser 6.5a2 is releasedTor Browser 6.0.3 is releasedTor 0.2.8.6 is released!Debian and
 Tor Services available as Onion ServicesStatementThe New Research from Northeastern
 UniversityA Quick, Simple Guide to Tor and the Internet of Things (So
 Far)The Tor Project Elects New Board�| of
 DirectorsTor 0.2.8.5-rc
 is releasedSelfrando:  Q and A with Georg Koppenmore
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  karsten
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * type:  defect => task


Comment:

 It's a task.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  karsten
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+-
 The release process should be defined and also be applicable to other
 products.

 And release 1.0.0 will follow these steps and include all milestone 1.0.0
 tickets.

 Exact date tbd (aiming at Aug 10, 2016).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19805 [Internal Services/Tor Sysadmin Team]: provide more onion services

[Tor Bug Tracker & Wiki]

#19805: provide more onion services
-+-
 Reporter:  ilf  |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by ilf):

 More:

 * check.torproject.org
 * lists.torproject.org
 * people.torproject.org

 Found via
 http://searchdns.netcraft.com/?restriction=site+contains=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

[tor-bugs] #19812 [Applications/Tor Browser]: onion everywhere

[Tor Bug Tracker & Wiki]

#19812: onion everywhere
--+
 Reporter:  ilf   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  onion, https
Actual Points:|  everywhere
   Points:|  Parent ID:
  Sponsor:|   Reviewer:
--+
 More and more websites are offered both via HTTP(S) and onion service:

 * https://onion.debian.org/
 * https://onion.torproject.org/
 * https://riseup.net/en/security/network-security/tor#riseups-tor-hidden-
 services

 But since onion addresses are not human-meaningful, few people
 '''always''' replace onion with HTTP(S), even in Tor Browser.

 Since HTTPS Everywhere is already in Tor Browser, how about creating Onion
 Everywhere Rulesets to auto-redirect users to .onion sites instead of
 HTTP(S)?

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