About device encrypted (DE) storage with owner lock pin/password

grayway2

Can we expect this improvement to be implemented the next month ?

GrapheneOS

grayway2 No. It's a long term plan.

grayway2

Package names, size of files, modified date of files, saved Wi-Fi SSID+ passwords, wallpaper, Bluetooth connections , device settings and much more must be protected by a user password before early boot process.

Our devices should not connect the WiFi without a user authentication pin/password after a reboot. We don't have to always enable airplane mode before powering off our phones to expect the device to be cut from networks after turning them on again ect.

GrapheneOS

grayway2

Our devices should not connect the WiFi without a user authentication pin/password after a reboot. We don't have to always enable airplane mode before powering off our phones to expect the device to be cut from networks after turning them on again ect.

It should still be able to make emergency calls.

grayway2

GrapheneOS thanks for clarification. I'm a bit enthusiast and forget the amount of works behind such feature.

grayway2

GrapheneOS Yes, but only after the device move from BFU to an AFU state.

Emergency calls are used most of the time in AFU. You don't really keep your phone off and suddenly power it on to call emergency services.

GrapheneOS

grayway2 It does need to work in that situation. It worked there with the old boot passphrase implementation.

fid02

grayway2 Emergency calls are used most of the time in AFU. You don't really keep your phone off and suddenly power it on to call emergency services.

If for instance someone has set a low value for autoreboot… if you need to call emergency services but it requires the phone to be unlocked, you'll have to enter the device credentials before you can call for help. Or if someone else picks it up to call an emergency number in that situation, they won't be able to do that without you unlocking the device. Hopefully that person will have their own phone, but if not, or if their phone is out of battery… I think the potential risks to personal safety are quite clear. I'm glad it does work BFU and I'm glad there are no plans to change that.

grayway2

GrapheneOS Currently, an android phone can bypass airplane mode in BFU and connect to emergency services with a saved WiFi because of DE encryption storage space.

Are you gonna be selective of what will remain encrypted with DE ? (Like updates install after reboot without user credential)

Or only emergency calls with or without a sim card will work depending the region we live.

GrapheneOS

grayway2

Are you gonna be selective of what will remain encrypted with DE ? (Like updates install after reboot without user credential)

We can't be selective about it since we want to make metadata encryption use the Owner user passphrase, not only filenames and data blocks.

Currently, an android phone can bypass airplane mode in BFU and connect to emergency services with a saved WiFi because of DE encryption storage space.

There's a planned toggle for controlling if emergency calls can disable airplane mode while locked, but supporting it without access to data would require storing it in the encryption header or something like that.

fid02

GrapheneOS There's a planned toggle for controlling if emergency calls can disable airplane mode while locked

I assume that the default will still be that emergency calls can disable airplane mode when the device is locked?

roamer4223

GrapheneOS I commented on a post on github that I believed was about this issue (airplane mode being disabled). I hope I did not break Github etiquette.

I believe this would be a really amazing security feature to have. (Enabling the user the disable the ability for emergency calls to disable airplane mode when phone is in BFU state)

I suppose, is there a way of doing this by, when the toggle is on and airplane mode can't be disabled. Is one way of doing this, temporarily removing all emergency numbers from the database in the phone?

If I posted on the wrong issue on GitHub, I'm sorry as well. Please know that the GrapheneOS project means a huge amount to me and I don't wish to cause annoyances, and I wish to do all I can to contribute to the community

grayway2

roamer4223 There's a planned toggle for controlling if emergency calls can disable airplane mode while locked, but supporting it without access to data would require storing it in the encryption header or something like that (grapheneOS account)

roamer4223

grayway2 but supporting it without access to data would require storing it in the encryption header or something like that (grapheneOS account)

Would this still be true for my suggestion above about removing all emergency numbers from database on phone (temporarily) while the toggle is on?

Just something that occurred to me, my knowledge is limited though.

Just a quick thanks, by the way, to the devs that work on GrapheneOS. I admire, and I thank you all, for helping make this life changing software available to so many. I will donate again as soon as I can and emplore others too as well.

grayway2

roamer4223 only the devs can answer about this. Now, all we can do is to wait and see how things evolves.

Don't expect this to be there soon. We are lucky if we get it during Christmas.

roamer4223

grayway2 thanks for the reply anyway mate! Fingers crossed then :)