briar issueshttps://code.briarproject.org/briar/briar/-/issues2024-02-13T07:33:58Zhttps://code.briarproject.org/briar/briar/-/issues/2458Detect whether phone is rooted2024-02-13T07:33:58ZakwizgranDetect whether phone is rootedOWASP guidelines recommend that Android apps should detect whether the phone is rooted. There are libraries that can check for this.OWASP guidelines recommend that Android apps should detect whether the phone is rooted. There are libraries that can check for this.https://code.briarproject.org/briar/briar/-/issues/2437Use `SystemClock#currentNetworkTimeClock()` to diagnose clock sync isses2023-06-28T13:56:25ZTorsten GroteUse `SystemClock#currentNetworkTimeClock()` to diagnose clock sync isses`SystemClock#currentNetworkTimeClock()` may be useful for diagnosing whether clock sync issues are due to misconfiguration or NTP tampering.`SystemClock#currentNetworkTimeClock()` may be useful for diagnosing whether clock sync issues are due to misconfiguration or NTP tampering.https://code.briarproject.org/briar/briar/-/issues/2393Convert blog posts and comments to HTML when composing2023-03-15T12:34:52ZakwizgranConvert blog posts and comments to HTML when composingWhen a blog post or comment is written, do a simple text to HTML conversion before storing the post. For example, wrap the text in a `<p>` tag, convert line breaks to `<p>` tags, and convert URLs to links. This should fix #689 and should...When a blog post or comment is written, do a simple text to HTML conversion before storing the post. For example, wrap the text in a `<p>` tag, convert line breaks to `<p>` tags, and convert URLs to links. This should fix #689 and should make links clickable in blog posts and comments (except for posts/comments written before this feature was implemented).
This is meant to be a simple alternative to #421 or #1038, as we haven't made progress on those more ambitious tickets.Sponsor 6 usability improvementshttps://code.briarproject.org/briar/briar/-/issues/2392Use separate buttons for reblogging (without comment) or commenting on a blog...2023-03-15T12:34:52ZakwizgranUse separate buttons for reblogging (without comment) or commenting on a blog postSponsor 6 usability improvementshttps://code.briarproject.org/briar/briar/-/issues/2335Show warning dialog if Tor detects clock skew2022-06-14T11:54:25ZakwizgranShow warning dialog if Tor detects clock skewThe Tor plugin already listens for STATUS_GENERAL events from Tor and parses CLOCK_SKEW messages. It should use these messages to broadcast EventBus events that can be received by the UI.
The UI should react to these events by showing a...The Tor plugin already listens for STATUS_GENERAL events from Tor and parses CLOCK_SKEW messages. It should use these messages to broadcast EventBus events that can be received by the UI.
The UI should react to these events by showing a warning dialog telling the user to check that the device's time, date and timezone are correct (perhaps with some filtering to ensure that we don't show the dialog again immediately after the user has dismissed it).
The dialog should be shown immediately if clock skew is detected while the app's in the foreground. If clock skew is detected while the app is in the background then the dialog should be shown when the app's brought to the foreground. We may be able to use a LiveEvent for this.https://code.briarproject.org/briar/briar/-/issues/2287Scrub path to Tor config file2022-06-20T17:10:53ZakwizgranScrub path to Tor config fileWhen Tor starts it prints the path to the config file, which we log. On Android this path doesn't contain any sensitive information, but on Desktop it might (eg usernames). We should scrub that line before logging it.When Tor starts it prints the path to the config file, which we log. On Android this path doesn't contain any sensitive information, but on Desktop it might (eg usernames). We should scrub that line before logging it.https://code.briarproject.org/briar/briar/-/issues/2159Power management setup instructions for Tecno phones2022-04-13T10:20:48ZakwizgranPower management setup instructions for Tecno phonesSome Tecno phones have a [padlock button in the recent apps list](https://code.briarproject.org/briar/briar/-/issues/1743#note_49393) that prevents apps from being [killed when the recent apps list is cleared](https://code.briarproject.o...Some Tecno phones have a [padlock button in the recent apps list](https://code.briarproject.org/briar/briar/-/issues/1743#note_49393) that prevents apps from being [killed when the recent apps list is cleared](https://code.briarproject.org/briar/briar/-/issues/992#note_44605). We should find out which phones have this feature and add setup instructions asking the user to lock Briar to the recent apps list.https://code.briarproject.org/briar/briar/-/issues/1963Onboarding when user activates Bluetooth plugin2022-03-04T16:52:31ZTorsten GroteOnboarding when user activates Bluetooth pluginWhen the user is actively turning on the Bluetooth plugin to communicate with users nearby, we should show an onboarding dialog making them aware of the "Connect via Bluetooth" feature accessible in the private conversation.When the user is actively turning on the Bluetooth plugin to communicate with users nearby, we should show an onboarding dialog making them aware of the "Connect via Bluetooth" feature accessible in the private conversation.https://code.briarproject.org/briar/briar/-/issues/1943Warn the user when the last shutdown wasn't clean2021-07-26T10:31:11ZakwizgranWarn the user when the last shutdown wasn't cleanShow some kind of warning (a notification, or something in the main UI when signing in) when the last shutdown wasn't clean (see #57).
We may also want to know whether the dirty shutdown happened before or after the last reboot.
Subtas...Show some kind of warning (a notification, or something in the main UI when signing in) when the last shutdown wasn't clean (see #57).
We may also want to know whether the dirty shutdown happened before or after the last reboot.
Subtask of #1824.https://code.briarproject.org/briar/briar/-/issues/1531Update threat model document2020-11-15T18:57:13ZakwizgranUpdate threat model documentThe [threat model document](https://code.briarproject.org/briar/briar/wikis/threat-model) on the wiki is out of date, and it doesn't mention the goal of concealing the fact that Briar is being used. The document should be updated.The [threat model document](https://code.briarproject.org/briar/briar/wikis/threat-model) on the wiki is out of date, and it doesn't mention the goal of concealing the fact that Briar is being used. The document should be updated.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1481Show outgoing images differently depending on sent/seen state2022-04-19T11:29:25ZTorsten GroteShow outgoing images differently depending on sent/seen stateWhen the image isn't sent, it is shown blurred.
![Image_Attachment_Contact_Offline](/uploads/ea4a802a719627cc0cacf00c2c381329/Image_Attachment_Contact_Offline.png)
When the contact is online and the message was requested, we might show...When the image isn't sent, it is shown blurred.
![Image_Attachment_Contact_Offline](/uploads/ea4a802a719627cc0cacf00c2c381329/Image_Attachment_Contact_Offline.png)
When the contact is online and the message was requested, we might show progress bar:
![Image_Attachment_Sending](/uploads/9c7c01bb0b27677797b0ee6d40120715/Image_Attachment_Sending.png)
Subtask of #1237.https://code.briarproject.org/briar/briar/-/issues/1436AndroidLanTcpPlugin not picking up non-wifi connections2020-11-15T19:52:56ZJulian DehmAndroidLanTcpPlugin not picking up non-wifi connectionsWhen running Briar in Anbox the wifi icon never turns green and lan is not working because it's using `eth0` as interface. We currently only check if we are connected via Wi-Fi or run an AP. The plugin should pick up "wired" connections ...When running Briar in Anbox the wifi icon never turns green and lan is not working because it's using `eth0` as interface. We currently only check if we are connected via Wi-Fi or run an AP. The plugin should pick up "wired" connections if there's no wifi access.
> we just need to make sure it doesn't cause other android devices to treat the mobile data interface as a lan interface (it often gets assigned a lan address due to nat).https://code.briarproject.org/briar/briar/-/issues/1312Include user manual in app2022-11-18T17:32:16ZakwizgranInclude user manual in appA user asked for the manual to be included in the app. This was always the plan but it doesn't look like we had a ticket for it.
Related to #94, #315.A user asked for the manual to be included in the app. This was always the plan but it doesn't look like we had a ticket for it.
Related to #94, #315.CleopatraCleopatrahttps://code.briarproject.org/briar/briar/-/issues/1224Explain when no transports can be used for adding a contact2020-08-12T16:23:17ZakwizgranExplain when no transports can be used for adding a contactWhen adding a contact in person, there are various circumstances where we can tell as soon as we've scanned the contact's QR code that we won't be able to communicate. For example:
* Both devices support Bluetooth, but neither device kno...When adding a contact in person, there are various circumstances where we can tell as soon as we've scanned the contact's QR code that we won't be able to communicate. For example:
* Both devices support Bluetooth, but neither device knows its own Bluetooth address (Android 8, see #1147)
* Both devices support wifi but they're on different networks (see #1223, #1178)
* One device only supports Bluetooth, the other only supports wifi
If the user declines to activate Bluetooth and there's no wifi connection, we can tell even sooner that we won't be able to communicate.
We should detect these situations and explain the problem to the user in an actionable way.https://code.briarproject.org/briar/briar/-/issues/1223Detect whether contact being added is on same wifi network2020-11-18T22:05:45ZakwizgranDetect whether contact being added is on same wifi networkWhen adding a contact in person, it would be useful to be able to detect whether the contact is on the same wifi network. We could do this by including a short hash of the SSID in the QR code.When adding a contact in person, it would be useful to be able to detect whether the contact is on the same wifi network. We could do this by including a short hash of the SSID in the QR code.https://code.briarproject.org/briar/briar/-/issues/1214Don't allow introductions if introducee doesn't support introduction client2022-01-06T14:43:23ZakwizgranDon't allow introductions if introducee doesn't support introduction clientIf the ClientVersioningManager says a contact doesn't support the same major version of the introduction client as us, don't allow an introduction request to be sent.If the ClientVersioningManager says a contact doesn't support the same major version of the introduction client as us, don't allow an introduction request to be sent.https://code.briarproject.org/briar/briar/-/issues/1147Support Bluetooth discovery for adding contacts2022-01-26T13:50:35ZakwizgranSupport Bluetooth discovery for adding contactsThe local Bluetooth address is no longer available on the Nexus 5X running Android 8.1. `BluetoothAdapter#getAddress()` returns the fake address 02:00:00:00:00:00, and `Settings.Secure.getString(ctx, "bluetooth_address")` returns null.
...The local Bluetooth address is no longer available on the Nexus 5X running Android 8.1. `BluetoothAdapter#getAddress()` returns the fake address 02:00:00:00:00:00, and `Settings.Secure.getString(ctx, "bluetooth_address")` returns null.
This means we can no longer include our Bluetooth address in the QR code when adding a contact. Instead we'll need to make the device temporarily discoverable, and indicate in the QR code that the contact should use discovery to find us. The contact will need the ACCESS_COARSE_LOCATION permission for discovery.
The contact will need to store our Bluetooth address for future connection attempts. We don't currently have a way for plugins to store local per-contact information, but we can add one.https://code.briarproject.org/briar/briar/-/issues/1089Setup Wizard page for Sony's power manager2020-11-19T13:20:26ZJulian DehmSetup Wizard page for Sony's power managerStamina mode, Sony's powersaving mode, kills Briar once the screen is turned off. This can be prevented by whitelisting Briar.
Similar to #1088 we could explain it to the user and offer to open the stamina activity.Stamina mode, Sony's powersaving mode, kills Briar once the screen is turned off. This can be prevented by whitelisting Briar.
Similar to #1088 we could explain it to the user and offer to open the stamina activity.https://code.briarproject.org/briar/briar/-/issues/1041Reduce CPU consumption2020-11-19T15:04:11ZakwizgranReduce CPU consumptionFeedback from a user: "I noticed that the app has a high CPU usage. My battery drained noticeably faster than usual, with briar running, and my OS warned me about it using a lot of CPU time."
Related to #44.Feedback from a user: "I noticed that the app has a high CPU usage. My battery drained noticeably faster than usual, with briar running, and my OS warned me about it using a lot of CPU time."
Related to #44.https://code.briarproject.org/briar/briar/-/issues/991Opening private conversation with new contact should hide new contact notific...2020-11-19T14:50:44ZakwizgranOpening private conversation with new contact should hide new contact notificationThe new contact notification that's shown when a contact is introduced should be hidden when opening the contact's private conversation. Touching the notification should open the contact's private conversation.
If multiple contacts have...The new contact notification that's shown when a contact is introduced should be hidden when opening the contact's private conversation. Touching the notification should open the contact's private conversation.
If multiple contacts have been introduced, each contact should be removed from the notification when opening the contact's private conversation, and touching a notification for multiple new contacts should open the contact list. (This is consistent with the behaviour of the private message notification.)