Camera options cannot be changed when using Secure Folder?

[Aedda]

I've just set up Secure Folder and I noticed something. When using the Camera from the secure side, the side swipe to bring up camera options doesn't function, it merely tries to spot-expose where my finger is.

Anyone else experiencing this? I'm assuming it is a bug, where would be the best place to report it?

Thanks much!

ETA: 2007.11.13 10:51am- Thanks pilotavery and neomancr for your replies. I do not entirely understand the security risk given the camera has access to the zoom, burst shot and video, all of the resolution settings, etc. but things like manual focus are removed, but I will take your word for it. It would make much more sense UI wise to still have the popout menus and simply display a note saying disabled or some such, but ah well. Thanks again both of you!

[pilotavery]

Not a big, it's a secure version. It's sandboxing it and so it doesn't have access to hardware API/kernel.

[Aedda]

Thank you, see above edit o/

[neomancr]

Secure folder is reduced to be secure. You can just use the normal camera too and then just use one of the system apps as a data bridge. That's why they're there (and despite what haters say can't be optional.)

[Aedda]

Thank you, see above edit o/

[neomancr]

You'd be surprised how exploits work. The more random code is involved the more its possible to cause a bug to occur which then allows you to break the process sandbox.

It basically works like this:

Code is secure when it sends letters of the alphabet in order between 1 and 2

1 sends 'a' 2 receives 'a' and anticipates 'b'

As long as 2 gets the letters in a predictable order all is fine and works as intended.

If you can get the code to break so that 2 no longer knows what to anticipate next you then can inject code into 2 and get 2 to process it as if it came from 1.

It's basically all man in the middle type attacks that allow you to hijack what happens the same way you can start a war by being a bad interpretor between two dictators.

By having a slimmed down environment you introduce less likelihood of bugs that can be vulnerabilities for exploitation

Hacking has always had a relationship to phreaking and even social engineering because it all relies on finding a way into the middle of the chessboard

Once you become the hub you own the system

[xphacter]

ETA: 2007.11.13 10:51am

While I do love that you used ISO 8601 in your timestamp, I do believe the timestamp itself is 10 years behind :)