- Nov 19, 2013
-
-
akwizgran authored
-
- Sep 27, 2013
- Jul 27, 2013
-
-
akwizgran authored
The method used by Commons IO to get the available disk space fails on Android devices that lack a df binary - use the Android API instead.
-
- Jun 27, 2013
-
-
akwizgran authored
This removes the other projects' dependency on the Android API.
-
- Jun 17, 2013
-
-
akwizgran authored
-
- Jun 14, 2013
-
-
akwizgran authored
-
- Jun 13, 2013
-
-
akwizgran authored
-
akwizgran authored
Both devices try to make outgoing connections and accept incoming connections simultaneously. This should lead to faster connection establishment when there are asymmetrical connectivity problems, such as devices that are unable to receive LAN multicast packets or make themselves discoverable via Bluetooth.
-
- Jun 05, 2013
-
-
akwizgran authored
-
- May 16, 2013
-
-
akwizgran authored
See issue #3612607.
-
- May 15, 2013
- May 14, 2013
-
-
akwizgran authored
To fix issue #3611966, KeyManagerImpl's handling of TransportAddedEvent was made asynchronous. This made it possible for a thread to call KeyManager.endpointAdded() before the KeyManager had asynchronously handled the TransportAddedEvent from a previous call to DatabaseComponent.addTransport().
-
- May 04, 2013
-
-
akwizgran authored
CryptoExecutor and DatabaseExecutor now use bounded thread pools with unbounded queues, since running too many tasks in parallel is likely to harm performance; IncomingConnectionExecutor, PluginExecutor and ReliabilityExecutor use unbounded thread pools with direct handoff, since their tasks may run indefinitely. There are no longer any bounded executors, and all executors discard tasks when shutting down, which fixes issue #3612189. Responsibility for starting and stopping services has been moved from BriarService in briar-android to LifecycleManagerImpl in briar-core. However, BriarService is still responsible for stopping the Android-specific executors, which is ugly. It would be better if executors registered themselves with LifecycleManager.
-
- Apr 30, 2013
-
-
akwizgran authored
Android doesn't currently store bundles persistently, so it's premature to protect against accidental information leaks through persistent bundle storage. Protecting against deliberate information leaks by the OS is probably futile, so there's currently no need for bundle encryption.
-
- Apr 29, 2013
-
-
akwizgran authored
-
- Apr 26, 2013
-
-
akwizgran authored
-
- Apr 24, 2013
- Apr 18, 2013
-
-
akwizgran authored
-
- Apr 16, 2013
- Apr 15, 2013
-
-
akwizgran authored
-
- Apr 14, 2013
- Apr 13, 2013
- Apr 12, 2013
- Apr 09, 2013
-
-
akwizgran authored
-
- Apr 08, 2013
-
-
akwizgran authored
-
- Apr 05, 2013
- Mar 31, 2013
-
-
akwizgran authored
-
- Mar 30, 2013
-
-
akwizgran authored
(Although it isn't possible to create an identity yet...)
-
- Mar 29, 2013
-
-
akwizgran authored
The invitation and private messaging UIs are currently broken. Some key rotation bugs were fixed; others may have been created (unit tests needed). An encoding for private keys was added. Pseudonyms were moved out of the messaging package and ratings were moved in.
-