Re: [tor-bugs] #23061 [Core Tor/Tor]: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int

2017-08-02 Thread Tor Bug Tracker & Wiki
#23061: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int -+- Reporter: teor | Owner: nickm Type: defect |

Re: [tor-bugs] #23083 [Obfuscation/BridgeDB]: BridgeDB gives the same bridges even to differrent IPs. It worth nothing to block the most of them.

2017-08-02 Thread Tor Bug Tracker & Wiki
#23083: BridgeDB gives the same bridges even to differrent IPs. It worth nothing to block the most of them. --+--- Reporter: cypherpunks | Owner: isis Type: defect| Status: closed

Re: [tor-bugs] #23061 [Core Tor/Tor]: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int

2017-08-02 Thread Tor Bug Tracker & Wiki
#23061: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int -+- Reporter: teor | Owner: nickm Type: defect |

Re: [tor-bugs] #23061 [Core Tor/Tor]: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int

2017-08-02 Thread Tor Bug Tracker & Wiki
#23061: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int -+- Reporter: teor | Owner: nickm Type: defect |

Re: [tor-bugs] #23061 [Core Tor/Tor]: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int

2017-08-02 Thread Tor Bug Tracker & Wiki
#23061: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int -+- Reporter: teor | Owner: nickm Type: defect |

Re: [tor-bugs] #22789 [Core Tor/Tor]: Tor 0.3.1.4-alpha crash on OpenBSD-current

2017-08-02 Thread Tor Bug Tracker & Wiki
#22789: Tor 0.3.1.4-alpha crash on OpenBSD-current -+- Reporter: fredzupy | Owner: nickm Type: defect | Status:

Re: [tor-bugs] #22926 [Core Tor/Tor]: The Tor compression code can call functions that are NULL

2017-08-02 Thread Tor Bug Tracker & Wiki
#22926: The Tor compression code can call functions that are NULL --+ Reporter: teor | Owner: ahf Type: defect| Status: assigned Priority: Medium| Milestone: Tor: 0.3.1.x-final

Re: [tor-bugs] #23080 [Core Tor/Tor]: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR

2017-08-02 Thread Tor Bug Tracker & Wiki
#23080: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR +- Reporter: dcf | Owner: Type: defect |

Re: [tor-bugs] #18628 [Obfuscation/Snowflake]: Devise some way for the browser proxy to forward metadata to the bridge before the OR data

2017-08-02 Thread Tor Bug Tracker & Wiki
#18628: Devise some way for the browser proxy to forward metadata to the bridge before the OR data ---+-- Reporter: arlolra| Owner: Type: defect | Status: needs_review Priority:

[tor-bugs] #23080 [Core Tor/Tor]: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR

2017-08-02 Thread Tor Bug Tracker & Wiki
#23080: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR --+ Reporter: dcf | Owner: Type: defect| Status: new Priority: Medium|

Re: [tor-bugs] #23047 [Internal Services/Tor Sysadmin Team]: Please add iwakeh to the onionoo, metrics, and exonerator groups

2017-08-02 Thread Tor Bug Tracker & Wiki
#23047: Please add iwakeh to the onionoo, metrics, and exonerator groups -+ Reporter: karsten | Owner: tpa Type: task | Status: closed

Re: [tor-bugs] #21321 [Applications/Tor Browser]: .onion HTTP is shown as non-secure in Tor Browser

2017-08-02 Thread Tor Bug Tracker & Wiki
#21321: .onion HTTP is shown as non-secure in Tor Browser -+- Reporter: cypherpunks | Owner: tbb- | team Type: task

Re: [tor-bugs] #23047 [Internal Services/Tor Sysadmin Team]: Please add iwakeh to the onionoo, metrics, and exonerator groups

2017-08-02 Thread Tor Bug Tracker & Wiki
#23047: Please add iwakeh to the onionoo, metrics, and exonerator groups -+ Reporter: karsten | Owner: tpa Type: task | Status: closed

[tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: Medium|

Re: [tor-bugs] #22926 [Core Tor/Tor]: The Tor compression code can call functions that are NULL

2017-08-02 Thread Tor Bug Tracker & Wiki
#22926: The Tor compression code can call functions that are NULL --+ Reporter: teor | Owner: ahf Type: defect| Status: assigned Priority: Medium| Milestone: Tor: 0.3.1.x-final

Re: [tor-bugs] #23088 [Obfuscation/BridgeDB]: >Please note that you must send the email using an address from one of the following email providers: Riseup, Gmail or Yahoo.

2017-08-02 Thread Tor Bug Tracker & Wiki
#23088: >Please note that you must send the email using an address from one of the following email providers: Riseup, Gmail or Yahoo. --+- Reporter: cypherpunks | Owner: isis Type: defect|

Re: [tor-bugs] #23086 [Obfuscation/BridgeDB]: GIMP Captcha uses insecure random number generator

2017-08-02 Thread Tor Bug Tracker & Wiki
#23086: GIMP Captcha uses insecure random number generator --+--- Reporter: cypherpunks | Owner: isis Type: defect| Status: closed Priority: Medium| Milestone:

Re: [tor-bugs] #23085 [Applications/Tor Browser]: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid

2017-08-02 Thread Tor Bug Tracker & Wiki
#23085: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid --+--- Reporter: Dbryrtfbcbhgf | Owner: tbb-team Type: defect|

Re: [tor-bugs] #23087 [Obfuscation/BridgeDB]: Get rid of GIMP in GiMP captcha

2017-08-02 Thread Tor Bug Tracker & Wiki
#23087: Get rid of GIMP in GiMP captcha --+--- Reporter: cypherpunks | Owner: isis Type: defect| Status: closed Priority: Medium| Milestone: Component:

Re: [tor-bugs] #23080 [Core Tor/Tor]: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR

2017-08-02 Thread Tor Bug Tracker & Wiki
#23080: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR +-- Reporter: dcf | Owner: Type: defect

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: needs_review

Re: [tor-bugs] #23091 [Core Tor/Tor]: Broken condition in check_expired_networkstatus_callback()

2017-08-02 Thread Tor Bug Tracker & Wiki
#23091: Broken condition in check_expired_networkstatus_callback() --+ Reporter: dgoulet | Owner: Type: defect| Status: merge_ready Priority: Medium| Milestone: Tor: 0.3.2.x-final

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed -+- Reporter: Vort | Owner: Type: defect |

[tor-bugs] #23087 [Obfuscation/BridgeDB]: Get rid of GIMP in GiMP captcha

2017-08-02 Thread Tor Bug Tracker & Wiki
#23087: Get rid of GIMP in GiMP captcha --+-- Reporter: cypherpunks | Owner: isis Type: defect| Status: new Priority: Medium| Milestone: Component:

[tor-bugs] #23089 [Obfuscation/Pluggable transport]: What if 194.132.0.0/16 and 149.202.98.0/24 get blocked?

2017-08-02 Thread Tor Bug Tracker & Wiki
#23089: What if 194.132.0.0/16 and 149.202.98.0/24 get blocked? -+- Reporter: cypherpunks | Owner: asn Type: defect | Status: new Priority: Very High

Re: [tor-bugs] #23085 [Applications/Tor Browser]: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid

2017-08-02 Thread Tor Bug Tracker & Wiki
#23085: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid --+-- Reporter: Dbryrtfbcbhgf | Owner: tbb-team Type: defect|

[tor-bugs] #23086 [Obfuscation/BridgeDB]: GIMP Captcha uses insecure random number generator

2017-08-02 Thread Tor Bug Tracker & Wiki
#23086: GIMP Captcha uses insecure random number generator --+-- Reporter: cypherpunks | Owner: isis Type: defect| Status: new Priority: Medium| Milestone: Component:

Re: [tor-bugs] #23080 [Core Tor/Tor]: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR

2017-08-02 Thread Tor Bug Tracker & Wiki
#23080: connection_ext_or_handle_cmd_useraddr and proposal 196 disagree on the format of ExtORPort USERADDR +-- Reporter: dcf | Owner: Type: defect

Re: [tor-bugs] #23082 [Core Tor/Tor]: tor_addr_parse is overly permissive

2017-08-02 Thread Tor Bug Tracker & Wiki
#23082: tor_addr_parse is overly permissive --+ Reporter: dcf | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor: 0.3.2.x-final Component: Core Tor/Tor |

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: Medium|

Re: [tor-bugs] #22926 [Core Tor/Tor]: The Tor compression code can call functions that are NULL

2017-08-02 Thread Tor Bug Tracker & Wiki
#22926: The Tor compression code can call functions that are NULL --+ Reporter: teor | Owner: ahf Type: defect| Status: assigned Priority: Medium| Milestone: Tor: 0.3.1.x-final

[tor-bugs] #23082 [Core Tor/Tor]: tor_addr_parse is overly permissive

2017-08-02 Thread Tor Bug Tracker & Wiki
#23082: tor_addr_parse is overly permissive --+ Reporter: dcf | Owner: Type: defect| Status: new Priority: Medium| Milestone: Component: Core Tor/Tor |Version: Tor:

[tor-bugs] #23084 [- Select a component]: Make all .onion services of TorProject use HTTPS over Tor to prevent MitM

2017-08-02 Thread Tor Bug Tracker & Wiki
#23084: Make all .onion services of TorProject use HTTPS over Tor to prevent MitM --+- Reporter: cypherpunks | Owner: Type: defect| Status: new Priority: Medium|

[tor-bugs] #23083 [Obfuscation/BridgeDB]: BridgeDB gives the same bridges even to differrent IPs. It worth nothing to block the most of them.

2017-08-02 Thread Tor Bug Tracker & Wiki
#23083: BridgeDB gives the same bridges even to differrent IPs. It worth nothing to block the most of them. --+-- Reporter: cypherpunks | Owner: isis Type: defect| Status: new Priority:

[tor-bugs] #23085 [Applications/Tor Browser]: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid

2017-08-02 Thread Tor Bug Tracker & Wiki
#23085: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid --+-- Reporter: Dbryrtfbcbhgf | Owner: tbb-team Type: defect|

Re: [tor-bugs] #23089 [Obfuscation/Pluggable transport]: What if 194.132.0.0/16 and 149.202.98.0/24 and 192.36.31.0/24 got blocked? (was: What if 194.132.0.0/16 and 149.202.98.0/24 and 192.36.31.0/32

2017-08-02 Thread Tor Bug Tracker & Wiki
#23089: What if 194.132.0.0/16 and 149.202.98.0/24 and 192.36.31.0/24 got blocked? -+- Reporter: cypherpunks | Owner: asn Type: defect | Status: new Priority:

Re: [tor-bugs] #23089 [Obfuscation/Pluggable transport]: What if 194.132.209.0/24 and 149.202.98.0/24 and 192.36.31.0/24 got blocked? (was: What if 194.132.0.0/16 and 149.202.98.0/24 and 192.36.31.0/2

2017-08-02 Thread Tor Bug Tracker & Wiki
#23089: What if 194.132.209.0/24 and 149.202.98.0/24 and 192.36.31.0/24 got blocked? -+- Reporter: cypherpunks | Owner: asn Type: defect | Status: new

Re: [tor-bugs] #23089 [Obfuscation/Pluggable transport]: What if 194.132.0.0/16 and 149.202.98.0/24 and 192.36.31.0/32 got blocked? (was: What if 194.132.0.0/16 and 149.202.98.0/24 get blocked?)

2017-08-02 Thread Tor Bug Tracker & Wiki
#23089: What if 194.132.0.0/16 and 149.202.98.0/24 and 192.36.31.0/32 got blocked? -+- Reporter: cypherpunks | Owner: asn Type: defect | Status: new Priority:

Re: [tor-bugs] #23082 [Core Tor/Tor]: tor_addr_parse is overly permissive

2017-08-02 Thread Tor Bug Tracker & Wiki
#23082: tor_addr_parse is overly permissive --+ Reporter: dcf | Owner: Type: defect| Status: new Priority: Medium| Milestone: Component: Core Tor/Tor |Version: Tor:

[tor-bugs] #23088 [Obfuscation/BridgeDB]: >Please note that you must send the email using an address from one of the following email providers: Riseup, Gmail or Yahoo.

2017-08-02 Thread Tor Bug Tracker & Wiki
#23088: >Please note that you must send the email using an address from one of the following email providers: Riseup, Gmail or Yahoo. --+-- Reporter: cypherpunks | Owner: isis Type: defect|

Re: [tor-bugs] #23071 [Core Tor/Tor]: test_hs_ntor.sh fails with recent pysha3

2017-08-02 Thread Tor Bug Tracker & Wiki
#23071: test_hs_ntor.sh fails with recent pysha3 -+ Reporter: nickm| Owner: nickm Type: defect | Status: needs_review Priority: Medium | Milestone: Tor: 0.3.1.x-final

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: Medium|

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed -+- Reporter: Vort | Owner: Type: defect |

Re: [tor-bugs] #23092 [Core Tor/Tor]: CircuitIdleTimeout man entry should document IDLE_TIMEOUT_WHILE_LEARNING

2017-08-02 Thread Tor Bug Tracker & Wiki
#23092: CircuitIdleTimeout man entry should document IDLE_TIMEOUT_WHILE_LEARNING --+ Reporter: teor | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor:

Re: [tor-bugs] #23092 [Core Tor/Tor]: CircuitIdleTimeout man entry should document IDLE_TIMEOUT_WHILE_LEARNING

2017-08-02 Thread Tor Bug Tracker & Wiki
#23092: CircuitIdleTimeout man entry should document IDLE_TIMEOUT_WHILE_LEARNING --+ Reporter: teor | Owner: Type: defect| Status: needs_revision Priority: Medium| Milestone: Tor:

Re: [tor-bugs] #18628 [Obfuscation/Snowflake]: Devise some way for the browser proxy to forward metadata to the bridge before the OR data

2017-08-02 Thread Tor Bug Tracker & Wiki
#18628: Devise some way for the browser proxy to forward metadata to the bridge before the OR data ---+-- Reporter: arlolra| Owner: Type: defect | Status: needs_review Priority:

[tor-bugs] #23092 [Core Tor/Tor]: CircuitIdleTimeout man entry should document IDLE_TIMEOUT_WHILE_LEARNING

2017-08-02 Thread Tor Bug Tracker & Wiki
#23092: CircuitIdleTimeout man entry should document IDLE_TIMEOUT_WHILE_LEARNING --+ Reporter: teor | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor:

Re: [tor-bugs] #22874 [Obfuscation/Snowflake]: Standalone broker (independent of App Engine)

2017-08-02 Thread Tor Bug Tracker & Wiki
#22874: Standalone broker (independent of App Engine) ---+-- Reporter: dcf| Owner: cmm32 Type: project| Status: assigned Priority: High | Milestone:

Re: [tor-bugs] #22343 [Applications/Tor Browser]: Save as... in the context menu results in using the catch-all circuit

2017-08-02 Thread Tor Bug Tracker & Wiki
#22343: Save as... in the context menu results in using the catch-all circuit -+- Reporter: gk | Owner: | arthuredelstein

Re: [tor-bugs] #18628 [Obfuscation/Snowflake]: Devise some way for the browser proxy to forward metadata to the bridge before the OR data

2017-08-02 Thread Tor Bug Tracker & Wiki
#18628: Devise some way for the browser proxy to forward metadata to the bridge before the OR data ---+-- Reporter: arlolra| Owner: Type: defect | Status: needs_review Priority:

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: Medium|

Re: [tor-bugs] #23085 [Applications/Tor Browser]: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid

2017-08-02 Thread Tor Bug Tracker & Wiki
#23085: Clicking on Test Tor Network Settings and then click the back button and I get this error The address isn’t valid --+--- Reporter: Dbryrtfbcbhgf | Owner: tbb-team Type: defect|

Re: [tor-bugs] #23090 [Core Tor/Tor]: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32

2017-08-02 Thread Tor Bug Tracker & Wiki
#23090: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32 --+ Reporter: teor | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor: 0.3.2.x-final

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: Medium|

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: Medium|

Re: [tor-bugs] #23089 [Obfuscation/Pluggable transport]: What if 194.132.209.0/24 and 149.202.98.0/24 and 192.36.31.0/24 got blocked?

2017-08-02 Thread Tor Bug Tracker & Wiki
#23089: What if 194.132.209.0/24 and 149.202.98.0/24 and 192.36.31.0/24 got blocked? -+- Reporter: cypherpunks | Owner: asn Type: defect | Status: closed

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: High

Re: [tor-bugs] #23090 [Core Tor/Tor]: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32

2017-08-02 Thread Tor Bug Tracker & Wiki
#23090: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32 --+ Reporter: teor | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor: 0.3.2.x-final

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: High

Re: [tor-bugs] #21948 [Applications/Tor Browser]: Going back to about:tor page gives a "The address isn’t valid"-error

2017-08-02 Thread Tor Bug Tracker & Wiki
#21948: Going back to about:tor page gives a "The address isn’t valid"-error -+- Reporter: gk | Owner: mcs Type: defect | Status:

Re: [tor-bugs] #23089 [Obfuscation/Pluggable transport]: What if 194.132.209.0/24 and 149.202.98.0/24 and 192.36.31.0/24 got blocked?

2017-08-02 Thread Tor Bug Tracker & Wiki
#23089: What if 194.132.209.0/24 and 149.202.98.0/24 and 192.36.31.0/24 got blocked? -+- Reporter: cypherpunks | Owner: asn Type: defect | Status: new

[tor-bugs] #23090 [Core Tor/Tor]: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32

2017-08-02 Thread Tor Bug Tracker & Wiki
#23090: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32 --+ Reporter: teor | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor: 0.3.2.x-final

Re: [tor-bugs] #23071 [Core Tor/Tor]: test_hs_ntor.sh fails with recent pysha3

2017-08-02 Thread Tor Bug Tracker & Wiki
#23071: test_hs_ntor.sh fails with recent pysha3 -+ Reporter: nickm| Owner: nickm Type: defect | Status: needs_revision Priority: Medium | Milestone: Tor:

Re: [tor-bugs] #23071 [Core Tor/Tor]: test_hs_ntor.sh fails with recent pysha3

2017-08-02 Thread Tor Bug Tracker & Wiki
#23071: test_hs_ntor.sh fails with recent pysha3 -+ Reporter: nickm| Owner: nickm Type: defect | Status: needs_review Priority: Medium | Milestone: Tor: 0.3.1.x-final

Re: [tor-bugs] #23061 [Core Tor/Tor]: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int

2017-08-02 Thread Tor Bug Tracker & Wiki
#23061: crypto_rand_double() should produce all possible outputs on platforms with 32-bit int -+- Reporter: teor | Owner: nickm Type: defect |

Re: [tor-bugs] #22876 [Internal Services/Service - trac]: The cypherpunks account can be deleted by everyone

2017-08-02 Thread Tor Bug Tracker & Wiki
#22876: The cypherpunks account can be deleted by everyone --+--- Reporter: cypherpunks | Owner: qbi Type: task | Status: closed Priority: Medium

Re: [tor-bugs] #22876 [Internal Services/Service - trac]: The cypherpunks account can be deleted by everyone

2017-08-02 Thread Tor Bug Tracker & Wiki
#22876: The cypherpunks account can be deleted by everyone --+--- Reporter: cypherpunks | Owner: qbi Type: task | Status: closed Priority: Medium

Re: [tor-bugs] #23089 [Obfuscation/Pluggable transport]: What if 0.0.0.0/0 got blocked? (was: What if 194.132.209.0/24 and 149.202.98.0/24 and 192.36.31.0/24 got blocked?)

2017-08-02 Thread Tor Bug Tracker & Wiki
#23089: What if 0.0.0.0/0 got blocked? -+- Reporter: cypherpunks | Owner: asn Type: defect | Status: closed Priority: Very High|

Re: [tor-bugs] #23088 [Obfuscation/BridgeDB]: >Please note that you must send the email using an address from one of the following email providers: Riseup, Gmail or Yahoo.

2017-08-02 Thread Tor Bug Tracker & Wiki
#23088: >Please note that you must send the email using an address from one of the following email providers: Riseup, Gmail or Yahoo. --+-- Reporter: cypherpunks | Owner: isis Type: defect|

Re: [tor-bugs] #23090 [Core Tor/Tor]: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32

2017-08-02 Thread Tor Bug Tracker & Wiki
#23090: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32 -+- Reporter: teor | Owner: Type: defect | Status: new

Re: [tor-bugs] #23064 [Applications/Tor Browser]: Tor doesn't open on OS X anymore

2017-08-02 Thread Tor Bug Tracker & Wiki
#23064: Tor doesn't open on OS X anymore --+--- Reporter: nirvanh | Owner: tbb-team Type: defect| Status: needs_information Priority: Very High |

Re: [tor-bugs] #23082 [Core Tor/Tor]: tor_addr_parse is overly permissive

2017-08-02 Thread Tor Bug Tracker & Wiki
#23082: tor_addr_parse is overly permissive --+ Reporter: dcf | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor: 0.3.2.x-final Component: Core Tor/Tor |

Re: [tor-bugs] #23071 [Core Tor/Tor]: test_hs_ntor.sh fails with recent pysha3

2017-08-02 Thread Tor Bug Tracker & Wiki
#23071: test_hs_ntor.sh fails with recent pysha3 -+ Reporter: nickm| Owner: nickm Type: defect | Status: closed Priority: Medium | Milestone: Tor: 0.3.1.x-final

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: High

[tor-bugs] #23091 [Core Tor/Tor]: Broken condition in check_expired_networkstatus_callback()

2017-08-02 Thread Tor Bug Tracker & Wiki
#23091: Broken condition in check_expired_networkstatus_callback() --+ Reporter: dgoulet | Owner: Type: defect| Status: new Priority: Medium| Milestone: Tor: 0.3.2.x-final

Re: [tor-bugs] #23091 [Core Tor/Tor]: Broken condition in check_expired_networkstatus_callback()

2017-08-02 Thread Tor Bug Tracker & Wiki
#23091: Broken condition in check_expired_networkstatus_callback() --+ Reporter: dgoulet | Owner: Type: defect| Status: needs_review Priority: Medium| Milestone: Tor: 0.3.2.x-final

Re: [tor-bugs] #23081 [Core Tor/Tor]: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed

2017-08-02 Thread Tor Bug Tracker & Wiki
#23081: Tor relay crashes at consensus_diff_queue_diff_work() with assertion in_main_thread() failed --+ Reporter: Vort | Owner: Type: defect| Status: new Priority: High

Re: [tor-bugs] #23075 [Applications/Tor Browser]: Add an option to select the number of cores used for building in tor-browser-build.git

2017-08-02 Thread Tor Bug Tracker & Wiki
#23075: Add an option to select the number of cores used for building in tor- browser-build.git --+ Reporter: boklm | Owner: boklm Type: task | Status: closed Priority:

Re: [tor-bugs] #23091 [Core Tor/Tor]: Broken condition in check_expired_networkstatus_callback()

2017-08-02 Thread Tor Bug Tracker & Wiki
#23091: Broken condition in check_expired_networkstatus_callback() --+ Reporter: dgoulet | Owner: Type: defect| Status: needs_review Priority: Medium| Milestone: Tor: 0.3.2.x-final