Skip to content
Snippets Groups Projects
  1. Nov 19, 2013
  2. Sep 27, 2013
  3. Jul 27, 2013
  4. Jun 17, 2013
  5. Jun 14, 2013
  6. Jun 13, 2013
    • akwizgran's avatar
      Made the invitation protocol symmetrical. · e1ec17f4
      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.
      e1ec17f4
  7. Jun 05, 2013
  8. May 16, 2013
  9. May 15, 2013
  10. May 14, 2013
    • akwizgran's avatar
      Fixed a race conditon when adding a transport and then an endpoint. · dddd15cd
      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().
      dddd15cd
  11. May 04, 2013
    • akwizgran's avatar
      Moved lifecycle management into briar-core and reconfigured executors. · 673d7fa0
      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.
      673d7fa0
  12. Apr 30, 2013
    • akwizgran's avatar
      Removed bundle encryption. · d5720c08
      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.
      d5720c08
  13. Apr 29, 2013
  14. Apr 26, 2013
  15. Apr 24, 2013
  16. Apr 18, 2013
  17. Apr 16, 2013
  18. Apr 15, 2013
  19. Apr 14, 2013
  20. Apr 13, 2013
  21. Apr 12, 2013
  22. Apr 09, 2013
  23. Apr 08, 2013
  24. Apr 05, 2013
  25. Mar 31, 2013
  26. Mar 30, 2013
  27. Mar 29, 2013
  28. Mar 23, 2013
  29. Mar 20, 2013
Loading