Custom Query (26254 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (103 - 105 of 26254)

Ticket Resolution Summary Owner Reporter
#4836 fixed Google Images search plugin fails OsamaK Anomie
Description

The Google Images search plugins from http://mycroft.mozdev.org/search-engines.html?name=images.google.com seem to send to addresses along the lines of http://images.google.com/images?q=$1. The current HTTPS Everywhere rules for some reason redirect this to https://encrypted.google.com/imghpimages?q=$1 (which gives an error), instead of something like https://encrypted.google.com/images?q=$1 that would actually work.

#25662 duplicate OBSOLETE OLD TOR CRYPTO AND ONLY RESOLVE OLD .ONION ADDRESSES Anony
Description

I think it would be best to completely obsolete all the old crypto within TOR, but if it is possible to only use it to resolve old .onion addresses and NOT to build new circuits EVER.

This would essentially be a firewall inside Tor to start only building circuits by default using the New Encryption introduced in Tor 0.3.2.9

There has been enough time elapsed for operators to upgrade and this is a serious bug if TOR is building obsolete circuits with obsolete TOR nodes. Thus the Default and Only setting should be to only build circuits using the Newer Encryption standard now that enough relays are already using the newer nodes.

#25682 duplicate Obsolete Tor Core Encryption, Only use SHA3/ed25519/curve25519 for building Circuits Anony
Description

a) Better crypto (replaced SHA1/DH/RSA1024 with SHA3/ed25519/curve25519)

Don't allow New Tor nodes to build circuits with obsolete Tor Nodes unless they support the newer encryption version 0.3.2.9 - 2018-01-09

Only use the old crypto to resolve old .Onion honeypots...........

Only use SHA3/ed25519/curve25519 to build New 3 hop Circuits. This will provide better anon for hidden services which use the same transport system.

Note: See TracQuery for help on using queries.