Author Topic: Possibility of using HTTPS as default for https enabled sites and proxies  (Read 5945 times)

Offline ID101

  • Black Box Tester
  • Jr. Member
  • **
  • Posts: 73
  • Karma: +3/-0
    • View Profile
Bit CheTM has https support, why don't we use it by default in scripts?

We can change all piratenpartij.nl search links to scrips to https
or at least adding aditional https line for each supported site

https://proxy.piratenpartij.nl/site url here

Reasons:
  • privacy concerns
  • legal defense
  • weak -  better than none - protection against mitm with "cooked" torrents
« Last Edit: November 12, 2014, 05:19:36 pm by ID101 »

Offline ID101

  • Black Box Tester
  • Jr. Member
  • **
  • Posts: 73
  • Karma: +3/-0
    • View Profile
Re: Possibility of using HTTPS as default for https enabled sites and proxies
« Reply #1 on: November 12, 2014, 05:10:32 pm »
New!

full encryption:

kickass.to

Code: [Select]
[home]
1=https://kickass.to
2=http://kickass.to
3=http://kickasstorrents.com
4=http://kickasstorrents.com.proxy.piratenpartij.nl
4=http://kat.ph.proxy.piratenpartij.nl
5=http://www.kickassunblock.info/
6=http://katunblock.com/
6=http://kickass.pw/
7=http://kickassproxy.info/
8=http://katproxy.pw/
9=http://katproxy.me/
10=http://kickassunblock.com/
11=http://katproxy.com/
12=http://kat.dashitz.com/
13=http://kat.kleisauke.nl/
14=http://kat.ph.proxy.piratenpartij.nl/
15=http://www.katmirror.com/
16= http://kat.5gg.biz/
17=https://proxy.piratenpartij.nl/kickass.to

yify-torrents.com
Code: [Select]
[home]
1=https://yts.re
2=http://yts.re
2=https://proxy.piratenpartij.nl/yts.re
3=http://proxy.piratenpartij.nl/yts.re

partial encryption:

rarbg.com

Code: [Select]
[home]
1=https://www.rarbg.com
2=http://www.rarbg.com
3=https://proxy.piratenpartij.nl/rarbg.com
4=http://www.rarbg.com.proxy.piratenpartij.nl

1337x.to/

Code: [Select]
[home]
1=https://1337x.to/
2=http://1337x.to
3=https://proxy.piratenpartij.nl/1337x.to
4=https://proxy.piratenpartij.nl/1337x.to
« Last Edit: November 12, 2014, 05:42:00 pm by ID101 »

Offline ID101

  • Black Box Tester
  • Jr. Member
  • **
  • Posts: 73
  • Karma: +3/-0
    • View Profile
Re: Possibility of using HTTPS as default for https enabled sites and proxies
« Reply #2 on: November 12, 2014, 05:57:16 pm »
I've noticed something strange with proxy.piratenpartij.nl in bit che 3.0 build b14(contrary to web browsers)

only two working:

Code: [Select]
http://thepiratebay.se.proxy.piratenpartij.nl
https://thepiratebay.se.proxy.piratenpartij.nl

not working(always return ./0/1 results)
Code: [Select]
http://proxy.piratenpartij.nl/thepiratebay.se
https://proxy.piratenpartij.nl/thepiratebay.se

http://anyothersite.proxy.piratenpartij.nl
https://anyothersite.proxy.piratenpartij.nl
http://proxy.piratenpartij.nl/anyothersite
https://proxy.piratenpartij.nl/anyothersite
« Last Edit: November 12, 2014, 07:29:36 pm by ID101 »

Offline chip!

  • Bad Ass
  • Administrator
  • Unstoppable
  • *****
  • Posts: 2301
  • Karma: +629/-6
    • View Profile
Re: Possibility of using HTTPS as default for https enabled sites and proxies
« Reply #3 on: November 22, 2014, 05:19:53 am »
i see what you're saying.. it fails by design because we are 'merging' the urls not 'appending'..

so in your example:

http://proxy.piratenpartij.nl/thepiratebay.se

+

/search/%SEARCH%/%PAGENUM%/99/0

results in the 'proper' url merge of:

http://proxy.piratenpartij.nl/search/%SEARCH%/%PAGENUM%/99/0

except its not the search url you want...


but if you change to this:

http://proxy.piratenpartij.nl/thepiratebay.se/

+

search/%SEARCH%/%PAGENUM%/99/0

then you'll get this url merge, which is what you want..

http://proxy.piratenpartij.nl/thepiratebay.se/search/%SEARCH%/%PAGENUM%/99/0


we can update the scripts.. with that format change

EDIT::  DONE for that script
« Last Edit: November 22, 2014, 06:51:02 am by chip! »
  -  https://convivea.com  -   And...  boom goes the dynamite.