optional encryption of the device

yes, I got some unofficial confirmation on IRC, but it has low priority at the moment, so vote it up

Any information if this full device encryption available on next (March) update?

modprobe ecryptfs works. So people with developer mode can play with CLI.

Also add the ability of precting the sd card with a password in a future update please. :)

any news on this? How high (or low) on the priority list is this?

Is the full device encryption feature part of Sailfish OS 2?

if there was the option of activating the boot screen with a virtual keyboard, we could just mount /home to the crypt-device. Would this be so hard to implement?

Thank you for the tip, has anyone tried this on SailfishOS 2 maybe? How does cryptsetup know what key to use, is it stored on the disk somewhere? Also, would it be much different to use luks (and safer as well, as in easier not to overwrite your data eg.)?

Hello, all! Is it possible to put this into one complete "instruction manual" to move everything into an encrypted "box"? I have nothing against some work in the terminal, but see: a newbie would have some trouble with these instructions. To be able to learn, some explanation would be nice. For instance, the usage of the instructions means that you make up a whole new file system on the SD card. The stuff on the SD card will be lost! This should be written down in there! Furthermore: is it possible to use it on the whole "home" folder? I am not so much into linux, so I'd better ask. As far as I see, you mount the SD card into /home/crypto and link the original pictures folder to a new encrypted folder on the SD card. Is this right? Such comments would make it far more readable and understandable for any newbie. What does the line "do the same with .cache/.nemothumbs" exactly mean? until I know this, I won't start working on a running system. How would I make a backup and put it back, if parts of the system were encrypted? Would this work?

Hi,

my Jolla phone broke a few month after I wrote this comment. It had this series defect with the battery. I never touched a Jolla again. And I never will!

For me the Nokia N9 is still the best phone ever.

But the Jolla thing was garbage in hard- and software. And it was a fraud to sell this prototype as a product. Even basic functionality wasn't working well.

Maybe they wanted to much. they had fancy GUI, android support etc. everything with bugs. Instead cronstructing just a simple and working, phone. Someone who wants to run android applications just buys an android tlephone.

I thought Jolla was bankrupt and dead. now I read on wikipedia that the last release of the OS was a few month ago ...

Too bad for you. :-(

Could you please still read your text and hopefully answer most of my questions? Thank you in advance! Especially "do the same with .cache/.nemothumbs" is of interest.

Well, I see your comment very differently. The Sailfish OS works - except for anything that needs the Google stuff. But I use my smartphone only as second device besides my laptop, so I am not so much affected by it. I have had a device, which has lost connection to the battery all the time. But I think that for the first device, it was not such a bad product. If I remember the iPhone 1, I would say that the Jolla was more useable and you were able to add functionality by yourself if you wanted to learn or ask. I don't want to use Android apps, but unfortunately there are some that work. I like the principle in Sailfish OS from Unix: "Do one thing and do it well". I have found many apps with minor functionality to Android apps, but they do their work well. And: I have control above my own data. I have a home folder which is analog to my linux laptop. I can install very many stuff on the command line as a user who wants to know how and what. Here might be the difference: Jolla is not a phone for the iPhone user. It is one for people who are interested in how it works and who would do some research in forums and the internet to find out, how to get something working - like the encryption. :-) If you have your old device, try to get it working. :-) I still like it better than my old iPhone or my new Nokia 5. For me, it is more usable and much faster in every day use. Cheers!

Truecrypt is IMHO not a good fit here as it creates containers with a fixed size. Additionally there may be license issues as the Truecrypt license allows to view the source code but prohibits changing it.

"WARNING: Using TrueCrypt is not secure as it may contain unfixed security issues" see: http://www.truecrypt.org/

@utkiek "...as any written software on the planet" :-)

@schmittlauch@utkiek TrueCrypt should work out as intended, audit came out clean. And there are optional forks, like VeraCrypt being actively developed - it supports TrueCrypt-containers too. While dm-crypt with luks might be the best option, having support for encrypted containers made with True/VeraCrypt would be really nice to have.

why use a non-free unsupported software, when there is a free and supported one (dm_crypt/luks) in linux?

just repeating my comment from 26th Dec... WTF?

@ortylp Sry did not read the comments and this is a valid answer and not a comment! I talked to aard myself.

Simply use Secrecy an Android app that encrypts image and file data, you would have to copy it into the container and delete the unprotected file.

http://m.playboi2nv.store.aptoide.com/app/market/com.doplgangr.secrecy/53/7898510/SECRECY+-+Encrypt%2FHide+Files+α#

No, we probably will never get 4.1, at least not for the phone.

@chemist please explain ...

As long as Qualcomm sits on their drivers we are stuck with what we have now, and as it is very unlikely that they upgrade them even themselves there won't be a newer Kernel possible.

that is disappointing