| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
The Google Play Store requires targetting >=API 31.
|
| |
|
|
|
| |
The previous channel got deleted from Freenode for no apparent reason.
Let us follow the #tinc channel and move to Libera.Chat too.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: pacien <pacien.trangirard@pacien.net>
|
| |
|