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

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able