Re: [tor-bugs] #19858 [Core Tor/Tor]: Move guard state out of globals per new guard plan

[Tor Bug Tracker & Wiki]

#19858: Move guard state out of globals per new guard plan
--+
 Reporter:  andrea|  Owner:  andrea
 Type:  task  | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  6
Parent ID:  #19877| Points:  3
 Reviewer:|Sponsor:  SponsorU-must
--+
Changes (by andrea):

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


Comment:

 This is done in my ticket19858 branch now.  For now existing calls into
 entryguards.c just use the default guard context; later on we'll need to
 figure out which call sites care about using a particular one once we have
 particular ones.

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

Re: [tor-bugs] #20235 [Core Tor/Tor]: Configure misidentifies clock_gettime and getentropy on macOS Sierra/XCode8 when compiling for iOS 8

[Tor Bug Tracker & Wiki]

#20235: Configure misidentifies clock_gettime and getentropy on macOS 
Sierra/XCode8
when compiling for iOS 8
-+-
 Reporter:  rainwolf |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.8
 Severity:  Normal   | Resolution:
 Keywords:  Sierra, XCode 8, clock_gettime,  |  Actual Points:
  getentropy, libSystem.dylib 028-backport osx   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Oh!  Hm.

 I tried making an example program as small as possible to still use
 getentropy():
 {{{
 #include 
 #include 
 #include 

 int main(int argc, char **argv)
 {
   unsigned x;
   if (getentropy(, sizeof(x)) < 0)
 perror("getentropy");
   else
 printf("%u\n", x);
   return 0;
 }
 }}}

 I tried compiling it in lots of different ways, but I couldn't find a way
 to tell gcc to ignore the presence of getentropy()
 {{{
 % gcc -Wall -Wl,-no_weak_imports getentropy_test.c -o get
 % gcc -Wall -mmacosx-version-min=10.10 -Wl,-no_weak_imports
 getentropy_test.c -o get
 % ( export MACOSX_DEPLOYMENT_TARGET=10.10 ; gcc -Wall -mmacosx-version-
 min=10.10 -Wl,-no_weak_imports getentropy_test.c -o get )
 }}}

 I wonder if Apple messed up somehow and forgot to tag these APIs as 10.12
 only?  Or maybe I'm doing something wrong with the above.

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

Re: [tor-bugs] #20235 [Core Tor/Tor]: Configure misidentifies clock_gettime and getentropy on macOS Sierra/XCode8 when compiling for iOS 8

[Tor Bug Tracker & Wiki]

#20235: Configure misidentifies clock_gettime and getentropy on macOS 
Sierra/XCode8
when compiling for iOS 8
-+-
 Reporter:  rainwolf |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.8
 Severity:  Normal   | Resolution:
 Keywords:  Sierra, XCode 8, clock_gettime,  |  Actual Points:
  getentropy, libSystem.dylib 028-backport osx   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:
 Sierra, XCode 8, clock_gettime, getentropy, libSystem.dylib
 028-backport
 =>
 Sierra, XCode 8, clock_gettime, getentropy, libSystem.dylib
 028-backport osx
 * component:  Core Tor => Core Tor/Tor


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

Re: [tor-bugs] #20235 [Core Tor]: Configure misidentifies clock_gettime and getentropy on macOS Sierra/XCode8 when compiling for iOS 8

[Tor Bug Tracker & Wiki]

#20235: Configure misidentifies clock_gettime and getentropy on macOS 
Sierra/XCode8
when compiling for iOS 8
-+-
 Reporter:  rainwolf |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor |Version:  Tor:
 |  0.2.8.8
 Severity:  Normal   | Resolution:
 Keywords:  Sierra, XCode 8, clock_gettime,  |  Actual Points:
  getentropy, libSystem.dylib 028-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  Sierra, XCode 8, clock_gettime, getentropy, libSystem.dylib =>
 Sierra, XCode 8, clock_gettime, getentropy, libSystem.dylib
 028-backport
 * milestone:   => Tor: 0.2.9.x-final


Comment:

 (#20241 is related to this, but not the same.)

 Does Apple provide a general way to target a specific version of their
 APIs, other than downgrading your developer tools?

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

Re: [tor-bugs] #20241 [Core Tor/Tor]: Fix compilation on osx sierra (10.12)

[Tor Bug Tracker & Wiki]

#20241: Fix compilation on osx sierra (10.12)
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  osx TorCoreTeam201609  |  Actual Points:  .1
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by nickm):

 * status:  new => assigned
 * keywords:  osx => osx TorCoreTeam201609
 * owner:   => nickm
 * actualpoints:   => .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] #20241 [Core Tor/Tor]: Fix compilation on osx sierra (10.12)

[Tor Bug Tracker & Wiki]

#20241: Fix compilation on osx sierra (10.12)
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  osx TorCoreTeam201609  |  Actual Points:  .1
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by nickm):

 * status:  assigned => 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] #20241 [Core Tor/Tor]: Fix compilation on osx sierra (10.12)

[Tor Bug Tracker & Wiki]

#20241: Fix compilation on osx sierra (10.12)
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  osx
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 OSX Sierra (which came out last week) broke compilation in two ways:

* It added a getentropy() function, but only if you include
 sys/random.h (which nobody else seems to require).
* It added clock_gettime(), but uses a wider type for tv_nsec than
 tv_usec (why? Where does apple run that provides an "int" that holds up to
 1e6, but where you need a "long" to hold 1e9??).
* It added clock_gettime(), but didn't add pthread_condattr_setclock()
 (whereas everybody else supports neither or both).

 My branch `osx_sierra_028` fixes both.  I'm going to merge it to master as
 low-risk so I can keep doing development, and ask for review on getting it
 into 028.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20240 [Applications/Tor Browser]: Set ASan verbosity on --debug (hardened browser)

[Tor Bug Tracker & Wiki]

#20240: Set ASan verbosity on --debug (hardened browser)
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 start-tor-browser supports --debug/--verbose. Please set "verbosity" in
 $ASAN_OPTIONS when it's used, given the history of problems with that
 feature.

 related: #20238, #20237, #19851

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20239 [Applications/Tor Browser]: Tor Browser should print error messages on startup failure

[Tor Bug Tracker & Wiki]

#20239: Tor Browser should print error messages on startup failure
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 This is related to #20238 (and #20237 and #19851). When the Browser failed
 to start, it produced absolutely no output. It just exited with an error
 status like 134, which luckily I was able to see because my $PS1 includes
 $?.

 I understand you don't want the browser leaking data into .xsession-errors
 or whatever, but this is clearly not the ideal way to do it. Nobody who's
 unfamiliar with Unix debugging would figure out what's happening.

 Could you redirect these fds later in the startup process? I don't know if
 the Browser uses fork()--it would have to happen before that, and
 obviously before any network access might happen. You'd need to do
 something like this in the C code:
 fd=open("/dev/null",O_WRONLY|O_CLOEXEC); dup2(fd, 1); dup2(fd, 2);
 close(fd); but with proper error checking.

 Even better, write a wrapper process that does *not* use ASan or other
 experimental features, that will execute the browser and pop a GUI window
 with stdout/stderr text on a nonzero exit status. And offer to restart it,
 like the Browser does when Tor crashes. Maybe even try to detect what's
 wrong--using the error text, or exit status, or by "unit-testing" some
 features that have caused trouble in the past--and work around it or
 suggest the fix.

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

[tor-bugs] #20238 [Applications/Tor Browser]: Hardened browser should have a way to disable ASan

[Tor Bug Tracker & Wiki]

#20238: Hardened browser should have a way to disable ASan
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 I've been hit twice recently by Address Sanitizer bugs (#20237, #19851).
 It's always a huge pain to figure out what's happening, and then to work
 around it. I had to grab an old glibc and hack around with $LD_PRELOAD for
 one, screw around with ulimits for the other. And I need to boot a Tails
 VM to get a working browser to search for the error messages (which aren't
 even printed by default), and then copy/paste is difficult.

 start-tor-browser should have a documented option to disable ASan. And the
 script shouldn't just clobber ASAN_OPTIONS if it's set, because that just
 complicates debugging (prepend/append your string instead).

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

Re: [tor-bugs] #20237 [Applications/Tor Browser]: Hardened browser gets ASan failure after upgrading to Linux 4.7.4

[Tor Bug Tracker & Wiki]

#20237: Hardened browser gets ASan failure after upgrading to Linux 4.7.4
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

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


Comment:

 Linux has been letting people set RLIMIT_DATA forever... but didn't really
 implement it until May 2016‽‽‽:
 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f4fcd55841fc9e46daac553b39361572453c2b88

 I'll close 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] #20228 [Metrics/CollecTor]: Append all votes with same valid-after time to a single file in `recent/`

[Tor Bug Tracker & Wiki]

#20228: Append all votes with same valid-after time to a single file in 
`recent/`
---+-
 Reporter:  karsten|  Owner:
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 This is a very useful suggestion!
 And, we should make it part of the first protocol version (#20234).
 A timely notice about that change should be ok?

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

Re: [tor-bugs] #20234 [Metrics/CollecTor]: Agree on common directory structure for CollecTor's web page

[Tor Bug Tracker & Wiki]

#20234: Agree on common directory structure for CollecTor's web page
---+-
 Reporter:  karsten|  Owner:
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 I would suggest changing the title of this ticket to "Define CollecTor's
 file-structure protocol 1.0".

 For distribution  we depend on that file structure and third parties
 downloading data also need something to rely on. So, this protocol
 description should be part of the Collector data description.

 The three folders `recent`, `archive`, and `index` are a good basis for
 the protocol. Thus, we don't need to write about any other files in the
 root directory. And, these folders can be liberally placed wherever on the
 physical/virtual machine a CollecTor admin sees them fit as long as they
 show up under the CollecTor root. And, the html-files can be even in a
 different place (which is the case on the mirror).

 Summary:
 * define CollecTor protocol 1.0
 * using the three folders `recent`, `archive`, and `index` as top folders
 * describe the substructure as it is hard-coded now.

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

Re: [tor-bugs] #20237 [Applications/Tor Browser]: Hardened browser gets ASan failure after upgrading to Linux 4.7.4

[Tor Bug Tracker & Wiki]

#20237: Hardened browser gets ASan failure after upgrading to Linux 4.7.4
--+--
 Reporter:  cypherpunks   |  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 cypherpunks):

 "ulimit -d unlimited" fixes the problem. The other limits are still set.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20237 [Applications/Tor Browser]: Hardened browser gets ASan failure after upgrading to Linux 4.7.4

[Tor Bug Tracker & Wiki]

#20237: Hardened browser gets ASan failure after upgrading to Linux 4.7.4
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 The hardened Tor browser 6.5a3 stopped working after I upgraded my Debian
 system to kernel version "4.7.0-1-amd64 #1 SMP Debian 4.7.4-2 (2016-09-19)
 x86_64 GNU/Linux" (from 4.6.4-1). I get the following:
 {{{
 ==6701==Parsed ASAN_OPTIONS: detect_leaks=0:verbosity=999
 ==6701==AddressSanitizer: failed to intercept '__isoc99_printf'
 ==6701==AddressSanitizer: failed to intercept '__isoc99_sprintf'
 ==6701==AddressSanitizer: failed to intercept '__isoc99_snprintf'
 ==6701==AddressSanitizer: failed to intercept '__isoc99_fprintf'
 ==6701==AddressSanitizer: failed to intercept '__isoc99_vprintf'
 ==6701==AddressSanitizer: failed to intercept '__isoc99_vsprintf'
 ==6701==AddressSanitizer: failed to intercept '__isoc99_vsnprintf'
 ==6701==AddressSanitizer: failed to intercept '__isoc99_vfprintf'
 ==6701==AddressSanitizer: libc interceptors initialized
 || `[0x10007fff8000, 0x7fff]` || HighMem||
 || `[0x02008fff7000, 0x10007fff7fff]` || HighShadow ||
 || `[0x8fff7000, 0x02008fff6fff]` || ShadowGap  ||
 || `[0x7fff8000, 0x8fff6fff]` || LowShadow  ||
 || `[0x, 0x7fff7fff]` || LowMem ||
 MemToShadow(shadow): 0x8fff7000 0x91ff6dff 0x004091ff6e00
 0x02008fff6fff
 redzone=16
 max_redzone=2048
 quarantine_size=256M
 malloc_context_size=30
 SHADOW_SCALE: 3
 SHADOW_GRANULARITY: 8
 SHADOW_OFFSET: 7fff8000
 ==6701==ERROR: AddressSanitizer failed to allocate 0xdfff0001000
 (15392894357504) bytes at address 2008fff7000 (errno: 12)
 ==6701==ReserveShadowMemoryRange failed while trying to map 0xdfff0001000
 bytes. Perhaps you're using ulimit -v
 }}}

 I have "ulimit -v" set to unlimited, "ulimit -d" to 8G, "ulimit -s" to 8M,
 "ulimit -m" to 1.5G. Browser 6.5a2-hardened fails the same way.

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

Re: [tor-bugs] #17754 [Core Tor/Tor]: 0.2.7.5 cannot work inside lxc container

[Tor Bug Tracker & Wiki]

#17754: 0.2.7.5 cannot work inside lxc container
--+---
 Reporter:  kibba |  Owner:
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:  Tor: 0.2.7.5
 Severity:  Normal| Resolution:
 Keywords:  lxc   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by PZajda):

 * cc: patrick@… (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] #20236 [Metrics/CollecTor]: Make changes to bridgedescs module for bulk-processing tarballs

[Tor Bug Tracker & Wiki]

#20236: Make changes to bridgedescs module for bulk-processing tarballs
---+-
 Reporter:  karsten|  Owner:
 Type:  enhancement| Status:  new
 Priority:  Low|  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by karsten):

 New branch: https://gitweb.torproject.org/karsten/metrics-
 db.git/log/?h=task-20236

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20236 [Metrics/CollecTor]: Make changes to bridgedescs module for bulk-processing tarballs

[Tor Bug Tracker & Wiki]

#20236: Make changes to bridgedescs module for bulk-processing tarballs
---+-
 Reporter:  karsten|  Owner:
 Type:  enhancement| Status:  new
 Priority:  Low|  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+-
 I recently finished re-processing the entire bridge descriptor archive for
 #19317.  However, I had to make some changes to avoid running out of
 memory or wasting time on unnecessary operations.  I now went through the
 changes and cleaned them up a bit, because I'd like to merge some/most/all
 (?) of them for the next time we need to bulk-process the bridge
 descriptor archive.  I'll post a branch once I have a ticket number.

 We should discuss which of these commits should go in by default (maybe
 ed48f03, ae5c53c, and e514d30?), which should only be enabled in a special
 bulk-processing mode (maybe df96751, 27cbfc8, and 68b29c2?), which should
 have their own config option (ugh!), or which we drop because we don't
 need as badly for processing descriptors in bulk.

 Clearly, these commits need work, but I figured it's better to clean them
 up a bit now than attempt to do that in four or eight weeks.  Branch
 follows in a minute.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20235 [Core Tor]: Configure misidentifies clock_gettime and getentropy on macOS Sierra/XCode8 when compiling for iOS 8

[Tor Bug Tracker & Wiki]

#20235: Configure misidentifies clock_gettime and getentropy on macOS 
Sierra/XCode8
when compiling for iOS 8
-+-
 Reporter:   |  Owner:
  rainwolf   |
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core |Version:  Tor: 0.2.8.8
  Tor|   Keywords:  Sierra, XCode 8, clock_gettime,
 Severity:  Normal   |  getentropy, libSystem.dylib
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 libSystem.dylib provides clock_gettime and getentropy from iOS 10 onward
 but not below but the configure script does not detect that. Even with the
 `-Wl,-no_weak_imports`

 linker flag. The only way I managed to compile for iOS8 and iOS9 on macOS
 Sierra with XCode8 was to patch out detection of clock_gettime and
 getentropy from the configure script. This is less-than-ideal but the only
 fix I know. I attached the patch that I used on configure.

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

Re: [tor-bugs] #19501 [User Experience/Website]: deprecate torproject's RPM repository

[Tor Bug Tracker & Wiki]

#19501: deprecate torproject's RPM repository
-+---
 Reporter:  cypherpunks  |  Owner:  Sebastian
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by Sebastian):

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


Comment:

 thank you!

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

Re: [tor-bugs] #18911 [User Experience/Website]: bitcoin donations via BitPay don't work properly for tor users (BitPay uses Cloudflare)

[Tor Bug Tracker & Wiki]

#18911: bitcoin donations via BitPay don't work properly for tor users (BitPay 
uses
Cloudflare)
-+---
 Reporter:  cypherpunks  |  Owner:  Sebastian
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:  invalid
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by Sebastian):

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


Comment:

 This is not really a website ticket, instead it should be brought up with
 the execdir. The website only reflects what Tor as an org is supporting
 atm. I'm sorry I don't have a better solution for you

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

Re: [tor-bugs] #19930 [User Experience/Website]: web site menu needlessly jumps around

[Tor Bug Tracker & Wiki]

#19930: web site menu needlessly jumps around
-+---
 Reporter:  chadmiller   |  Owner:  Sebastian
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Minor| Resolution:
 Keywords:  defer-new-website|  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by Sebastian):

 * keywords:   => defer-new-website


Comment:

 Yep, this is really annoying. Defering it to website redesign, however.

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

Re: [tor-bugs] #20125 [User Experience/Website]: Tor Mirror Update as of 9/9/2016

[Tor Bug Tracker & Wiki]

#20125: Tor Mirror Update as of 9/9/2016
-+---
 Reporter:  aquintex |  Owner:  Sebastian
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor mirror   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by Sebastian):

 Hi, you mentioned you wanted to prepare an update, what's the status on
 that? Should I still 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] #19933 [User Experience/Website]: Debian/Ubuntu instructions need updating

[Tor Bug Tracker & Wiki]

#19933: Debian/Ubuntu instructions need updating
-+---
 Reporter:  ln5  |  Owner:  Sebastian
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by Sebastian):

 * 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