I can recommend https://addons.mozilla.org/de/firefox/addon/https-finder/ as addition to HTTPS Everywhere.
HTTPS Finder automatically checks for https availability and can create a ruleset for HTTPS Everywhere if desired.
Topic: HTTPS Everywhere - Rulesets for bitcoin.org etc. (Read 9310 times)
We need a update of these rules... hmm maybe i'll do it. 
It works!
Thanks OP
Thanks OP
Hm, my mining.bitcoin.cz rule seems to be wrong, buit I can't see the mistake.
Can anybody please check that ?
Can anybody please check that ?
Connection is encrypted either way, so your ISP does not know what you are doing here.
Updated ruleset that works for old bitcoin.org/smf/ related links also!
http://www.bitcoinservice.co.uk/files/875
Thanks http://www.bitcoinservice.co.uk/files/875
as long as no issued/signed SSL certificate for bitcoin.org [who trust unsigned/self-signed ? and what for ?] what point in it ?
p.s.
sorry for [probably]stupid qustion.
p.s.
sorry for [probably]stupid qustion.
Updated ruleset that works for old bitcoin.org/smf/ related links also!
Version 0.6
http://www.bitcoinservice.co.uk/files/875
File is free... just refresh the page.
Version 0.6
http://www.bitcoinservice.co.uk/files/875
File is free... just refresh the page.
Try adding deepbit.net too.
Done.Update
- renamed bitcoin.xml to forum.bitcoin.org.xml
- added support for deepbit.net
Link:
http://stm.square7.ch/files/rules-v5.zip
Try adding deepbit.net too.
Thank you!
- removed support for bitcoin.org main page (has no SSL support anymore)
- added support for the bitcoin.org forum (forum.bitcoin.org still has SSL)
Link:
http://stm.square7.ch/files/rules-v4.zip
new version below.
Attention: Do not use my rulesets until the next update !
Due to the recent changes to the bitcoin.org site the site and forum are NOT reachable when my ruleset is enabled.
I will try to update the set later that day.
Due to the recent changes to the bitcoin.org site the site and forum are NOT reachable when my ruleset is enabled.
I will try to update the set later that day.
Thanx, SmokeTooMuch
I added thepiratebay to your list. Hope you don't mind
https://rapidshare.com/files/458673279/Archive.zip
I added thepiratebay to your list. Hope you don't mind
https://rapidshare.com/files/458673279/Archive.zip
- Slushs pool site mining.bitcoin.cz
- Bitcoin Faucet freebitcoins.appspot.com
- alloscomp.com
Download:
http://stm.square7.ch/files/rules-v3.zip
new version below.
Thanks Vasilev!
I was aware of some mistakes but I was too lazy to fix them and the community didn't repsond very much to this.
I was aware of some mistakes but I was too lazy to fix them and the community didn't repsond very much to this.
A number of your rules have extra slash at end of the to= string. This leads to 404 when going to e.g. (bitcoin2cc.com/faq.php).
I have fixed that. Other changes:
* Forced www.bitcoin.org instead of just bitcoin.org. The certificate is self-signed for the www domain, and forcing it wrongly prevents me from using Perspectives to bypass the warning.
* Removed targethost vekja.net from Mullvad rule. It is already always HTTPS.
* Added targethost mullvad.net to Mullvad rule. It is a valid target but not included.
* Cosmetic changes to better follow EFF rules.
I have done a bare minimum of testing on these rules and they all work for the frontpages.
Here are new rules, .7z:
https://sovietpride.su/stf/lgbtf/HTEv2.7z
sha256: a196848a0e5768843d6b8fb80cf43144cf00d68a36f7e4700ec82aee195a6d54
md5: 9cb3250df1f3f36170191ea81de49a71
or in .tar.xz
https://sovietpride.su/stf/lgbtf/HTEv2.tar.xz
sha256: ea469b0c50d8d6f5469b22fbdf35b4315f9da8b60ea489996907b6eaf7b32aa0
md5: e7a69d10b18fb251cf42fc17d9b232ad
More people should be using HTTPSEverywhere.
// Perspectives is also nice if you don't mind it sending certain hosts to their servers (via https) to check on its certificate status. I have mine set to paranoid settings: check all HTTPS, not just unsigned; 75% agreement; certificate has been seen consistently for 7 days.
PS: Easier way to find Firefox profile on Windows is just to paste "%appdata%\Mozilla\Firefox\Profiles" into Explorer and hit enter.
I have fixed that. Other changes:
* Forced www.bitcoin.org instead of just bitcoin.org. The certificate is self-signed for the www domain, and forcing it wrongly prevents me from using Perspectives to bypass the warning.
* Removed targethost vekja.net from Mullvad rule. It is already always HTTPS.
* Added targethost mullvad.net to Mullvad rule. It is a valid target but not included.
* Cosmetic changes to better follow EFF rules.
I have done a bare minimum of testing on these rules and they all work for the frontpages.
Here are new rules, .7z:
https://sovietpride.su/stf/lgbtf/HTEv2.7z
sha256: a196848a0e5768843d6b8fb80cf43144cf00d68a36f7e4700ec82aee195a6d54
md5: 9cb3250df1f3f36170191ea81de49a71
or in .tar.xz
https://sovietpride.su/stf/lgbtf/HTEv2.tar.xz
sha256: ea469b0c50d8d6f5469b22fbdf35b4315f9da8b60ea489996907b6eaf7b32aa0
md5: e7a69d10b18fb251cf42fc17d9b232ad
More people should be using HTTPSEverywhere.
// Perspectives is also nice if you don't mind it sending certain hosts to their servers (via https) to check on its certificate status. I have mine set to paranoid settings: check all HTTPS, not just unsigned; 75% agreement; certificate has been seen consistently for 7 days.
Also seems like encryption isn't working on the whole site, somehow that doesnt make sense (to me).
Certain images are served via HTTP, thus causing a minor security issue. Browsers flag this. View the source and search for "src="http://" to see.PS: Easier way to find Firefox profile on Windows is just to paste "%appdata%\Mozilla\Firefox\Profiles" into Explorer and hit enter.
yup, I'm trying to figure it out myself. Not sure what Drupal is doing.
Hmm, seems like the site autmatically forwards http requests(port 80) to https.
Also seems like encryption isn't working on the whole site, somehow that doesnt make sense (to me).
Also seems like encryption isn't working on the whole site, somehow that doesnt make sense (to me).
Yay, got it to work !
Feel free to download.
Feel free to download.
Jump to: