Jump to Navigation

Me on Twitter

  • RT @datagouvfr: Ce n’est pas tous les jours qu’on libère 15 millions de données. Demain (mercredi), venez explorer les données sur les tran… 1 day 5 hours ago
  • @UlrichRozier Essaye la bouillie bordelaise. C'est bio. 3 days 18 hours ago
  • RT @karesti: If you need some #chaosengineering experts feel free to reach me! #womenintech https://t.co/gCkAa2cW1Y 3 days 18 hours ago
  • RT @martinfowler: Statement from Centro de Autonomía Digital on the arrest of @olabini. He has finally been been able to speak to lawyers.… 1 week 5 days ago
  • RT @alsacreations: Pure CSS Francine, une oeuvre dans le style d'une peinture du 18e siècle entièrement conçue à la main en HTML/CSS https:… 8 weeks 1 day ago
  • "Selon les services allemands de cybersécurité, Windows 10 vous surveille de 534 façons [...] et montre qu’à moins… https://t.co/t2qXSX6xt6 9 weeks 2 days ago
  • Stop saying, “We take your privacy and security seriously” - https://t.co/MippyEQMtx 9 weeks 3 days ago
  • Introducing Ionic 4: Ionic for Everyone | The Ionic Blog - https://t.co/bwFrpypFNY 13 weeks 14 hours ago
  • Récit de la découverte des bitcoins dans la fresque « La Liberté guidant le peuple 2019 » – https://t.co/0NryL5qjxT… https://t.co/ilKQOA172k 13 weeks 3 days ago
  • Why does decentralization matter? - Official Mastodon Blog - https://t.co/v7zfx38YvF 16 weeks 3 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