| mal | Thaodan: are you using --fetch-submodules? try without it | 00:35 |
|---|---|---|
| Thaodan | mal: it was something with the manifest , used rinigus unchanged manifest and everything was fine | 01:10 |
| Thaodan | went not further, had to extend my build scripts | 01:11 |
| Thaodan | Recursion is complicated :D | 01:22 |
| Thaodan | https://gitlab.com/Thaodan/hadk_tools/-/commit/02a95f9395db68c105606cff29f0b45273abc2c7 | 01:22 |
| rinigus | Thaodan: morning! Not clear when that error was hit. Is it with some auto-generated manifests (assuming it from your statement regarding unchanged manifest)? | 05:47 |
| archer_3123_ | I was wondering if anyone was on here that's working on the pinephone port | 06:00 |
| rinigus | piggz: and that's why there is no point in adding 'encryption' to the ports: https://forum.sailfishos.org/t/how-to-unlock-the-encryption-of-your-home-if-you-dont-know-your-lock-code-bruteforce/3004 | 06:44 |
| r0kk3rz | thats a pretty easy hack | 09:25 |
| T42 | <adampigg> yeah, interesting | 09:25 |
| rinigus | I guess if we want to have proper encryption, we should somehow allow users to generate and input long(er?) key. | 09:29 |
| r0kk3rz | or, they should not be dumb and salt + rehash it | 09:30 |
| rinigus | if you know the algorithm of salt+rehash, it should be trivial to brute force that as well. | 09:34 |
| rinigus | (if I understand that correctly) | 09:34 |
| r0kk3rz | ish, but slower | 09:34 |
| r0kk3rz | which is the point | 09:34 |
| r0kk3rz | you can brute force anything, its a question of how long it takes | 09:35 |
| r0kk3rz | if you hash the pin 100x, then any brute forcing is 100x slower for eg | 09:35 |
| rinigus | yes, I agree that you can brute force anything. we just have to make it impractical. just salt with rehash will not probably impact it that much | 09:36 |
| rinigus | now, don't we have some "secure" storage on devices? something that can generate random key and used as a salt with pin? assuming that this random key cannot be lifted from device ... | 09:37 |
| rinigus | don't know whether such secure storage exists, please correct | 09:38 |
| r0kk3rz | some probably do yeah | 09:38 |
| Thaodan | rinigus: i tried updating to Android 9 r61 | 11:33 |
| rinigus | Thaodan: I see. such update is going to be very messy - probably would require reflash of the device. | 11:34 |
| rinigus | ... or is it done as a part of updates for sony devices via rpm? | 11:34 |
| rinigus | don't think so | 11:35 |
| Thaodan | no | 11:36 |
| Thaodan | it's just a minor update in the same version | 11:36 |
| rinigus | but in this sense, we better keep aosp9 as it is, with the same version as we have on devices. | 11:39 |
| rinigus | in a sense as it is on official devices - we shouldn't touch base unless there is a major reason to do so. | 11:39 |
| rinigus | Thaodan: now some good reasons for reflash: switch to aosp10, switch to aarch64 :) | 11:40 |
| Thaodan | even that can work without reflaah | 11:40 |
| Thaodan | reflash | 11:40 |
| Thaodan | at least without manual reflash | 11:41 |
| rinigus | probably we can update system & vendor without reflash. but that is some effort and uncharted so far. (I hope I understood you right) | 11:42 |
| rinigus | Thaodan: ^ | 11:42 |
| Thaodan | you did | 11:43 |
| Thaodan | the problem with updating major versions is updating odm but that's easier as community port as you don't necessary have the proper process to distribute the odm partition | 11:45 |
| rinigus | Thaodan: note that in case of tama, any system & vendor update means recompilation for 6 devices. at least 3 + 3 via patching, whatever is easier. | 11:45 |
| rinigus | Thaodan: odm is this sony-distributed bit? | 11:46 |
| rinigus | going to oem_{a,b}? | 11:47 |
| Thaodan | it is but it's the major problem as it contains the blobs you need to update but can't distribute | 11:47 |
| Thaodan | in our case we could just request the user to download them and put them somewhere on the device | 11:48 |
| rinigus | Thaodan: as far as I have seen, on android aosp, you make an update, shutdown, and then fastboot flash oem. so, it is responsibility of the user to perform it | 11:49 |
| rinigus | in case of aosp9, we already have the latest version of that blob installed. for aosp10, new will be needed | 11:50 |
| Thaodan | If anyone wants to build sony tama devices he can now do so automatically with my hadk-build tools: https://gitlab.com/Thaodan/hadk_tools/-/commit/ead5d2c3061da7a0561984514fe4c90696e13d9c | 12:41 |
| rinigus | Thaodan: very nice. so how does it work? which parts does it compile? | 13:29 |
| Thaodan | all of them | 14:38 |
| Thaodan | except some I have forgot for mw | 14:39 |
| *** amccarthy_ is now known as amccarthy | 21:29 | |
| T42 | Harold Ballard %lastname% was added by: Harold Ballard %lastname% | 23:34 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!