| rainemak | dcaliste, unfortunately cannot participate today's meeting | 06:56 |
|---|---|---|
| rainemak | dcaliste, but drop questions if you have them in mind | 06:56 |
| dcaliste | rainemak: no problem, I guess you are very busy at the moment. | 06:56 |
| rainemak | dcaliste, yes | 06:56 |
| dcaliste | I have one for Chris but he's not here at the moment neither. | 06:57 |
| dcaliste | I would like to discuss with pvuorela also about the PR in messagingframework, I'll ask him. | 06:57 |
| dcaliste | pvuorela: do you have a moment to discuss the signature PR in messaging framework ? | 07:07 |
| jpetrell | dcaliste: just checked the pull requests. I'll try to find time at some point to properly test the signature use cases (I don't want to approve just reading the code), but I don't think the pull requests are far from mergeable condition. email settings section should be put behind a loader | 07:09 |
| dcaliste | jpetrell: I'm sorry you lost your time last week on version issues in the various pieces to have signature handling. As you've seen, I've moved the QMF PR upstream so it is based on HEAD. | 07:09 |
| dcaliste | jpetrell: ok for the loader, I'll do it later today or tomorrow. | 07:10 |
| jpetrell | dcaliste: awesome! no worries, not your fault :) | 07:10 |
| jpetrell | like discussed the email signing could be initially be installable package in OS. once we get secrets in core releases and signature more testing we can enable it for all | 07:11 |
| dcaliste | jpetrell: yes sure need to be tested on device before accepting anything ! I agree with the installation plan also. | 07:11 |
| dcaliste | jpetrell: just one question, | 07:11 |
| jpetrell | sure, shoot | 07:11 |
| dcaliste | the various PR in settings and email are using import Sailfish.Secrets, so I must put the Requires: xxx in the spec file. | 07:12 |
| dcaliste | This Requires is on Secret itself, not the GPG plugin for it. | 07:12 |
| dcaliste | Is it an issue ? Because it will pull Secret for everyone. | 07:12 |
| pvuorela | dcaliste: pong, have some time but i've only superficially checked the pr so far. | 07:17 |
| dcaliste | pvuorela: ok, yeh, I guess you are busy also ;) It is mostly a rebase of the PR from mer-core. | 07:18 |
| pvuorela | dcaliste: yea, had quite much changes there :) | 07:19 |
| dcaliste | pvuorela: in case you didn't follow the history of it, it mostly add a new attribute for a mailPart : the undecodedData stuff. This is the content of a part (header and body) as received from the server, before any parsing. | 07:21 |
| dcaliste | This is required, because we cannot reconstruct the pristine data from the parsed and stored ones. | 07:21 |
| dcaliste | Of course pristine data are required to check signature. | 07:21 |
| pvuorela | alright. | 07:22 |
| dcaliste | Then, there is additional code in storage to actually save and restore to disk the undecoded data. | 07:22 |
| dcaliste | It is stored in a abc-parts/x-raw file where x stands for the part number. | 07:22 |
| dcaliste | The most additional code is in IMAP handling to be able to ask precisely this undecoded data when required. | 07:24 |
| dcaliste | Then, I've added tests to check that this undecoded data can be read from a received stream, or save and restore from disk. | 07:24 |
| dcaliste | Finally, I've added a plugin interface to handle cryptographic data in email, and implemented it for OpenGPG and S/MIME protocols. | 07:25 |
| dcaliste | This interface is responsible to find a signed part in QMailMessage, it also provides a verify() and a sign() methods. | 07:26 |
| dcaliste | pvuorela: if you have any additional question, please don't hesitate. | 07:27 |
| dcaliste | jpetrell: one additional reminder, when compiling Secrets, don't forget to add https://github.com/sailfishos/sailfish-secrets/pull/143 otherwise the UI will complain that you don't have the required plugin for signature. | 07:28 |
| dcaliste | I've asked chriadam_ about inclusion plan, but he seems to be off at the moment. | 07:29 |
| pvuorela | dcaliste: sure. maybe someone else should look into that too, but i'll see what i can do. haven't digged into signing details that much yet. | 07:31 |
| dcaliste | pvuorela: mvoggt looked at it when initially submitted into mer-core, see https://git.merproject.org/mer-core/messagingframework/merge_requests/6 | 07:33 |
| dcaliste | pvuorela: but I agree that several people should look at the current one upstream, indeed. | 07:33 |
| *** frinring_ is now known as frinring | 09:06 | |
| *** bugzy_ is now known as bugzy | 17:46 | |
| teachmetype_ | Is it a multi-lingual space or is it better if I keep using DeepL? | 20:28 |
| teachmetype_ | I'm Italian. | 20:28 |
| teachmetype_ | Well, in the meantime, I'm starting to ask my question since no one answers: | 20:33 |
| teachmetype_ | I've never planned, apart from a light smattering on Python about ten years ago (of which I don't remember anything). | 20:33 |
| teachmetype_ | I'm still a computer enthusiast, and I'd like to start my own study and succeed in... development. | 20:34 |
| teachmetype_ | Who like me starts from scratch and is interested in a system like Sailfish, where to start? What language? | 20:34 |
| kimmoli | https://sailfishos.org/develop/sdk-overview/develop-firstapp-article/ | 20:36 |
| teachmetype_ | I'm reading the page you quoted. | 20:38 |
| teachmetype_ | Thanks anyway. | 20:38 |
| r0kk3rz | teachmetype_: you can do apps in python if you have some familiarity with it | 20:40 |
| r0kk3rz | python is probably easier than learning c++ from the start | 20:40 |
| Marzanna | Does anyone experience sudden crash of all apps on SailfishX? | 20:40 |
| teachmetype__ | I talked about Python just to say something I did, but I don't know anything about it at the moment | 20:43 |
| teachmetype__ | If you can start me off anyway, and help me out later... then okay: Python. | 20:43 |
| teachmetype__ | *If that | 20:44 |
| teachmetype__ | ..or this? xD | 20:44 |
| teachmetype__ | I don't remember your nick, but thanks. | 20:44 |
| r0kk3rz | as a first programming language, python is quite ok | 20:45 |
| teachmetype__ | Okay, so I'm gonna start reading up on it. | 20:46 |
| *** ahjolinna_ is now known as ahjolinna | 23:54 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!