briar issueshttps://code.briarproject.org/groups/briar/-/issues2018-06-12T11:32:37Zhttps://code.briarproject.org/briar/briar/-/issues/140User testing sessions2018-06-12T11:32:37ZakwizgranUser testing sessionsTwo user testing sessions for Milestone F -- findings to be documented in the issue tracker.Two user testing sessions for Milestone F -- findings to be documented in the issue tracker.Milestone Fhttps://code.briarproject.org/briar/briar/-/issues/142Co-ordinate with OTF security audit2018-06-12T11:32:37ZakwizgranCo-ordinate with OTF security auditMilestone Gakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/143Co-ordinate translations before 1.0 release2018-06-12T11:32:37ZakwizgranCo-ordinate translations before 1.0 releaseMilestone GTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/144User testing sessions2018-06-12T11:32:37ZakwizgranUser testing sessionsTwo user testing sessions for Milestone G -- findings to be documented in the issue tracker.Two user testing sessions for Milestone G -- findings to be documented in the issue tracker.Milestone Ghttps://code.briarproject.org/briar/briar/-/issues/146Upgrade Spongy Castle to 1.532018-06-12T11:32:37ZakwizgranUpgrade Spongy Castle to 1.53Milestone Aakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/147Implement crypto_secretbox with Spongy Castle2018-06-12T11:32:37ZakwizgranImplement crypto_secretbox with Spongy CastleThis is a simple combination of XSalsa20 and Poly1305. Use libsodium or tweetnacl to generate test vectors.This is a simple combination of XSalsa20 and Poly1305. Use libsodium or tweetnacl to generate test vectors.Milestone Ahttps://code.briarproject.org/briar/briar/-/issues/148Upgrade Tor to 0.2.7.52018-06-12T11:32:37ZakwizgranUpgrade Tor to 0.2.7.5Milestone Aakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/149Use control port to create Tor hidden service2018-06-12T11:32:37ZakwizgranUse control port to create Tor hidden serviceHidden services can now be created via the control port, with the controller storing the private key. This will enable us to store the private key in the encrypted database.Hidden services can now be created via the control port, with the controller storing the private key. This will enable us to store the private key in the encrypted database.Milestone Chttps://code.briarproject.org/briar/briar/-/issues/152Merge patches upstream2020-11-21T19:42:04ZakwizgranMerge patches upstreamDetermine which of the patches in the /patches dir should be merged upstream and contact the upstream developers.
Related: #25, #64, #115Determine which of the patches in the /patches dir should be merged upstream and contact the upstream developers.
Related: #25, #64, #115https://code.briarproject.org/briar/briar/-/issues/154Test Requirement of Foreground and Permanent Notification Icon2018-06-12T11:32:36ZTorsten GroteTest Requirement of Foreground and Permanent Notification IconShowing a permanent notification icon is discouraged and many people's notification bar is incredibly cluttered with notification icons already. I'd like to raise the question whether we really need to show the icon to signal the user th...Showing a permanent notification icon is discouraged and many people's notification bar is incredibly cluttered with notification icons already. I'd like to raise the question whether we really need to show the icon to signal the user that she is signed into Briar at the moment.
The notification icon is shown for the app to run in the foreground and for preventing it from getting killed. However, we should experiment to see whether running in the foreground is definitely necessary. (It's more likely to be necessary on devices with less memory, so that's the place to test.)Milestone Cakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/158Support Android 6 Permission Model2018-06-12T11:32:36ZTorsten GroteSupport Android 6 Permission ModelCurrently, the app is built for API level 22 and does not yet support the new permission model of Android 6 (API 23).
This affects at least the permission `ACCESS_COARSE_LOCATION`. We need to ask for this permission before adding cont...Currently, the app is built for API level 22 and does not yet support the new permission model of Android 6 (API 23).
This affects at least the permission `ACCESS_COARSE_LOCATION`. We need to ask for this permission before adding contacts via Bluetooth. For details see #223.
See https://developer.android.com/training/permissions/requesting.html for more information.Android Beta 2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/160Improve .gitignore2018-06-12T11:32:36ZErnir ErlingssonImprove .gitignoreImprove the .gitignore to clean up the change-listImprove the .gitignore to clean up the change-listMilestone Ahttps://code.briarproject.org/briar/briar/-/issues/162Build with latest Android SDK2018-06-12T11:32:36ZakwizgranBuild with latest Android SDKThe project is currently built with SDK version 22, which isn't bundled with Android Studio by default. This creates an extra hurdle for people to build the code. Build with the latest SDK (23) while keeping 22 as the target.The project is currently built with SDK version 22, which isn't bundled with Android Studio by default. This creates an extra hurdle for people to build the code. Build with the latest SDK (23) while keeping 22 as the target.Milestone Aakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/163Create a blackhole transport for testing2022-11-18T12:21:25ZakwizgranCreate a blackhole transport for testinghttps://code.briarproject.org/briar/briar/-/issues/164Research reproducible builds with Gradle2018-05-11T14:21:26ZakwizgranResearch reproducible builds with GradleFor dependencies that don't require patches against upstream, it would be nice to manage the dependencies through Gradle rather than keeping the jars in our repo. But our long-term plan is to have reproducible builds, so every dependency...For dependencies that don't require patches against upstream, it would be nice to manage the dependencies through Gradle rather than keeping the jars in our repo. But our long-term plan is to have reproducible builds, so every dependency should either be built from source or use an upstream binary with a reproducible build process. Find out whether this is possible with Gradle dependencies.https://code.briarproject.org/briar/briar/-/issues/165Research upgrading the dependency injection framework2018-06-12T11:32:36ZakwizgranResearch upgrading the dependency injection frameworkCurrently we use Roboguice 2. Investigate whether Roboguice 3 or Dagger would offer advantages, and how much work would be involved in the upgrade. Whatever we choose must work for briar-desktop as well as briar-android.Currently we use Roboguice 2. Investigate whether Roboguice 3 or Dagger would offer advantages, and how much work would be involved in the upgrade. Whatever we choose must work for briar-desktop as well as briar-android.Milestone Ahttps://code.briarproject.org/briar/briar/-/issues/166Upgrade Tor to 0.2.7.62018-06-12T11:32:36ZakwizgranUpgrade Tor to 0.2.7.6Also update the GeoIP database.Also update the GeoIP database.Milestone Aakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/167Replace TransportConfig with namespaced Settings2018-06-12T11:32:36ZakwizgranReplace TransportConfig with namespaced SettingsThe Tor and Bluetooth plugins use a mixture of Settings and TransportConfig to store their configuration. No other plugins use TransportConfig.
Add namespaces to Settings so all components can use them without treading on each other's...The Tor and Bluetooth plugins use a mixture of Settings and TransportConfig to store their configuration. No other plugins use TransportConfig.
Add namespaces to Settings so all components can use them without treading on each other's toes, and remove TransportConfig.
Plugins should be able to access their settings through the PluginCallback, as they currently can for TransportConfig. Perhaps the PluginManager should also push updated settings to the plugins so they don't have to listen on the EventBus?Milestone BSantiago Torres-AriasSantiago Torres-Ariashttps://code.briarproject.org/briar/briar/-/issues/169Switch KDF from SHA-256 to BLAKE22018-06-12T11:32:36ZakwizgranSwitch KDF from SHA-256 to BLAKE2Subtask of #111.Subtask of #111.Milestone Aakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/170Use Argon2 for password-based key derivation2020-11-21T19:40:11ZakwizgranUse Argon2 for password-based key derivationArgon2 won the password hashing competition and has a number of advantages over PBKDF2.
In this case it makes sense to wrap a native implementation even if there's a Java implementation available.Argon2 won the password hashing competition and has a number of advantages over PBKDF2.
In this case it makes sense to wrap a native implementation even if there's a Java implementation available.