Jump to Navigation

Me on Twitter

  • Knew that already, but may be of some interest for tech beginners... https://t.co/9WIhTRIYyW 2 weeks 7 hours ago
  • RT @stefanolaru: 3 hours of debugging can save you 5 mins of reading the docs. 2 weeks 17 hours ago
  • Like a #scifi movie, except it's real 4 weeks 21 hours ago
  • First paragraphs are just so confuse... Anyway the rest is a great & straight description of #sleep states in… https://t.co/dDLejX0SXO 4 weeks 1 day ago
  • RT @github: A pixel editor in the terminal? Why not! https://t.co/0d2xHvyyXJ 4 weeks 2 days ago
  • I've just realized that #Debian is not #fsf approved. Probably been for years... https://t.co/bCkBbJdv1t 4 weeks 6 days ago
  • RT @n1k0: We send robots to Mars but still struggle with i18n in the UI https://t.co/J8ilJ41bpp 5 weeks 2 days ago
  • RT @ak_anneka: 1er test de custom en cours Est-ce que ça vous plaît ? #WIP @POSCA_Coloring https://t.co/TMq9rQeE2y 5 weeks 2 days ago
  • Intel ME explained (intel management engine) from insider - https://t.co/y9h3OpeuBp 5 weeks 4 days ago
  • https://t.co/6b9nQaWvUO This video is from another galaxy... Fellow technologists PLEASE WATCH ! #coreboot #dance #thinkpad 5 weeks 6 days 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