HTTPS not working properly on here

[retro-pc_user]

Don't know if this is a known bug or not, but, the HTTPS for this site isn't working whatsoever.

Here's what it looks like:

 

[SomeGuy]

HTTPS is an evil blight on the internet designed to intentionally lock out older clients further forcing everyone in to upgrading software and hardware.

Since this forum is about vintage computing, locking out such users would be be the wrong thing to do.

- Posted from Windows 95.

 

[retro-pc_user]

Ah. Another site migrated to HTTPS and none of my retro machines can talk to the newer HTTPS protocol. Thanks for pointing that out.

 

[commodorejohn]

HTTPS is an evil blight on the internet designed to intentionally lock out older clients further forcing everyone in to upgrading software and hardware.

Since this forum is about vintage computing, locking out such users would be be the wrong thing to do.

- Posted from Windows 95.

^ What he said.

 

[Chuck(G)]

I wonder if there's a proxy site that can de-https content for one. At first blush, it wouldn't seem to be impossible.

 

[KC9UDX]

What about TOR?

 

[mbbrutman]

HTTPS is not implemented here. Anything you see today is an accident ...

However, it is on the todo list and I expect it will be implemented soon. It will be optional, not required - you will still be able to use HTTP. (Or at least that is the plan.)

Remember, you are transmitting your userid and password via cookies every time you load a page here when you are signed in. I hope you are using a unique password for this sight, even if we do implement HTTPS.

 

[retro-pc_user]

I'm using a unique password and planning on changing it sometime soon for security measures. Thank you, good sir.

 

[CP/M User]

Wouldn't stay automatically logged in, help prevent transmitting Password info to Cookies?

 

[mbbrutman]

Staying logged in means that you are basically sending a cookie that indicates you are logged in each time you load a page. That cookie is enough to let you make posts under your identity. So while not as bad as sending a password, it's still pretty bad - somebody can impersonate you with just the cookie.

Any machine that sees that request packet can see the cookie. That includes your ISP and anybody sniffing packets if you are using an open WiFi hotspot. Even if you just load a page from this forum while "logged in" without sending the password, you have just given somebody what they need to impersonate you. Sending a password is slightly worse, unless you reuse passwords across multiple forums - then you are really playing with fire.

The short story is that ranting about HTTPS seems to be uninformed. We're not going to break old machines and browsers. But we will encourage people to do their normal activities here using SSL to minimize the risk. And everybody should understand what the risk is and mitigate it properly.

 

[glitch]

There are indeed "SSL Strip" proxies, with proper firewall configuration, you can even make them transparent.

 

[NeXT]

What about TOR?

That's just asking for problems.

 

[CP/M User]

Staying logged in means that you are basically sending a cookie that indicates you are logged in each time you load a page. That cookie is enough to let you make posts under your identity. So while not as bad as sending a password, it's still pretty bad - somebody can impersonate you with just the cookie.

Any machine that sees that request packet can see the cookie. That includes your ISP and anybody sniffing packets if you are using an open WiFi hotspot. Even if you just load a page from this forum while "logged in" without sending the password, you have just given somebody what they need to impersonate you. Sending a password is slightly worse, unless you reuse passwords across multiple forums - then you are really playing with fire.

The short story is that ranting about HTTPS seems to be uninformed. We're not going to break old machines and browsers. But we will encourage people to do their normal activities here using SSL to minimize the risk. And everybody should understand what the risk is and mitigate it properly.

That's disturbing news. I have got a WiFi Device, though I keep it disabled.

 

[eeguru]

The short story is that ranting about HTTPS seems to be uninformed. We're not going to break old machines and browsers. But we will encourage people to do their normal activities here using SSL to minimize the risk. And everybody should understand what the risk is and mitigate it properly.

My password is 'mikebizsexyazhel' Is that secure?

 

[mbbrutman]

I can see that we should be looking into other types of security too ... ;-)

 

[pearce_jj]

There are indeed "SSL Strip" proxies, with proper firewall configuration, you can even make them transparent.

Most corporates do this and resign with self signed certificate. IMHO TLS should be somehow evolved to prevent this.