briar issueshttps://code.briarproject.org/briar/briar/-/issues2018-09-03T12:12:48Zhttps://code.briarproject.org/briar/briar/-/issues/1314Missing or repeated flags in emoji chooser2018-09-03T12:12:48ZakwizgranMissing or repeated flags in emoji chooser* Android version: 6.0.1
* Briar version: 1.0.1
* User feedback: "In icon section, some flags are missing and most of them are repeated several times."* Android version: 6.0.1
* Briar version: 1.0.1
* User feedback: "In icon section, some flags are missing and most of them are repeated several times."Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1309IllegalStateException when creating account2018-06-14T17:17:17ZakwizgranIllegalStateException when creating account* Android version: 8.0.0
* Phone model: Motorola XT1650 (griffin)
* Briar version: 1.0.2 (e516c32)
Stacktrace:
```
java.lang.IllegalStateException
at org.briarproject.briar.android.login.SetupControllerImpl.createAccount(SetupControll...* Android version: 8.0.0
* Phone model: Motorola XT1650 (griffin)
* Briar version: 1.0.2 (e516c32)
Stacktrace:
```
java.lang.IllegalStateException
at org.briarproject.briar.android.login.SetupControllerImpl.createAccount(SetupControllerImpl.java:88)
at org.briarproject.briar.android.login.SetupControllerImpl.createAccount(SetupControllerImpl.java:82)
at org.briarproject.briar.android.login.DozeFragment.onClick(DozeFragment.java:109)
at android.view.View.performClick(View.java:6259)
at android.view.View$PerformClick.run(View.java:24732)
at android.os.Handler.handleCallback(Handler.java:789)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6592)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:769)
```
This comes from an old Briar version and the code in question has changed. The exception is thrown because the author name or password is null, but those values are now stored in the activity rather than the controller, and they're saved and restored on screen rotation. So this bug may already have been fixed. The ticket can be closed if we don't get any more reports.Android 1.1https://code.briarproject.org/briar/briar/-/issues/1306Share access to Play Store reviews2018-08-24T17:49:56ZakwizgranShare access to Play Store reviewsAllow team members other than @akwizgran to respond to Play Store reviews. I'm assuming there's a mechanism for this, we just need to find out what it is.Allow team members other than @akwizgran to respond to Play Store reviews. I'm assuming there's a mechanism for this, we just need to find out what it is.https://code.briarproject.org/briar/briar/-/issues/1305Share access to crash reports and feedback2018-08-24T17:50:57ZakwizgranShare access to crash reports and feedbackAllow team members other than @akwizgran to read crash reports and feedback and create tickets from them. This involves sharing access to the reports and establishing a workflow for avoiding duplicate tickets. Each member should be able ...Allow team members other than @akwizgran to read crash reports and feedback and create tickets from them. This involves sharing access to the reports and establishing a workflow for avoiding duplicate tickets. Each member should be able to search past reports to find reports that relate to the same issue.
The private key for decrypting reports should not be stored on a server. To protect the confidentiality of future reports, we should either replace the encryption key pair when a member leaves the team, or re-encrypt the reports to another key pair that can be replaced when a member leaves.https://code.briarproject.org/briar/briar/-/issues/1304Share access to contact email account2018-08-24T17:51:17ZakwizgranShare access to contact email accountAllow team members other than @akwizgran to read and respond to contact emails. This involves sharing access to the account and establishing a workflow for avoiding duplicate responses, such as moving messages into a folder before dealin...Allow team members other than @akwizgran to read and respond to contact emails. This involves sharing access to the account and establishing a workflow for avoiding duplicate responses, such as moving messages into a folder before dealing with them.https://code.briarproject.org/briar/briar/-/issues/1301LAN plugin isn't activated when starting wifi hotspot2018-10-03T15:40:05ZakwizgranLAN plugin isn't activated when starting wifi hotspotA user reported that the wifi icon doesn't become green when starting a wifi hotspot while Briar is running, but if the hotspot is started before running Briar, the icon is green.
* Android version: 6.0.1
* Phone model: Fairphone FP2
* ...A user reported that the wifi icon doesn't become green when starting a wifi hotspot while Briar is running, but if the hotspot is started before running Briar, the icon is green.
* Android version: 6.0.1
* Phone model: Fairphone FP2
* Briar version: 1.0.4 (f31219d)
```
"Mobile data status" : "Available, enabled, connected",
"Wi-Fi Direct" : "Supported",
"Wi-Fi address" : "0.0.0.0",
"Wi-Fi status" : "Available, not enabled, not connected"
```
(It's not clear however whether the wifi hotspot was running when the report was sent.)akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1298Wifi address should be scrubbed from crash reports/feedback2018-12-10T10:13:18ZakwizgranWifi address should be scrubbed from crash reports/feedbackIt's possible for the wifi IP address included in crash reports and feedback to be a public (routable) address, so it should be scrubbed like other IP addresses.It's possible for the wifi IP address included in crash reports and feedback to be a public (routable) address, so it should be scrubbed like other IP addresses.Android 1.1https://code.briarproject.org/briar/briar/-/issues/1297"Decrypting database" label needs some padding2018-06-19T16:25:38Zakwizgran"Decrypting database" label needs some padding![device-2018-06-08-115926](/uploads/67a98c8a74a7898936b9047535fecf67/device-2018-06-08-115926.png)![device-2018-06-08-115926](/uploads/67a98c8a74a7898936b9047535fecf67/device-2018-06-08-115926.png)Android 1.1https://code.briarproject.org/briar/briar/-/issues/1294Log formatter doesn't log exception stacktraces2018-06-13T10:08:51ZakwizgranLog formatter doesn't log exception stacktracesOur custom log formatter doesn't log exception stacktraces.Our custom log formatter doesn't log exception stacktraces.Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1293Tor not activated due to auth cookie not being created2018-06-26T11:05:31ZakwizgranTor not activated due to auth cookie not being created* Android version: 7.1.1
* Phone model: Sony E6653
* Briar version: 1.0.5 (183f0c5)
* User feedback: "Leider auf diesem Stand unbrauchbar"
Log extract:
```
05-24 14:55:41.910 I/TorPlugin: Starting Tor
05-24 14:55:43.653 I/TorPlugin: May...* Android version: 7.1.1
* Phone model: Sony E6653
* Briar version: 1.0.5 (183f0c5)
* User feedback: "Leider auf diesem Stand unbrauchbar"
Log extract:
```
05-24 14:55:41.910 I/TorPlugin: Starting Tor
05-24 14:55:43.653 I/TorPlugin: May 24 16:55:43.646 [notice] Tor 0.2.9.14 (git-73e1a45b461ab669) running on Linux with Libevent 2.0.22-stable, OpenSSL 1.0.2n and Zlib 1.2.8.
05-24 14:55:43.704 I/TorPlugin: May 24 16:55:43.650 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
05-24 14:55:43.705 I/TorPlugin: May 24 16:55:43.653 [notice] Read configuration file \"/data/user/0/org.briarproject.briar.android/app_tor/torrc\".
05-24 14:55:43.705 I/TorPlugin: May 24 16:55:43.677 [notice] I think we have 8 CPUS, but only 4 of them are available. Telling Tor to only use 4. You can override this with the NumCPUs option
05-24 14:55:43.707 I/TorPlugin: May 24 16:55:43.679 [notice] Opening Control listener on 127.0.0.1:59051
05-24 14:55:43.709 I/TorPlugin: May 24 16:55:43.679 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
05-24 14:55:46.711 W/TorPlugin: Auth cookie not created
05-24 14:55:46.711 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/tor
05-24 14:55:46.711 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/geoip
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/torrc
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/done
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/.tor/control_auth_cookie
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/.tor/lock
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/.tor/cached-certs
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/.tor/state
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/.tor/cached-microdescs.new
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/.tor/cached-microdesc-consensus
05-24 14:55:46.712 I/TorPlugin: /data/user/0/org.briarproject.briar.android/app_tor/.tor/cached-microdescs
05-24 14:55:46.712 W/PluginManagerImpl: Plugin org.briarproject.bramble.tor did not start
05-24 14:55:46.712 W/PluginManagerImpl: org.briarproject.bramble.api.plugin.PluginException
```
The log shows that the cookie file exists, but apparently either Tor hasn't written the cookie to the file within the three-second timeout, or the FileObserver has failed to notice.Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1291Huawei power management UI has changed2018-06-15T15:23:18ZakwizgranHuawei power management UI has changedWhen installing Briar on the Huawei P8 Lite 2017 (Android 7.0/EMUI 5.0.1), the "Protect Briar" button in the setup wizard opens a screen with power management controls that seem to be the opposite of those on older devices like the Ascen...When installing Briar on the Huawei P8 Lite 2017 (Android 7.0/EMUI 5.0.1), the "Protect Briar" button in the setup wizard opens a screen with power management controls that seem to be the opposite of those on older devices like the Ascend Y330 (Android 4.2.2/EmotionUI 2.0).
![device-2018-05-30-145840](/uploads/3120e842df0ce698a66b0a25b8d7089e/device-2018-05-30-145840.png) ![device-2018-05-30-151203](/uploads/2ca5e5416beff355d8e8e59175c48747/device-2018-05-30-151203.png)
Users might think they need to change the setting for Briar, which would have the opposite of the intended effect.
Subtask of #1260.Android 1.1https://code.briarproject.org/briar/briar/-/issues/1289RecyclerView pre-rendering causes threaded messages to be marked as read2019-03-21T13:48:56ZakwizgranRecyclerView pre-rendering causes threaded messages to be marked as readSee https://code.briarproject.org/akwizgran/briar/merge_requests/818#note_27170:
> The latest versions of the support library use a performance optimization for `RecyclerView` which pre-renders list items on spare UiThread cycles. This ...See https://code.briarproject.org/akwizgran/briar/merge_requests/818#note_27170:
> The latest versions of the support library use a performance optimization for `RecyclerView` which pre-renders list items on spare UiThread cycles. This calls `onBindViewHolder()` which we currently use to determine whether a user has seen a post.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1288Use placeholder text for text fields2018-06-18T14:20:47ZakwizgranUse placeholder text for text fieldsMost of our text fields use placeholder text, but a few use floating labels (e.g. the forum creation screen) or separate labels (e.g. the password screen). Let's standardise on one style.
Floating labels don't work well with automatical...Most of our text fields use placeholder text, but a few use floating labels (e.g. the forum creation screen) or separate labels (e.g. the password screen). Let's standardise on one style.
Floating labels don't work well with automatically giving keyboard focus to the text field, so let's use placeholder text everywhere.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1286Build fails with verification error when following instructions on website2022-01-13T17:42:40ZakwizgranBuild fails with verification error when following instructions on websiteA user reported that the Android Studio build failed with "an error about dependencies, we think it is because of the checksum" when following the build instructions on the website.
Sounds like it could be related to recent changes in t...A user reported that the Android Studio build failed with "an error about dependencies, we think it is because of the checksum" when following the build instructions on the website.
Sounds like it could be related to recent changes in the way jtorctl and the Tor binaries are downloaded and verified.https://code.briarproject.org/briar/briar/-/issues/1281Introduction fails after deleting and re-adding contact2018-05-24T09:58:37ZakwizgranIntroduction fails after deleting and re-adding contactThis was reported by a friend of @grote.
Steps to reproduce:
* Set up fresh accounts for Alice, Bob and Carol
* Carol signs out and plays no further role
* Put Bob into airplane mode and turn off Bluetooth
* Wait until Alice sees Bob as...This was reported by a friend of @grote.
Steps to reproduce:
* Set up fresh accounts for Alice, Bob and Carol
* Carol signs out and plays no further role
* Put Bob into airplane mode and turn off Bluetooth
* Wait until Alice sees Bob as offline
* Alice asks to introduce Bob to Carol
* Alice and Bob remove each other as contacts
* Take Bob out of airplane mode
* Alice asks to introduce Bob to Carol again
* Alice sees the second introduction request as received (two check marks)
* Alice sends a private message to Bob
* Alice sees the private message as received
Expected result:
* Bob sees Alice's introduction request and private message
Actual result:
* Bob only sees Alice's private message
The suspected cause is that Alice's second introduction request depends on the first request, because Alice (in the introducer role) doesn't delete the last local message ID from the session when removing Bob as a contact. Bob no longer has a copy of Alice's first request, so the second request is never delivered to the client layer. But Alice sees the second request as received because it's acked by the sync layer.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1280Support v3 hidden services2022-07-13T11:20:27ZakwizgranSupport v3 hidden servicesTor's v3 hidden service protocol has several security improvements over the legacy v2 protocol. We should make a planned migration from v2 to v3 hidden services:
1. Add support for connecting to v3 hidden services (depends on #1279)
2. ...Tor's v3 hidden service protocol has several security improvements over the legacy v2 protocol. We should make a planned migration from v2 to v3 hidden services:
1. Add support for connecting to v3 hidden services (depends on #1279)
2. Create v3 hidden services for all new and existing Briar accounts
3. After a reasonable time, remove support for v2 hidden services
Each account will have two hidden services during the transition period. This will increase our bandwidth usage, but most of the bandwidth cost comes from downloading the consensus, which will be shared between the two services.Android 1.4https://code.briarproject.org/briar/briar/-/issues/1279Upgrade Tor to 0.3.42018-10-20T09:05:50ZakwizgranUpgrade Tor to 0.3.4Tor 0.3.3 is now stable. This series adds support for creating and managing v3 hidden services via the control port. Consensus diffs are also supported, which should save some bandwidth.Tor 0.3.3 is now stable. This series adds support for creating and managing v3 hidden services via the control port. Consensus diffs are also supported, which should save some bandwidth.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1277BdfReaderImpl accepts any string/raw length up to Integer.MAX_VALUE2018-09-07T11:16:32ZakwizgranBdfReaderImpl accepts any string/raw length up to Integer.MAX_VALUEThis leads to a remotely triggerable OOM by sending, for example, a private message with the body 0x604406400000, which is the start of a BDF list containing a 100 MB string, causing the BdfReaderImpl to try to allocate a 100 MB buffer.This leads to a remotely triggerable OOM by sending, for example, a private message with the body 0x604406400000, which is the start of a BDF list containing a 100 MB string, causing the BdfReaderImpl to try to allocate a 100 MB buffer.Android 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1276Remove support for inactive contacts2019-04-23T14:45:32ZakwizgranRemove support for inactive contactsSince the introduction client was rewritten we no longer need the concept of inactive contacts. However we still need to be able to specify whether transport keys should initially be active or inactive when adding a contact.Since the introduction client was rewritten we no longer need the concept of inactive contacts. However we still need to be able to specify whether transport keys should initially be active or inactive when adding a contact.akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1274Reproducible Tor builds2018-07-30T16:52:06ZakwizgranReproducible Tor buildsSubtask of #1272.Subtask of #1272.Android 1.1Torsten GroteTorsten Grote