Verifying SSL certs after Heartbleed

After the recent heartbleed storm that hit our beloved wide web, a lot of people and companies have revocated and then reissued new SSL certificates.

In order to verify that the certs have been correctly setup, here’s a simple command that I used to check the date of the certs:

$ openssl s_client -connect google.com:443 < /dev/null 2>/dev/null \
     | openssl x509 -startdate -noout

This commands outputs today:

notBefore=Apr 9 12:05:08 2014 GMT


The OSGI world of REST

Today, I’m speaking at EclipseConn in Germany about the OSGI world of REST.
For reference I’m pasting here the link to both the presentation and the code:


  1. Presentation link
  2. Sample code

Using Grunt JS with Apache Sling

This weekend I’ve given a try to see how difficult would it be to extract from Maven everything that has to do with the compilation of client-side files ( CofeeScript, JS, CSS, etc ), while keeping the rest of the build in Maven.


  • Live-reload client-side source files in Apache Sling w/o Maven, as soon as source files change.
  • Compile CoffeeScript files with GruntJS, b/c it’s faster than compiling with Maven, and then deploy the compiled files into JCR.


  1. First Step: configure a Grunt JS script that watches for CoffeeScript files, compiling them in the same target folder with Maven.  In my case that was ${project.build.directory}/coffee/js.
  2. Once compiled, deploy JS files in Apache Sling, in the right JCR path.
  3. Use grunt-contrib-watch plugin to update the page in Sling automatically.
  4. Integrate Grunt JS back into the Maven build


Source code from Gist.