Respected all,
Can I know the issues that are currently in https everywhere.
On 09/05/2016 12:58 PM, AKASH DAS wrote:
Can I know the issues that are currently in https everywhere.
This is the mailing list for Tor development, so you may want to redirect your question to the EFF or some different channel.
HTTPS Everywhere has been really smooth for me and I've actually never had an issue with it across many devices and several years. I know that some websites don't handle HTTPS correctly, but that's why the EFF built the tool based on a carefull-managed whitelist. If almost all of your common websites are using HTTPS, then you might even consider enabling the "Block all unencrypted requests" option, but then don't be surprised when your favorite news site no longer loads. The situation is really improving thanks to Let's Encrypt. :)
On Mon, Sep 05, 2016 at 10:28:26PM +0530, AKASH DAS wrote:
Can I know the issues that are currently in https everywhere.
I don't know if this is what you're looking for, but here are some open bug tracker tickets.
https://trac.torproject.org/projects/tor/query?status=!closed&component=... https://trac.torproject.org/projects/tor/query?status=!closed&component=...
If I have to make any patch in the code, do I have to submit it in this mailing list or https-everywhere's mailing list? Just a doubt
On Mon, Sep 5, 2016 at 10:35 PM, David Fifield david@bamsoftware.com wrote:
On Mon, Sep 05, 2016 at 10:28:26PM +0530, AKASH DAS wrote:
Can I know the issues that are currently in https everywhere.
I don't know if this is what you're looking for, but here are some open bug tracker tickets.
https://trac.torproject.org/projects/tor/query?status=! closed&component=HTTPS+Everywhere%2FEFF-HTTPS+Everywhere https://trac.torproject.org/projects/tor/query?status=! closed&component=HTTPS+Everywhere%2FHTTPS+Everywhere%3A+Chrome
On 09/05/2016 01:19 PM, AKASH DAS wrote:
If I have to make any patch in the code, do I have to submit it in this mailing list or https-everywhere's mailing list? Just a doubt
What are you trying to patch? If you are trying to add a URL to their whitelist, you don't need to submit a patch as they have a tool for that. Otherwise, I am not certain how they accept git patches.
Per convention, please reply below the original message instead of above it.