Skip to main content

heartbleed centOS6.5

Wondering if NSA already knew about heartbleed and was cracking google and FB and other servers so far.

now that its out people are rushing to fix it and we are also.

I saw a great into to heartbleed at http://vimeo.com/91425662

so if you run this it would tell you what version of openssl nginx is using
ldd `which nginx` | grep ssl
        libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f6d0c0cf000) 

and now if you do this it would tell you if you are vulnerable 
strings /usr/lib64/libssl.so.10 | grep "^OpenSSL "
OpenSSL 1.0.1e-fips 11 Feb 2013

if you have anything between 1.0.1. and 1.0.1f you are vulnerable, perconna guys have a nice post on same http://www.mysqlperformanceblog.com/2014/04/08/openssl-heartbleed-cve-2014-0160/

CentOS has released patch to current stable release and to fix all you need to do is update centOS or recompile nginx and disable heartbleed.

to update centOS  run "sudo yum update openssl" and restart services using openssl like nginx,mysql,apache.

 to verify if its fixed run 

 http://possible.lv/tools/hb/?domain=uat.xyz.com
http://filippo.io/Heartbleed/#qa.xyz.com

Comments

  1. IgorApril 11, 2014 at 2:47 AM

    Good video, even for non tech folks. BTW I also like this comic: Heartbleed Explanation
    http://xkcd.com/1354/

    ReplyDelete

Post a Comment

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are Download Erlang Download Rabbit MQ Server Download Rabbit MQ Java client jars Compile and run the below two class and you are done. This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time. For more information on AMQP, Exchanges, Queues, read this excellent tutorial http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/ +++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++ import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.se...
23 comments
Read more

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...
7 comments
Read more

Killing a particular Tomcat thread

Update: This JSP does not work on a thread that is inside some native code.  On many occasions I had a thread stuck in JNI code and it wont work. Also in some cases thread.stop can cause jvm to hang. According to javadocs " This method is inherently unsafe. Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked". I have used it only in some rare occasions where I wanted to avoid a system shutdown and in some cases we ended up doing system shutdown as jvm was hung so I had a 70-80% success with it.   -------------------------------------------------------------------------------------------------------------------------- We had an interesting requirement. A tomcat thread that was spawned from an ExecutorService ThreadPool had gone Rogue and was causing lots of disk churning issues. We cant bring down the production server as that would involve downtime. Killing this thread was harmless but how to kill i...
6 comments
Read more