| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
| |
Together with necessary adjustments for Kotlin and build options.
|
| | |
|
| | |
|
| |
|
|
|
| |
Use the more explicit name and shorter description following the
changes in 5a54bf9 and 90d672c.
|
| | |
|
| |
|
|
|
| |
Everything seems to still be working fine in the emulator.
Will need to update Kotlin, its plugins, and Gradle too after.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Moving back the configuration files and logs to the user-accessible
storage. Everything should be accessible through a file manager using
the "USB storage" mode. The embedded FTP server is no longer
necessary.
|
| |
|
|
|
|
|
|
|
| |
Google Play requires apps to target this API level by August 31 2023.
The app builds and seems to work, with the exception of notifications
which require additional runtime permission handling. Those are needed
for the VPN service to be able to report config and runtime errors to
the user.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Recommended and performed by Android Studio's Upgrade Assistant.
|
| | |
|
| |
|
|
| |
The Google Play Store requires targetting >=API 31.
|
| | |
|
| | |
|
| |
|
|
|
| |
JCenter is shutting down.
All used dependencies seem to be available on Maven Central.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is a ridiculous workaround to make the configuration (and other files) accessible to the user
necessary after the new storage access restriction enforced in Android 11 which prevent other
applications from accessing the supposedly public application's directory.
The app's internal private storage directory is now exposed to the user through an embedded FTP
server that the user can turn on and off from the configuration activity. The user can then play
with the configuration and retrieve logs through a remote or local FTP client application of their
choice.
GitHub: closes #103
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The following works from API 21 to 30 (included):
* creating a new network configuration
* private key encryption and decryption
* communication between apps and the tinc daemon
* communication between tinc daemon and the internet
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The following works from API 21 to 29 (included):
* creating a new network configuration
* private key encryption and decryption
* communication between apps and the tinc daemon
* communication between tinc daemon and the internet
The app seems to have issues with the new storage restriction on API 30
(Android 11).
GitHub: closes #97
|
| |
|
|
| |
Hotfix for both Android 5 and 10!
|
| |
|
|
| |
Daemon refuses to start on Android 5 when targeting API 29
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Workaround for new shared memory restrictions added in Android 10
preventing file descriptor leakage to sub-processes.
This change set BREAKS ENCRYPTED PRIVATE KEYS SUPPORT.
GitHub: https://github.com/pacien/tincapp/issues/92
|
| |
|
|
| |
switching from android.support to androidx
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Security update
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
So app can be built by F-Droid
|