News for hackers. Stuff that matters.

subiye

Re:Conceal, a fast Android crypto lib for SD storage. on Tuesday January 28, 2014 @06:36PM (#7140645)
Conceal ships with a default Keychain implementation which stores the key in SharedPreferences in the internal storage. You can totally customize this if you want to store this in a DB or somewhere else.

We realize that most apps already have their own implementation of caches and we'd rather look at this as a library that helps extend the app specific storage into external storage without letting other apps read this data.

Re:Conceal, a fast Android crypto lib for SD storage. on Tuesday January 28, 2014 @06:35PM (#7140638)
Conceal ships with a default Keychain implementation which stores the key in SharedPreferences in the internal storage. You can totally customize this.
Re:Conceal, a fast Android crypto lib for SD storage. on Tuesday January 28, 2014 @06:26PM (#7140583)
Hey guys I worked on Conceal, AMA
Re:The most dangerous code in the world on Wednesday October 24, 2012 @08:45PM (#4695806)
Another author here. With regards to TextSecure specifically, I will quote the code in the paper here:

schemeRegistry.register(new Scheme("http", PlainSocketFactory.getSocketFactory(), 80)); schemeRegistry.register(new Scheme("https", SSLSocketFactory.getSocketFactory(), 443)); ... HttpHost target = new HttpHost(hostUrl.getHost(), hostUrl.getPort(), HttpHost.DEFAULT_SCHEME_NAME); ... HttpResponse response = client.execute(target, request);

Viewing the code sample from the paper it can be seen that an SSLSocket was meant to be used if the connection was over HTTPS. However this use of the API results in a request being sent over HTTP instead of HTTPS. The argument for CAs not having correct certs makes less sense here in conjunction with the use of SSL API.

We clearly qualify in the paper that this is not exploitable directly.