OSDev.org

Hi, I've noticed that the forum doesn't use any kind of protection. Why not add HTTPS, via Let's encrypt for example ?

orion40 wrote:Hi, I've noticed that the forum doesn't use any kind of protection. Why not add HTTPS, via Let's encrypt for example ?

http://forum.osdev.org/viewtopic.php?f=6&t=30881

No one's gotten around to it.

That's really about it.

orion40 wrote:Why not add HTTPS, via Let's encrypt for example ?

Because my OS and most other OSes with networking here have HTTP but don't have HTTPS support.

matt11235 wrote:http://forum.osdev.org/viewtopic.php?f=6&t=30881

Thanks for the link, I did a quick search, but didn't found anything. So basically, until the admin pops out of nowhere, this is not going to change ?

omarrx024 wrote:Because my OS and most other OSes with networking here have HTTP but don't have HTTPS support.

Well I guess you're joking, but I'll add more thought anyway: no HTTPS mean passwords and authentification cookies sent in clear text. Who care about your OSdev account ? Probably no one, but your username/password is probably reused several time on other services. Like your email, which hold the key to all your other accounts.
Then there's all kind of nasty redirection, and overall disruption you can cause without HTTPS.

Hell, even donations to get a certificate, I'm sure a few people would be ready to give a dollar or two for that (me included).

orion40 wrote:but your username/password is probably reused several time on other services. Like your email

Corollary: do NOT reuse your password on mulitple websites. Use generated passwords.

I generate passwords by crazily typing randomly and then I don't even need to see the password again, only store it where nobody else would search it in my house.

I also use my cell phone frequently instead of a password.
I use a cell phone as a password for all of the websites I can.
It could be safer sometimes because nobody would have a password and would need my cell phone to log into a website that can use it to recover the account.

~ wrote:I generate passwords by crazily typing randomly and then I don't even need to see the password again, only store it where nobody else would search it in my house.

I also use my cell phone frequently instead of a password.
I use a cell phone as a password for all of the websites I can.
It could be safer sometimes because nobody would have a password and would need my cell phone to log into a website that can use it to recover the account.

How do you use a cell phone as a password? Do you mean you're using 2 factor auth?

For example in Yahoo I have two factor disabled.

When I log in normally I add my cell phone as a means to recover my account.

When I log in again, I use the option to recover the account instead of logging in normally with a password, as if I would have forgotten it. Then it just sends me an SMS with a random code and I use all that as a way to log in instead of using a password.

I still write down the new password just in case I need it.

omarrx024 wrote:

orion40 wrote:Why not add HTTPS, via Let's encrypt for example ?

Because my OS and most other OSes with networking here have HTTP but don't have HTTPS support.

I'm sorry to hear that. Might I suggest libressl? I ported it in 2014 before many systems and they merged the portability fixes I sent them afterwards. It basically works out of the box with no configuration of mine, and passes almost all badssl.com tests.

Viva SSL libre!

HTTPS should be added for many reasons

= People give more trust to websites with HTTPS (or the padlock).
= Encrypted connections are important. It stops sniffing (MITM attacks) as well as giving a good level of privacy.
= Google likes it.

= There is no reason not to. All you need to do is play with Apache. I tried it once when I was into web development (way back before my journey of advanced programming). Mozilla and EFF made Lets Encrypt (and I like those organizations. you can believe what they say because they don't get money).

Looks like it's using it now! Guess someone got around to it

Yep, although it is not as painless as everyone makes it out to be.

chase wrote:Yep, although it is not as painless as everyone makes it out to be.

Using caddyserver.com makes it as painless as ever possible. It's HTTPS and LetsEncrypt by default and you have to put effort to revert it to plain HTTP.

Why on Earth does it matter except that some large corporations are trying to bully everyone?

We hardly communicate much sensitive stuff. What next? Show your passport before you can take part in a pub chat?