Jump to Navigation

Me on Twitter

  • @Eyal_Lezmy pas seulement l'équipe mais potentiellement tte la communauté. Question d'intérêt public en qq sorte ;-) — 12 years 37 weeks ago
  • @ParisAndroidUG Quel est le moyen privilégié de poser une question android au #PAUG ? J'ai beau chercher... pas de forum-like sur paug.fr... — 12 years 37 weeks ago
  • @malsini documentation is (c) by @agoncal. I suggest u have a look at his book... Also we talked about articles at http://t.co/NZE3z6zG — 12 years 37 weeks ago
  • A voir absolument : Animez vos pages HTML5, Martin Gorner, Google (Atelier Open Data Google / Dataconnexions) http://t.co/6quwgLu6 — 12 years 38 weeks ago
  • Yesterday ended a great 3-day Java EE 6 training course by @agoncal with @alexlewando and others. Group agrees on the quality of the class ! — 12 years 38 weeks ago
  • @romainguy @ParisAndroidUG Retour d'expérience depuis les débuts d'android, qu'est-ce qui marche et ne marche pas ? Le futur d'android ? — 12 years 38 weeks ago
  • #NegativeSpace A bit hard to use but a very ingenious puzzle game for #android that deserves a try http://t.co/71GvLfmV — 12 years 39 weeks ago
  • @louistouzet Bravo pour cette belle appli qui monte, qui monte ! #AngryBirds https://t.co/i5ppeyvr http://t.co/3xBnMBBs — 12 years 39 weeks ago
  • 2 dev java/android cherchent équipe / projet #dataconnexions — 12 years 40 weeks ago
  • @Lim_Ace too bad it doesn't display correctly on my #android... Can't read anything — 12 years 41 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