Jump to Navigation

Me on Twitter

  • mlocate will never ruin my evenings anymore ! UNINSTALLED ! https://t.co/07wCGOZv2Q — 3 years 48 weeks ago
  • "failed to build cryptography" of course... — 3 years 49 weeks ago
  • The worst is that I already know that I forgot some optional openssl dependencies and that I'll need to start again... — 3 years 49 weeks ago
  • Building https://t.co/oTfN2b5DJ4 inside #docker on #armv7 ... Let's go to bed and see if it's done tomorrow morning… https://t.co/6xUegSZlZz — 3 years 49 weeks ago
  • RT @Unexplained: Caption this! https://t.co/FobPIx7gXB — 3 years 50 weeks ago
  • Nice pattern : proposing the user to test his password before disconnecting from an always-connected app #keybase #security — 3 years 50 weeks ago
  • RT @esascience: These cosmic #fireworks are the motions of numerous stars at the outskirts of our Milky Way as measured by @ESAGaia! — 3 years 50 weeks ago
  • Want to really understand how bitcoin works? Here’s a gentle primer | Ars Technica - https://t.co/7nVsFJzG8X — 3 years 51 weeks ago
  • @MCetMOI Impossible d'installer l'appli sur un smartphone sans Google... Je crois que je vais arrêter là... Du mal… https://t.co/owPEvVJNXk — 4 years 3 weeks ago
  • @MCetMOI Euh... Application d'authentification mise en avant sur des sites d'Etat mais certificat de… https://t.co/EDnElhpcZQ — 4 years 3 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