briar issueshttps://code.briarproject.org/groups/briar/-/issues2019-06-10T13:48:57Zhttps://code.briarproject.org/briar/briar/-/issues/1564Publish hidden service for connecting to pending contact2019-06-10T13:48:57ZakwizgranPublish hidden service for connecting to pending contactSubtask of #1232.Subtask of #1232.Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1556Add support for handshake keys to KeyManager2019-06-03T14:59:09ZakwizgranAdd support for handshake keys to KeyManagerPart of #1232.Part of #1232.Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1538Generate and store handshake key pair at startup if necessary2019-05-16T13:02:40ZakwizgranGenerate and store handshake key pair at startup if necessarySubtask of #1232.Subtask of #1232.Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1537Implement contact manager methods for pending contacts2019-05-13T09:04:51ZakwizgranImplement contact manager methods for pending contactsSubtask of #1232.Subtask of #1232.Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1536Find out whether intent extras or instance state bundles are persisted by the OS2019-04-22T13:30:11ZakwizgranFind out whether intent extras or instance state bundles are persisted by the OSSince roughly Android 5, the recent apps list has been persisted across reboots. Find out whether intent extras or instance state bundles for the activities in the recent apps list are persisted. If so, this might leak confidential infor...Since roughly Android 5, the recent apps list has been persisted across reboots. Find out whether intent extras or instance state bundles for the activities in the recent apps list are persisted. If so, this might leak confidential information to disk.Android 1.1https://code.briarproject.org/briar/briar/-/issues/1532Upgrade obfs4proxy to 0.0.102020-09-23T14:08:29ZakwizgranUpgrade obfs4proxy to 0.0.10Version 0.0.10 of obfs4proxy has some changes that might make it harder to distinguish meek_lite from ordinary TLS connections.
https://lists.torproject.org/pipermail/tor-dev/2019-April/013776.htmlVersion 0.0.10 of obfs4proxy has some changes that might make it harder to distinguish meek_lite from ordinary TLS connections.
https://lists.torproject.org/pipermail/tor-dev/2019-April/013776.htmlAndroid 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1506Provide a Tor/obfsproxy arm64 binary2019-10-14T16:34:24ZTorsten GroteProvide a Tor/obfsproxy arm64 binary[Starting August 1, 2019](https://android-developers.googleblog.com/2019/01/get-your-apps-ready-for-64-bit.html), all new apps and app updates that include native code are required to provide 64-bit versions in addition to 32-bit version...[Starting August 1, 2019](https://android-developers.googleblog.com/2019/01/get-your-apps-ready-for-64-bit.html), all new apps and app updates that include native code are required to provide 64-bit versions in addition to 32-bit versions when publishing to Google Play.
We currently do not provide 64-bit binaries of Tor and obfsproxy for arm and x86, but should do so.
As the APK size will get quite big with the additional binaries, we should consider split APKs (#1278).Android 1.2Torsten GroteTorsten Grote2019-07-31https://code.briarproject.org/briar/briar/-/issues/1505API 28: Show Soft Keyboard When Activities no longer receive focus2020-02-14T10:34:52ZTorsten GroteAPI 28: Show Soft Keyboard When Activities no longer receive focushttps://developer.android.com/about/versions/pie/android-9.0-changes-28#focus
> Additionally, activities no longer implicitly assign initial focus in touch-mode. Instead, it is up to you to explicitly request initial focus, if desired.
...https://developer.android.com/about/versions/pie/android-9.0-changes-28#focus
> Additionally, activities no longer implicitly assign initial focus in touch-mode. Instead, it is up to you to explicitly request initial focus, if desired.
When entering the password, creating groups, forums or writing blog posts, the keyboard is shown initially, because the input fields receive focus. On API 28, we can't rely on this anymore and should use explicit keyboard states instead.Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1501Show new contacts at the top of the contact list2019-03-22T16:54:17ZTorsten GroteShow new contacts at the top of the contact listCurrently, new contacts get added to the bottom of the list. They should be at the top for better visibility.Currently, new contacts get added to the bottom of the list. They should be at the top for better visibility.Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1498Use Meek-Lite pluggable transport in China2019-02-22T12:28:21ZTorsten GroteUse Meek-Lite pluggable transport in ChinaThe obfs4 project [includes a meek-likte transport](https://github.com/Yawning/obfs4/tree/master/transports/meeklite) that we could use to circumvent Tor censorship in China.The obfs4 project [includes a meek-likte transport](https://github.com/Yawning/obfs4/tree/master/transports/meeklite) that we could use to circumvent Tor censorship in China.Android 1.1Torsten GroteTorsten Grote2019-02-28https://code.briarproject.org/briar/briar/-/issues/1497Check whether ongoing notification's priority and importance need to be incre...2019-02-21T12:41:39ZakwizgranCheck whether ongoing notification's priority and importance need to be increasedThis blog post describes some "guidelines" for a foreground service's ongoing notification:
https://android-developers.googleblog.com/2018/12/effective-foreground-services-on-android_11.html
> There are some guidelines around creating ...This blog post describes some "guidelines" for a foreground service's ongoing notification:
https://android-developers.googleblog.com/2018/12/effective-foreground-services-on-android_11.html
> There are some guidelines around creating and managing foreground services. For all API levels, a persistent notification with at least PRIORITY_LOW must be shown while the service is created. When targeting API 26+ you will also need to set the notification channel to at least IMPORTANCE_LOW.
Our ongoing notification uses PRIORITY_MIN and the channel uses IMPORTANCE_NONE. Find out whether this affects how the system treats our foreground service, especially on API 26+.
Related to #1146. Subtask of #1260.Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1496Check whether we're affected by implicit broadcast restrictions on Android 8+2019-02-21T10:32:35ZakwizgranCheck whether we're affected by implicit broadcast restrictions on Android 8+Apps targetting Android 8+ don't receive certain implicit broadcasts. Check whether we're affected.
https://developer.android.com/about/versions/oreo/background
Subtask of #1260.Apps targetting Android 8+ don't receive certain implicit broadcasts. Check whether we're affected.
https://developer.android.com/about/versions/oreo/background
Subtask of #1260.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1487Investigate OOM errors in nightly tests2021-08-27T11:34:07ZakwizgranInvestigate OOM errors in nightly testsThe nightly tests have started to fail regularly due to OOM errors. Investigate whether memory usage has increased significantly.The nightly tests have started to fail regularly due to OOM errors. Investigate whether memory usage has increased significantly.Android 1.3akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1468Restrict size of image attachments2021-06-28T08:08:18ZTorsten GroteRestrict size of image attachmentsWe can not process images of arbitrary size, because the device may lack the memory to load the entire image into it or because the maximum texture size is smaller than the image.
* [x] don't read entire images in memory
* [x] scale ful...We can not process images of arbitrary size, because the device may lack the memory to load the entire image into it or because the maximum texture size is smaller than the image.
* [x] don't read entire images in memory
* [x] scale full screen images down to screen size to avoid exceeding max texture size
* [x] add tests for [MarkEnforcingInputStream](https://github.com/bumptech/glide/blob/ad33b8d503024c8a3a6a3da60ce28c4d7732ae58/library/src/main/java/com/bumptech/glide/util/MarkEnforcingInputStream.java)
* [x] tests for our own code that handles the various image types and edge cases
* [x] limit our supported mime types to image/gif, image/jpeg and image/png
* [x] limit the size of images that can be sent
Subtask of #1237.Android 1.3Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1467Improve Conversation Scrolling Behaviour2019-06-17T10:10:29ZTorsten GroteImprove Conversation Scrolling BehaviourCurrently, we scroll down after loading the list of messages (after each activity start). We also scroll down when loading a message text or image asynchronously.
This is problematic, because the user can't scroll up right after a large...Currently, we scroll down after loading the list of messages (after each activity start). We also scroll down when loading a message text or image asynchronously.
This is problematic, because the user can't scroll up right after a large conversation is displayed and because when looking at older photos, the user forcibly gets scrolled to the end of the conversation and needs to find where she was.
Subtask of #1242Android 1.3Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1452Websocket Authentication2018-11-27T10:00:33ZTorsten GroteWebsocket AuthenticationDespite many (older) claims in the internet that you can establish websocket connections with basic auth, this doesn't seem to be true for javascript libraries running in a recent browser. I managed to do it in Python and assumed it will...Despite many (older) claims in the internet that you can establish websocket connections with basic auth, this doesn't seem to be true for javascript libraries running in a recent browser. I managed to do it in Python and assumed it will just work on browsers as well, but it seems that isn't the case. At least I haven't been able to make this work. The only thing we can send in the upgrade request from a browser is a list of protocols. In absence of a standardized authentication mechanism, there's people using this already to pass auth tokens. I confirmed that we can access this header on the server side and check if there's an auth token in it.
If we don't want that hacky (but easy) solution, I am afraid we need to get into the business of tracking each session's authentication state and require them to send a first message with the token before we start sending stuff to it. Maybe even terminate sessions that haven't authenticated after a timeout.Headless MVPTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1451"All in briar-headless" run configuration runs tests in other modules2018-11-07T17:47:51Zakwizgran"All in briar-headless" run configuration runs tests in other modulesThe "All in briar-headless" run configuration in Android Studio runs tests in other modules as well as briar-headless. It seems to be picking up JUnit 4 tests from all modules.The "All in briar-headless" run configuration in Android Studio runs tests in other modules as well as briar-headless. It seems to be picking up JUnit 4 tests from all modules.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1450"All tests" run confguration doesn't run briar-android tests2018-11-27T10:00:04Zakwizgran"All tests" run confguration doesn't run briar-android testsThe "All tests" run configuration for Android Studio stops after running the briar-headless tests, so the briar-android tests aren't run.The "All tests" run configuration for Android Studio stops after running the briar-headless tests, so the briar-android tests aren't run.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1442Use v3 hidden service for crash reports and feedback2021-11-17T13:38:12ZakwizgranUse v3 hidden service for crash reports and feedbackVersions of Briar that support v3 hidden services should use a v3 service for crash reports and feedback. The old service can be retired eventually when most users have upgraded.
Creating this here rather than in https://code.briarproje...Versions of Briar that support v3 hidden services should use a v3 service for crash reports and feedback. The old service can be retired eventually when most users have upgraded.
Creating this here rather than in https://code.briarproject.org/briar/admin because it requires some small code changes.https://code.briarproject.org/briar/briar/-/issues/1435[android] Migrate to HtmlCompat2020-08-14T11:32:43ZTorsten Grote[android] Migrate to HtmlCompat`UiUtils#getSpanned()` should use the new HtmlCompat.
https://commonsware.com/blog/2018/05/29/at-last-htmlcompat.html`UiUtils#getSpanned()` should use the new HtmlCompat.
https://commonsware.com/blog/2018/05/29/at-last-htmlcompat.htmlAndroid 1.2