Jump to Navigation

Me on Twitter

  • Looks huge ! #JavaEE8 http://t.co/NffP1OypY0 10 years 12 weeks ago
  • Sometimes #Python has #batteriesincluded sometimes not : see os.makedirs() http://t.co/lffkJy59Rn 10 years 13 weeks ago
  • @espylaub 1 year old already but very clear description of one big mobile software issue today. http://t.co/7q0I4wIRok 10 years 13 weeks ago
  • #ux #antipattern asking for a confirmation to exit the app when the user has already clicked twice or more just to find the button ! 10 years 15 weeks ago
  • UX designers: Side drawer navigation could be costing you half your user engagement http://t.co/o3YkClSmIW 10 years 29 weeks ago
  • CSS fans : The Future of Responsive Digital Layout http://t.co/zkAmlqV9zD 10 years 30 weeks ago
  • new SimpleDateFormat("yyyy-MM-dd kk:mm:ss").format(new Date()).replace(" 24", " 00"); Sorry but... #WTF!!!?? Can you just read the docs ? 10 years 36 weeks ago
  • #Argh ! http://t.co/oQ1MtqHWS7 10 years 41 weeks ago
  • @ubuntu #fail Typing "garmin" to get a GPS plugin in Software Center just finds crap when Synaptic got it right at first try 10 years 41 weeks ago
  • @SpiderOak what's going on with your website ? http://t.co/vS0p3UpsA8 10 years 42 weeks ago

cryptography

android A paper backup for your private key

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. NeverEver.

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 simplenot 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

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