Skip to main content

security - Switch the SSL provider after Heartbleed bug instead of revoking

itemprop="text">

I have a question regarding the
Heartbleed problem and the SSL certificates. About Heartbleed many people say that
admins should revoke their certificates and get new ones. I got my SSL certs from
Startcom and as you may know they charge for revoking. I am very angry about that but
know my question(s): - Is it possible to just switch from Startcom to another provider
like Comodo, get new certs and change the certs on my server? - Could be there any
problems with the old certs if they are not being revoked? - Is it possible to "block"
these old certs on my server (Ubuntu 12.04)?



I
don't think that my certs have been compromised but this is a serious topic for
me.



Answer






I
got my SSL certs from Startcom and as you may know they charge for revoking. I am very
angry about that
...




What would you
prefer they do -- revoke hundreds of thousands of certificates? That would produce a
certificate revocation list that some portable devices wouldn't even be able to fit in
their memory. And then every time they updated their CRL, every device, even those on
low bandwidth networks, would have to re-download a massive list. It's just not
practical.




Is it
possible to just switch from Startcom to another provider like Comodo, get new certs and
change the certs on my
server?





Sure,
but how would that help? An attacker could still impersonate your server by using the
old certs.




Could
be there any problems with the old certs if they are not being
revoked?




Yes, an
attacker could use them to impersonate your
server.




Is it
possible to "block" these old certs on my server (Ubuntu
12.04)?





How
would that help? The attacker wouldn't pass any traffic to your server but would instead
interpose themselves.



The upshot of all this is
that your security is compromised and there's basically nothing you can do about it.
(Though it's a pretty minor compromise because it can only be exploited by an active
attacker with at least some control over the network used to access your server. Also,
you may have more serious compromises due to heartbleed, and many of those you can and
should do something about.)


Comments

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...