briar issueshttps://code.briarproject.org/groups/briar/-/issues2021-05-05T16:08:09Zhttps://code.briarproject.org/briar/briar/-/issues/1827Raise target API level to 302021-05-05T16:08:09ZakwizgranRaise target API level to 30Adapt to changes in the Android platform2021-04-30https://code.briarproject.org/briar/briar-gtk/-/issues/84Use Briar blue instead of theme selected color2020-12-16T14:02:59ZNicoUse Briar blue instead of theme selected colorCurrently we use [`@theme_selected_bg_color`](https://code.briarproject.org/briar/briar-gtk/-/blob/154be3dcfe2c93f5cf66f25f1b356e54653175a1/briar-gtk/data/ui/application.css#L67) for things like usernames. This is mostly blue, but on e.g...Currently we use [`@theme_selected_bg_color`](https://code.briarproject.org/briar/briar-gtk/-/blob/154be3dcfe2c93f5cf66f25f1b356e54653175a1/briar-gtk/data/ui/application.css#L67) for things like usernames. This is mostly blue, but on e.g. Linux Mint it's green. There, the difference between own and their usernames is not visible that much, because both names are colored in green. We should use the Briar blue code instead, so that we have blue-green on all platforms.GTK 0.1.0-beta3x0lootsx0lootshttps://code.briarproject.org/briar/briar/-/issues/1826Finish migrating SettingsFragment to ViewModel2021-04-01T13:22:18ZakwizgranFinish migrating SettingsFragment to ViewModelA ViewModel for Settings has been introduced in #214 ([`214-user-avatars`](https://code.briarproject.org/briar/briar/-/tree/214-user-avatars)). The rest of the non-UI logic should get migrated there and exposed via LiveData.
Subtask of ...A ViewModel for Settings has been introduced in #214 ([`214-user-avatars`](https://code.briarproject.org/briar/briar/-/tree/214-user-avatars)). The rest of the non-UI logic should get migrated there and exposed via LiveData.
Subtask of #1823.Adapt to changes in the Android platformTorsten GroteTorsten Grote2021-04-30https://code.briarproject.org/briar/briar-gtk/-/issues/76Handle error when adding pending contact2021-03-09T10:34:35ZNicoHandle error when adding pending contactFound by @grote in https://code.briarproject.org/briar/python-briar-wrapper/-/issues/19.
We should definitely fix this in the next release. For now, all we seem to be able to do is tell users about the failure. Once https://code.briarpr...Found by @grote in https://code.briarproject.org/briar/python-briar-wrapper/-/issues/19.
We should definitely fix this in the next release. For now, all we seem to be able to do is tell users about the failure. Once https://code.briarproject.org/briar/briar/-/issues/1825 is done, we can offer ways to fix the error.
When implementing this issue, we have to keep in mind that attackers might want to know if a user already has a contact, i.e. exploring the contacts relationships of the targeted user.
In general Briar GTK should start to properly handle errors. When doing this, the documentation of Briar Headless should be improved, too.GTK 0.1.0-beta3NicoNicohttps://code.briarproject.org/briar/briar/-/issues/1825Unspecific 500 Server Error when adding already existing pending contact2021-05-05T16:15:44ZNicoUnspecific 500 Server Error when adding already existing pending contact@grote found https://code.briarproject.org/briar/python-briar-wrapper/-/issues/19 where he encountered problems when re-adding an already existing pending contact.
I tried to somehow handle those error in _briar_wrapper_, but the respon...@grote found https://code.briarproject.org/briar/python-briar-wrapper/-/issues/19 where he encountered problems when re-adding an already existing pending contact.
I tried to somehow handle those error in _briar_wrapper_, but the response by Briar Headless is always just `500: Internal server error`. I get this when adding a pending contact after
* it has already been added seconds before and the peer is offline
* it has already been added more than 4 days before (manually changed system time) and the peer was offline all the time
* the pending contact got already added days before and left the pending state
* the link is invalid (I think so, just changed some characters)
* and for sure there are more errors
The problem is that [in this line](https://code.briarproject.org/briar/briar/-/blob/01a146ba71743e3709bd6e56052558da95abfbed/briar-headless/src/main/java/org/briarproject/briar/headless/contact/ContactControllerImpl.kt#L96) `contactManager.addPendingContact` gets called without catching its exceptions. Looking [at its implementation](https://code.briarproject.org/briar/briar/-/blob/01a146ba71743e3709bd6e56052558da95abfbed/bramble-core/src/main/java/org/briarproject/bramble/contact/ContactManagerImpl.java#L136), there are at least `DbException, FormatException, GeneralSecurityException` that get thrown.NicoNicohttps://code.briarproject.org/briar/briar/-/issues/1824Adapt to power management restrictions2021-04-30T13:42:29ZakwizgranAdapt to power management restrictionsAdapt to changes in the Android platform2021-04-30https://code.briarproject.org/briar/briar-mailbox/-/issues/8Receive RSS feeds shared by other apps2022-11-01T10:00:29ZakwizgranReceive RSS feeds shared by other appsReceive RSS feeds shared by other apps in the form of XML files.
When a feed is received for the first time, ask the user whether to accept it. If the user accepts the feed it becomes available for download (see #6) and updates to the f...Receive RSS feeds shared by other apps in the form of XML files.
When a feed is received for the first time, ask the user whether to accept it. If the user accepts the feed it becomes available for download (see #6) and updates to the feed shared by the same app are accepted automatically.Mailbox2022-10-31https://code.briarproject.org/briar/briar/-/issues/1821Bluetooth setup screen2021-08-31T13:11:23ZakwizgranBluetooth setup screenReflected transport properties should enable most devices to learn their own Bluetooth addresses, but there's still a bootstrapping problem when a group of two or more contacts are all running Android 8.1+ and none of them added each oth...Reflected transport properties should enable most devices to learn their own Bluetooth addresses, but there's still a bootstrapping problem when a group of two or more contacts are all running Android 8.1+ and none of them added each other via Bluetooth.
We could solve this by adding a "Bluetooth setup" workflow. If the user activates the Bluetooth plugin and we don't know the device's address, we tell the user that Bluetooth needs to be set up and that they need a contact nearby to help with this. When both users are ready, we perform discovery, show a list of devices, and ask the users to pick each other's devices. If the devices succeed in making a connection they'll learn each other's addresses and exchange them via reflected transport properties.Adapt to changes in the Android platformTorsten GroteTorsten Grote2021-04-30https://code.briarproject.org/briar/briar/-/issues/1820Use briar-debug alongside briar: tor socket already in use2022-02-25T15:05:47ZToni MarschallUse briar-debug alongside briar: tor socket already in useHello,
is it somehow possible to run briar-debug alongside briar?
Both are installed on my device but only the first startup app got an internet connection. The status on the second app is "Your phone has Internet access via Wi-Fi. Bri...Hello,
is it somehow possible to run briar-debug alongside briar?
Both are installed on my device but only the first startup app got an internet connection. The status on the second app is "Your phone has Internet access via Wi-Fi. Briar can't connect to the Internet". In the debug log i can read that a server socket is already bound and a connection to some local ips in not possible (tor?).
Is there a workaround?
```
...
2020-10-30 10:09:28.762 6449-9468/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.49.1 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9456/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.1.80 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9457/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.1.78 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9456/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.1.48 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9457/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.0.253 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9456/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.0.82 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9457/org.briarproject.briar.android.debug I/TcpPlugin: 10.0.0.10 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9456/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.0.175 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9457/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.43.1 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9456/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.43.1 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9457/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.49.1 is not connectable from 192.168.8.113
2020-10-30 10:09:28.763 6449-9456/org.briarproject.briar.android.debug I/TcpPlugin: 192.168.49.1 is not connectable from 192.168.8.113
...
2020-10-30 10:09:29.009 6449-9464/org.briarproject.briar.android.debug I/TcpPlugin: Server socket already bound
...
```
My home network is 192.168.8.x
Thankshttps://code.briarproject.org/briar/briar/-/issues/1819Crash if screen is rotated during setup and "Create Account" is tapped twice2021-07-06T10:03:53ZakwizgranCrash if screen is rotated during setup and "Create Account" is tapped twiceI got the following crash on the Nokia 3.1 (Android 10) while trying to reproduce another bug. During setup, I rotated the screen to landscape and back to portrait after tapping "Create Account", which caused the progress wheel to disapp...I got the following crash on the Nokia 3.1 (Android 10) while trying to reproduce another bug. During setup, I rotated the screen to landscape and back to portrait after tapping "Create Account", which caused the progress wheel to disappear and the "Create Account" button to reappear. I tapped the button again and Briar crashed:
```
2020-10-29 10:58:16.219 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Destroying StartupActivity
2020-10-29 10:58:16.224 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Stopping SplashScreenActivity
2020-10-29 10:58:16.229 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Destroying SplashScreenActivity
2020-10-29 10:58:28.199 10998-11087/org.briarproject.briar.android.debug I/SetupControllerImpl: Creating account
2020-10-29 10:58:28.380 10998-11087/org.briarproject.briar.android.debug I/IdentityManagerImpl: Creating identity took 178 ms
2020-10-29 10:58:28.381 10998-11087/org.briarproject.briar.android.debug I/IdentityManagerImpl: Identity registered
2020-10-29 10:58:29.328 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Pausing SetupActivity
2020-10-29 10:58:29.343 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Stopping SetupActivity
2020-10-29 10:58:29.412 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Destroying SetupActivity
2020-10-29 10:58:29.614 10998-11087/org.briarproject.briar.android.debug I/ScryptKdf: KDF cost parameter 8192
2020-10-29 10:58:30.015 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Creating SetupActivity
2020-10-29 10:58:30.087 10998-11087/org.briarproject.briar.android.debug I/ScryptKdf: Deriving key from password took 472 ms
2020-10-29 10:58:30.213 10998-11087/org.briarproject.briar.android.debug I/AndroidKeyStrengthener: Loaded key from keystore
2020-10-29 10:58:30.338 10998-11087/org.briarproject.briar.android.debug I/AccountManagerImpl: Storing database key in file
2020-10-29 10:58:30.341 10998-11087/org.briarproject.briar.android.debug I/AccountManagerImpl: Created database key directory
2020-10-29 10:58:30.344 10998-11087/org.briarproject.briar.android.debug I/AccountManagerImpl: Stored database key in backup file
2020-10-29 10:58:30.345 10998-11087/org.briarproject.briar.android.debug I/AccountManagerImpl: Renamed backup file to primary
2020-10-29 10:58:30.347 10998-11087/org.briarproject.briar.android.debug I/AccountManagerImpl: Stored second copy of database key in backup file
2020-10-29 10:58:30.354 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Starting SetupActivity
2020-10-29 10:58:30.366 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Resuming SetupActivity
2020-10-29 10:58:33.257 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Pausing SetupActivity
2020-10-29 10:58:33.261 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Stopping SetupActivity
2020-10-29 10:58:33.288 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Destroying SetupActivity
2020-10-29 10:58:33.623 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Creating SetupActivity
2020-10-29 10:58:33.968 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Starting SetupActivity
2020-10-29 10:58:33.980 10998-10998/org.briarproject.briar.android.debug I/BaseActivity: Resuming SetupActivity
2020-10-29 10:58:36.130 10998-11087/org.briarproject.briar.android.debug I/SetupControllerImpl: Creating account
2020-10-29 10:58:36.132 10998-11087/org.briarproject.briar.android.debug E/AndroidRuntime: FATAL EXCEPTION: pool-3-thread-1
Process: org.briarproject.briar.android.debug, PID: 10998
java.lang.AssertionError: Already have a database key
at org.briarproject.bramble.account.AccountManagerImpl.createAccount(AccountManagerImpl.java:169)
at org.briarproject.briar.android.account.SetupControllerImpl.lambda$createAccount$0$SetupControllerImpl(SetupControllerImpl.java:111)
at org.briarproject.briar.android.account.-$$Lambda$SetupControllerImpl$bM_lMydguKzowB8BXIvR9b0joQw.run(Unknown Source:8)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
```Adapt to changes in the Android platformIvanaIvana2021-04-30https://code.briarproject.org/briar/briar-mailbox/-/issues/7Status screen2022-02-07T09:46:52ZakwizgranStatus screenDesign and implement a status screen showing whether the mailbox is running, whether it has internet access, whether it's connected to Tor, and how much data is waiting to be downloaded by contacts and the owner.Design and implement a status screen showing whether the mailbox is running, whether it has internet access, whether it's connected to Tor, and how much data is waiting to be downloaded by contacts and the owner.Mailbox: Status UI for Mailbox app2022-10-31https://code.briarproject.org/briar/briar-mailbox/-/issues/6Implement RSS API2022-11-17T14:30:52ZakwizgranImplement RSS APIImplement the RSS endpoints of the mailbox REST API. These endpoints allow the owner to receive a list of feeds offered by the mailbox (including the time when each feed was last updated) and download feeds.
Related to briar#1809 and br...Implement the RSS endpoints of the mailbox REST API. These endpoints allow the owner to receive a list of feeds offered by the mailbox (including the time when each feed was last updated) and download feeds.
Related to briar#1809 and briar#1810. Depends on briar#1804.RSS import2022-10-31https://code.briarproject.org/briar/briar-mailbox/-/issues/5Implement file management API2022-02-07T09:47:08ZakwizgranImplement file management APIImplement the file management endpoints of the mailbox REST API.
Related to briar#1807 and briar#1808. Depends on briar#1804.Implement the file management endpoints of the mailbox REST API.
Related to briar#1807 and briar#1808. Depends on briar#1804.Mailbox: File management APITorsten GroteTorsten Grote2022-10-31https://code.briarproject.org/briar/briar/-/issues/1812Update own mailbox's contact list when contacts are added or removed2022-08-12T12:44:40ZakwizgranUpdate own mailbox's contact list when contacts are added or removedWhen a contact is added, updated or deleted, queue an update on any open connections to the user's own mailbox.
Related to briar-mailbox#4, #2188. Depends on #2182, #2183, #2187, #2184.When a contact is added, updated or deleted, queue an update on any open connections to the user's own mailbox.
Related to briar-mailbox#4, #2188. Depends on #2182, #2183, #2187, #2184.Mailbox: Contact management API2022-10-31https://code.briarproject.org/briar/briar-mailbox/-/issues/4Implement contact management API2022-02-07T09:47:07ZakwizgranImplement contact management APIImplement the contact management endpoints of the mailbox REST API. These endpoints allow the owner to add, update and remove contacts.
Depends on briar#1804.Implement the contact management endpoints of the mailbox REST API. These endpoints allow the owner to add, update and remove contacts.
Depends on briar#1804.Mailbox: Contact management APISebastianSebastian2022-10-31https://code.briarproject.org/briar/briar-mailbox/-/issues/3Publish hidden service2022-05-16T14:48:58ZakwizgranPublish hidden serviceWrite backend code to install Tor and obfs4proxy binaries if necessary, manage a Tor process, and publish a hidden service.
This can start as a copy of the corresponding code in Briar's TorPlugin. If we identify code that ought to be sh...Write backend code to install Tor and obfs4proxy binaries if necessary, manage a Tor process, and publish a hidden service.
This can start as a copy of the corresponding code in Briar's TorPlugin. If we identify code that ought to be shared rather than copied we can refactor it into a library.
Depends on #46.Mailbox: TorTorsten GroteTorsten Grote2022-10-31https://code.briarproject.org/briar/briar-mailbox/-/issues/2Mailbox pairing with Briar2022-02-07T09:47:08ZakwizgranMailbox pairing with BriarDesign and implement a UI and backend for pairing the mailbox with Briar.
This is the mailbox counterpart of briar#1805. Depends on briar#1804.Design and implement a UI and backend for pairing the mailbox with Briar.
This is the mailbox counterpart of briar#1805. Depends on briar#1804.Mailbox: Pairing2022-10-31https://code.briarproject.org/briar/briar-mailbox/-/issues/1Manage app lifecycle2022-07-13T11:02:06ZakwizgranManage app lifecycleDefine the app lifecycle and create a portable (Android + J2SE) lifecycle component that can register other components to be started and stopped. On Android, use a foreground service.Define the app lifecycle and create a portable (Android + J2SE) lifecycle component that can register other components to be started and stopped. On Android, use a foreground service.Mailbox: Manage app lifecycleSebastianSebastian2022-10-31https://code.briarproject.org/briar/briar/-/issues/1811Update Bramble protocol stack to support syncing via mailbox2022-08-17T10:09:50ZakwizgranUpdate Bramble protocol stack to support syncing via mailboxWhen communicating via mailboxes, the max latency and thus the retransmission interval are very long, so we need to be careful about any circumstances that could cause messages to be lost.
On the sender side, if an error (such as an IO ...When communicating via mailboxes, the max latency and thus the retransmission interval are very long, so we need to be careful about any circumstances that could cause messages to be lost.
On the sender side, if an error (such as an IO error, app crash or device crash) occurs while we're writing messages to a file, we need to ensure that those messages can be sent again after recovering from the error. Ideally this should apply to acks too.
On the receiver side, if an error occurs while we're reading messages from a file, we need to ensure that the file can be read again after recovering from the error.Mailbox2022-10-31https://code.briarproject.org/briar/briar/-/issues/1810Download RSS feeds from mailbox2022-11-17T14:30:25ZakwizgranDownload RSS feeds from mailboxWrite backend code for downloading RSS feeds offered by the mailbox, parsing the feeds and creating Briar blog posts for any new feed items.
Only feeds the user has subscribed to (see #1809) should be downloaded.
Depends on #1804.Write backend code for downloading RSS feeds offered by the mailbox, parsing the feeds and creating Briar blog posts for any new feed items.
Only feeds the user has subscribed to (see #1809) should be downloaded.
Depends on #1804.RSS import2022-10-31