- Dec 11, 2015
-
-
akwizgran authored
-
- Dec 10, 2015
-
-
akwizgran authored
Removed methods that are no longer needed for Java 6, moved the remaining method into the utils directory.
-
akwizgran authored
Removed methods that are no longer needed for Java 6, moved the remaining method into the utils directory.
-
Ernir Erlingsson authored
-
Ernir Erlingsson authored
-
Ernir Erlingsson authored
-
Ernir Erlingsson authored
-
Ernir Erlingsson authored
-
Ernir Erlingsson authored
-
- Dec 09, 2015
-
-
Ernir Erlingsson authored
-
Ernir Erlingsson authored
-
- Dec 08, 2015
-
-
Ernir Erlingsson authored
-
Ernir Erlingsson authored
-
str4d authored
-
- Nov 30, 2015
-
-
akwizgran authored
-
- Apr 29, 2015
-
-
akwizgran authored
-
- Jan 14, 2015
-
-
akwizgran authored
-
- Dec 29, 2014
-
-
akwizgran authored
1. The things we're really trying to protect - contact identities, message contents, etc - can't be erased from memory because they're encapsulated inside objects we don't control. 2. Long-term secrets can't be protected by erasing them from memory because they're stored in the database and the database key has to be held in memory whenever the app's running. 3. If the runtime uses a compacting garbage collector then we have no way to ensure an object is erased from memory. 4. Trying to erase secrets from memory makes the code more complex. Conclusion: Let's not try to protect secrets from an attacker who can read arbitrary memory locations.
-
- Apr 30, 2014
-
-
akwizgran authored
-
- Apr 07, 2014
-
-
akwizgran authored
Thanks to the team that audited CryptoCat for this idea. :-)
-
- Apr 05, 2014
-
-
akwizgran authored
-
- Mar 10, 2014
-
-
akwizgran authored
-
- Mar 02, 2014
-
-
akwizgran authored
-
- Mar 01, 2014
-
-
akwizgran authored
-
- Feb 11, 2014
-
-
akwizgran authored
-
- Feb 09, 2014
-
-
akwizgran authored
-
- Feb 05, 2014