Jump to Navigation

Me on Twitter

  • #OMG ! I just realised there was SEVERAL apps on #GooglePlay to check the availability of the #nexus devices !! — 11 years 42 weeks ago
  • "A quick brown fox jumped over the lazy dogs" is called a pangram because it has all the letters of the alphabet. http://t.co/wyzT5YcY9j — 11 years 43 weeks ago
  • @apkudo Good tool, the GUI needs a good failure overview to make it really useful for developers : we need to identify the problematic cases — 11 years 43 weeks ago
  • If you post a comment that contains an URL it will be *silently* ignored... #GooglePlay #android http://t.co/f7NPsr714f — 11 years 43 weeks ago
  • @ippontech Etude bien utile pour débuter dans le dev #mobile. Certains pts gagneraient en clarté avec qques exemples http://t.co/hdA2990pg4 — 11 years 43 weeks ago
  • Last night I got #android 4.2.2 on my #nexus7 ! I'm getting accustomed to regular updates... It's not so bad... — 11 years 44 weeks ago
  • Communication between Activity and Service using Messaging - #android by the example http://t.co/KlGqJBM3 — 11 years 44 weeks ago
  • RT @AskJamesApp: Pour en savoir plus sur moi http://t.co/cyFf1WPs #askjames — 11 years 45 weeks ago
  • My #AngryBirds Score app for #android : https://t.co/RwQDfUqe. A very limited app compared to the one of @louistouzet but it helps ! — 11 years 46 weeks ago
  • Just pushed a 277Mb commit to http://t.co/bJgdwBL9 in a couple of minutes : nice tool ! And it's free #bitbucket — 11 years 47 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