asked 2014-03-26 08:01:07 +0300
The settings menu has a new section 'Untrusted software'.
The section currently (in 1.0.4.20) contains only a on/off switch for 'Allow untrusted software': Unable installation of software coming from 3rd party stores or downloaded from the Internet'.
What is the intended purpose of that option? How does e.g. affect installations from Openrepos?
answered 2014-03-26 22:02:34 +0300
The 1.0.4.20 has brought a new feature: possibility to install rpm files directly by clicking on them in the Transfers view (I know, it was already possible with the Store opened, but now it's nicely integrated).
And as installing applications by an other way than the official Store can lead to severe issues (we've seen that), Jolla want to protect themselves.
So it will not affect installations from OpenRepos because you have already it installed, but starting from now, in order to install Warehouse for example, you will need to accept that you are taking some risks and that Jolla will not be responsible in case of damages:
answered 2014-03-26 10:30:53 +0300
Liability?! Also some of the repos over a openrepos did prevent/disturb/crash SSU, that is why there is guide how to deactivate them with the last update. That can happen with any other unvalidated 3rd party installed software. Most OSs have that setting, this way they make sure the user has to actively accept to install 3rd party blobbs and therefor cannot blame Jolla for anything while he bricks his phone with said 3rd party software.
Don't insult, it's not clever. I'm not trolling. Please take a look
Basil ( 2014-03-28 10:27:11 +0300 )edit@Basil sure access to bits and pieces that should not be erased by anyone needs to be protected, but seriously? We are asking for OpenSource, access to all H/W and then we tell "bad product design" if we brick it with some 3rd party blobb Jolla is not aware of?! People would argue that they had to reset their device because Jolla did not protect them, we are not talking about erasing bootloaders or recovery partitions. As we have no way to fix it ourselves brick means send to care...
chemist ( 2014-03-28 15:34:33 +0300 )editYes, seriously. Not "be protected from erasing by anyone", but have separate privileges and methods to do so. Brick after software install and "we have no way to fix it ourselves" is a problem. and this is bad design. Failed system(!) update without fallback solution (maybe not even package replated, but a deleted/replaced file) is a problem, and this is bad design.
Basil ( 2014-03-28 17:10:59 +0300 )editAsked: 2014-03-26 08:01:07 +0300
Seen: 1,260 times
Last updated: Mar 26 '14
