Jump to Navigation

Me on Twitter

  • @alexlewando bon courage pour la fin ;-) #forgecamp — 11 years 46 weeks ago
  • After spending the morning on android signing keys, I see green robots everywhere! Now it's becoming serious..! — 11 years 46 weeks ago
  • @alexlewando Tu es dans quelle équipe ? — 11 years 46 weeks ago
  • favorable user feedback is really the best reward http://t.co/1BF1IGUF — 11 years 47 weeks ago
  • 1st #android app, 2nd release and so many hours for such a simple thing : https://t.co/OH0Wb4H6. Now back to #dataconnexions ! — 11 years 47 weeks ago
  • quand je fais une mise en prod http://t.co/aZ66rUtG http://t.co/69Dh79sx #lesjoiesducode — 11 years 47 weeks ago
  • You know that you got a good password when you cannot recover it yourself — 11 years 48 weeks ago
  • Checking out tutorials @DataStax http://t.co/QOHSIUjj while waiting for yesterday @pcmanus slides or video... — 11 years 48 weeks ago
  • @pcmanus hello peut-on avoir les slides d'hier ? — 11 years 48 weeks ago
  • Very nice talk about #cassandra by @pcmanus . Makes it easy to understand the product pros and cons — 11 years 49 weeks ago
More at Twitter...

cryptography

android A paper backup for your private key

Submitted by nicobo on June 14, 2012 - 01:03

Android keychainAndroid requires developers to sign their applications with a digital certificate and that each future release be signed with the same certificate.

Sadly, bad things happen when the developer (you) looses access to the certificate : he (you) will not be able to release updates for the application without it. Never. Ever.

Android does not currently support multiple certificates per application so the best you could do would be to release a new app with the same name, in the hope your users will find a way to it by themselves.

As years go on, you will change your computer, wipe USB keys, reinstall OS, ...
So many dangerous operations for your digital certificates, hidden among millions of files !
If, like me, you are anxious at the idea of losing your certificates or passwords, just print a paper copy !
Although it is not invulnerable, paper should be less prone to mass erasing than a simple electronic file.

The idea is simple, not new, and you just need to know two commands to get a printable hard copy of your certificate.

Let's start.

java HttpClient 3.x : a portable SSL Socket Factory implementation

Submitted by nicobo on January 18, 2012 - 23:13

I was just trying to implement client and server authentication over SSL on IBM Websphere 6 (JRE 1.4.2)...

[...]

It may sound awkward in 2012, but if you wish the HTTPS server to identify your Java client (versus : only the server is identified), you will have to write your own implementation of a socket factory.

The Java Runtime Environment doesn't provide ready-to-use classes to do this. Yes : there is javax.net.ssl.SSLSocketFactory.getDefault() but it requires to set some system (therefore global) properties to point to the certificates files !!!

Even with Apache's HttpClient (at least version 3.x), you have to use a custom SSLProtocolSocketFactory.

The HttpClient SSL Guide provides sample code to implement mutual client and server authentication ; unfortunately the latest stable release of it (contrib 3.1) is bound to Sun's API with imports such as com.sun.net.ssl.KeyManagerFactory. Needless to say that this will not work on an IBM Websphere JRE...

This article contains an implementation of a SSLProtocolSocketFactory for HttpClient, to whom may be interested...

Syndicate content