Post Reply 
We are now HTTPS-Friendly
May. 17, 2015, 07:46 PM (This post was last modified: Feb. 18, 2016 10:35 PM by Kye-U.)
Post: #1
We are now HTTPS-Friendly
Leveraging CloudFlare's Let's Encrypt's SSL certificate in combination with a self-signed certificate, you now have an option of perusing TUOPF over an encrypted connection Thumbs Up

UPDATE: I have moved to Let's Encrypt for true end-to-end secure connections between your browser and my host.

Simply browse to/bookmark https://www.prxbx.com/forums or click on the "Use HTTPS" button at the top-right corner of every page.

You will know you're browsing securely if you see the lock icon appear in the header logo and the "Use HTTPS" button disappears.

[Image: wX1pnNL.png]

Benefits of HTTPS: http://mashable.com/2011/05/31/https-web-security/

SSL Test Results: https://www.ssllabs.com/ssltest/analyze....Results=on
Visit this user's website
Add Thank You Quote this message in a reply
Jan. 24, 2016, 02:54 AM
Post: #2
RE: We are now HTTPS-Friendly
Hello there Kye-U.

Given that ProxHTTPSProxy and variants are in essence locally hosted projects, would it be possible (or even at all practical) to generate a certificate that's sufficiently compatible with them? I keep getting a "417: SSL Certificate Failed" with ProxHTTPSProxyMII v1.3.1

Thanks for your time and sorry about any inconvenience.

"He that believeth on the Son hath everlasting life: and he that believeth not the Son shall not see life; but the wrath of God abideth on him" - John 3:36
Add Thank You Quote this message in a reply
Jan. 24, 2016, 05:09 PM
Post: #3
RE: We are now HTTPS-Friendly
(Jan. 24, 2016 02:54 AM)Greyhat Harry Wrote:  I keep getting a "417: SSL Certificate Failed" with ProxHTTPSProxyMII v1.3.1

I don't see this.
Where is the error reported?
Have you modified "cacert.pem"?
Add Thank You Quote this message in a reply
Jan. 24, 2016, 07:37 PM
Post: #4
RE: We are now HTTPS-Friendly
. Reported by both browser and ProxHTTPSProxyMII alike.
. cacert.pem being used has the same crc32 as the original from the zip.


Attached File(s)
.png  cert.png (Size: 11.58 KB / Downloads: 785)

"He that believeth on the Son hath everlasting life: and he that believeth not the Son shall not see life; but the wrath of God abideth on him" - John 3:36
Add Thank You Quote this message in a reply
Feb. 18, 2016, 10:36 PM (This post was last modified: Feb. 18, 2016 10:52 PM by Kye-U.)
Post: #5
RE: We are now HTTPS-Friendly
Hi Greyhat Harry,

I have migrated prxbx.com from using CloudFlare to Let's Encrypt as our SSL provider. Could you please let me know if you're still running into the issue you mentioned? Thanks!
Visit this user's website
Add Thank You Quote this message in a reply
[-] The following 1 user says Thank You to Kye-U for this post:
chatterer
Feb. 22, 2016, 06:45 PM
Post: #6
RE: We are now HTTPS-Friendly
Nope, seems to be working ok now!

Yet there's something else I've noticed: specifically when accessing threads (say this one), the https connection status is reported to be unsafe by the browser. It just changes from safe to unsafe and vice versa for no apparent reason.

Thanks for having looked into this anyways Smile!

"He that believeth on the Son hath everlasting life: and he that believeth not the Son shall not see life; but the wrath of God abideth on him" - John 3:36
Add Thank You Quote this message in a reply
Feb. 23, 2016, 08:44 PM (This post was last modified: Feb. 23, 2016 09:04 PM by Kye-U.)
Post: #7
RE: We are now HTTPS-Friendly
(Feb. 22, 2016 06:45 PM)Greyhat Harry Wrote:  Nope, seems to be working ok now!

Yet there's something else I've noticed: specifically when accessing threads (say this one), the https connection status is reported to be unsafe by the browser. It just changes from safe to unsafe and vice versa for no apparent reason.

Thanks for having looked into this anyways Smile!

Great to hear!

Yes, that happens on some pages. For example, in this thread there is an embedded image reference to http://i.imgur.com/wX1pnNL.png. That is a warning saying there is a mix of secure (https) and insecure (http) elements. The more important fact is that you can rest assured that your credentials are not being sent/received in plaintext Smile!
Visit this user's website
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: