Jump to Navigation

Me on Twitter

  • @codinghorror Many thanks @codinghorror it's 17mn that could have been told in 5mn but it's a good demonstration of… https://t.co/d5D5NtGdi2 4 years 44 weeks ago
  • RT @matvelloso: And you think you're a big deal because you can ssh into your container... https://t.co/s4L9yYR6MU 4 years 45 weeks ago
  • Exploring The Raspberry Pi 4 USB-C Issue In-Depth | Hackaday - https://t.co/2Y57LjxOmQ 4 years 45 weeks ago
  • Did I already retweeted that ? "Bad Map Projection: South America" - https://t.co/N3Nr74Y6t3 4 years 46 weeks ago
  • Bad Map Projection: South America - https://t.co/N3Nr74Y6t3 4 years 47 weeks ago
  • It's never too late to learn : very good introduction to #Bluetooth #security and pairing - How Bluetooth works - https://t.co/tru1Jm3kza 4 years 47 weeks ago
  • People who make laws on things they don't understand; just the same all over the world unfortunately - https://t.co/Otc4fkhXi5 4 years 49 weeks ago
  • RT @tewoz: Demain, lancement officiel de ma campagne de crowdfunding pour mon recueil de strips « Comme un Lundi » ! Je compte sur vous pou… 5 years 3 weeks ago
  • Found that in my old CD tower. Noticed the penguin ? Yes it's a #Linux version of #Tribes - Still one of the best g… https://t.co/4QEzHVXhmO 5 years 5 weeks ago
  • RT @esascience: In this #Hubble image, a very distant galaxy – nicknamed the Sunburst Arc – appears at least 12 times 5 years 6 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