← Back to context

Comment by lawl

12 years ago

Agree. This needs a big fat the world is coming to an end stlye of warning.

I've just shut down the webservers running SSL that I can control. If you are vuln and don't want to build openssl from source and can afford the outage. I'd reccomend to do the same.

OTHERWISE BUILD FROM SOURCE IMMEDIATELY, PATCH, AND GET NEW KEYS!

Let's hope CA's don't get swamped by all the CSR's. Or rather let's hope they do so we see people are doing something...

For me right now these are just my hobby projects. So I don't care if they're down. But I imagine it will be fun tomorrow.

And when it's fixed, get new keys.

Btw: I'm a dev. Not a sysadmin though :P

Edit: Debian is patched. I'm online again \o/

6 comments

lawl

Reply
M4v3R  12 years ago

Ok, anyone could assist me on how to update openssl without breaking anything? I've fetched newest sources from openssl.org and compiled them, but "make install" doesn't actually install it, it only got compiled, but issuing "openssl version" still gives me the old version.

What I want to do is to patch it so our webserver uses new version.

  • josh-wrale  12 years ago

    I would tread lightly here if you aren't comfortable with compiling. Rather than break your website, it might be better to take it down until your distro's packages are available.

    You should probably spend your time investigating a good method of reissuing keys for when you get to a stable OpenSSL version.

    Some apps have OpenSSL statically compiled into the binaries. Beware that what you think is fixed may not be.

    • M4v3R  12 years ago

      Well, I'm not really in position of taking the whole service down at this moment, I would really like to have a way to patch it instead.

      2 replies →