Also note that nowadays ext4 filesystem natively supports per-directory encryption which may allow a more efficient and better integrated way to encrypt /home. replying to myself: this is called filesystem-based encryption. Here is the relevant documentation for the part living inside the Linux kernel. Appears that Android nowadays also uses this for providing user-data encryption (albeit with a different user-space tooling). As this allows very fine-grained encryption of specific directories only, it may be easier to integrate with LightDM, i.e. maybe not requiring a full restart of LightDM after unlocking just some of the more privacy-relevant directories. Both recent LUKS versions and fscrypt userspace can process the disk encryption password via Argon 2. If you choose sufficiently CPU-intensive parameters for Argon 2 (e.g. multi-second execution time, 4 CPU threads, 512 MB of RAM), then even a password with 40 bits of entropy will be very costly to break using a GPU based brute-force atttack. If one believes the (pretty outdated) claims on the argon2-gpu gitlab page, then the Argon2 settings that I use with LUKS on my Volla22: PBKDF: argon2id Time cost: 12 Memory: 500000 Threads: 4 only allow for roughly 8 password attempts per seconds when brute-forcing on a NVIDIA Tesla K20X. That's only 2^28 password attempts per year and GPU!? Note that Argon2 support in LUKS is not available on the older 16.04 version of UBports, you need 20.04 (focal).

You can install what you want on any UT device if you make its file system read/write. But if you do that, which is not a supported way using UT, you'll be then the only one to deal with any issue, including breaking the system, you could encounter. AND you'll no longer should make OTA updates as it will overwrite some or all of the customisations you made, with a result depending on which parts where modded (from system bug to device not booting anymore). If you really want to mess with your UT, search the forum how you can make the system read/write. There is also a telegram group for people like you that are not feared "breaking" UT.

@developerbayman no, it was not dropped. In development and testing scenarios it is still used. It just isn't supported, as in if you experience issues after using apt, you would need to return to a clean system and retest before asking for help on your issues. I'm that sense we mean it is not supported.

Hi @Homer3 This is Tide: https://github.com/fredldotme/Tide?tab=readme-ov-file#tide---the-touch-friendly-ide An IDE for development of Ubuntu Touch on Ubuntu Touch.

@Timespansoul said in Issues building lomiri-telephony-service: @lduboeuf Will the merge request lead to an updated control file? It has been merged to ubports/focal, so yes.

@rocket2nfinity Sadly I have noticed this My Nexus 6P isn't maintained anymore, my PinePhone Pro is just bad, and my Fairphone 5 doesn't have a public release yet. I can't win lol

thanks

Hi, the problem was not dekko directly. My mail provider allows only check/sync every 15 minutes. Dekko sync -out of the box- every 5 minutes. Seemingly the syncs where blocked. After configure sync every 15 minutes it works.

Hi I think I understand the problem. On the first try, I has added the NC account and nothing happens. I added the account again right away. the result was the empty calendar. So remove both account entrys. Add one nc account and wait wait wait even if the account is not yet visible. After any minutes the account will be shown and the sync is working.

@Luksus @danfro I tried it and it worked. This is great. I hope it is integrated into the VPN settings. It is simple and makes things much easier. This is a request. I hope you will consider it. Thank you.

@naizena Weird. I wonder what the difference is?

@wayneoutthere this would be great. Also, I might add OMEMO encryption would be cool too.

@ikoz It's my Phone the problem I think (Redmi note 9 pro)

@ikoz said in Ubuntu Touch ARM TrustZone Support: Is the manufacturer the chip's (e.g. Qualcomm) or the phone's who signs the keys It would stand to reason that the device manufacturers would be the ones doing th signing with their keys. Or better said, whoever is responsible for the OS image that is pre-installed on the device. If it's the latter then do all devices which have UT pre installed also have locked bootloader? I expect that they could do so. But not having such a device myself, I cannot say for sure.

@techgeekunited There is not one IMG for Ubuntu Touch. There is as much images as there are ported devices. And those images are managed by UBports installer when installing to a device.

Thanks! I was wondering what default sudo password was.