Archive for the ‘Android’ Category
Posted by jpluimers on 2020/03/04
Simple but cool app: [Archive.is] SMS Backup+ – Apps on Google Play:
Automatically backup your SMS, MMS and call history with a separate label in Gmail and Google Calendar.
Later you can restore the saved data (except MMS) back to the phone, especially useful when switching to a new device.
IMAP access needs to be manually enabled in Gmail, see the website and FAQ for more information. You can of course use your own IMAP server for backups, giving you full control over your data.
SMS Backup+ is a free open-source project which has been in active development since the early days of Android, completely ad and tracking-free, supported through voluntary donations.
Sourcecode: [WayBack] GitHub – jberkel/sms-backup-plus: Backup Android SMS, MMS and call log to Gmail / Gcal / IMAP
Via: [WayBack] Wirre Telefongespräche für 500. Ich kriege ja nicht mehr oft Anrufe auf der deutschen Telefonnummer, und so liegt das Telefon jetzt daheim und hängt am… – Kristian Köhntopp – Google+
–jeroen
Like this:
Like Loading...
Posted in Android, Development, Mobile Development, Software Development | Leave a Comment »
Posted by jpluimers on 2020/01/10
Posted in Android, Android Devices, Apple, Development, iMac, Mac, Mac OS X / OS X / MacOS, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, MacMini, macOS 10.12 Sierra, macOS 10.13 High Sierra, Mobile Development, Software Development | Leave a Comment »
Posted by jpluimers on 2019/02/06
For my link archive:
Basically:
- storing encrypted data plus IV in preferences is OK
- store the symmetric encryption key (for instance an AES one) in the keystore for the application
- likely a salt is also needed, then store the salt with the IV and encrypted data
–jeroen
Presumptions:
- The keystore of a specific application UUID is only accessible by only that application UUID when the device has been unlocked by the user
- The keystore saves credentials in a secure way
- It is OK to save both the encrypted data and associated IV
Approach (plain data is “hashed application PIN”, encrypted data is “encrypted hashed application PIN”:
- store a symmetric AES key in the application key store
- after entering application PIN:
- hash the application PIN
- use the hashed application PIN to to enter the application
- from the keystore, obtain the symmetric AES key
- create a cipher based on the AES key
- use the cipher to obtain an IV, and to encrypt the hashed application PIN
- store the encrypted hashed application PIN and IV both in the application preferences
- when needing to enter the application, present the user to either enter the application PIN again or proof that they can pass the device unlock sequence (using an unlock activity)
- if the user provided the application PIN, then:
- hash the application PIN
- try to enter the application with the hashed application PIN
- proved the device unlock, then:
- from the preferences, obtain the IV and encrypted hashed application PIN
- from the keystore, obtain the symmetric AES key
- create a cipher based on the AES key
- decrypt the encrypted hashed application PIN using the cipher and the IV into the hashed application PIN
- try to enter the application with the hashed application PIN
Like this:
Like Loading...
Posted in Android, Development, Mobile Development, Software Development | Leave a Comment »
Posted by jpluimers on 2019/01/30
Hopefully by now the Google Assistant and Google Home have made their way into the Dutch language. If so, then it’s time for me
[WayBack] Quick Intro Into Actions on Google | Grokking Android: Find out which options exist to develop apps for the Google Assistant with Actions on Google and to bring the Assistant to devices with the Assistant SDK.
–jeroen
Like this:
Like Loading...
Posted in Android, Android Devices, Development, Google, Google AI, Google Assistant, GoogleHome, Mobile Development, Software Development | Leave a Comment »
