#tde-devs < 2025/08/25 > |
|---|
| [02:36] | micheleC has joined |
| [07:39] | Fat-Zer has quit (Ping timeout: 252 seconds) |
| [07:52] | Fat-Zer has joined |
| [07:54] | micheleC: @Fat-Zer: so if tsak does most of the work and tdmtsak only interacts with it for the TDM part, it seems it does not make much sense to allow to build one without the other or viceversa. Or am I missing some use case? |
| [09:27] | Fat-Zer: micheleC: well... it's pretty much it... except that kdesktop also interacts with tsak via tdmtsak |
| [09:28] | Fat-Zer: but as far as I can see as for now there is no way for kdesktop to start tsak on it's own so it only works if tsak is started by tdm |
| [10:10] | micheleC: I have not checked the code behind it but this is what I observe on my system. I have everything built with TSAK but keep everything disabled. Nor tsak neither tdmtsak are running at the moment. If I go into TCC and enable tsak both at login and in the screensaver modules, then SAK works fine. |
| [10:11] | micheleC: probably it is as you say, since if I don't enable SAK in the login manager module, kdesktop can't use SAK at all |
| [10:12] | micheleC: so once again I wonder if it makes sense to have independent built options |
| [10:12] | micheleC: perhaps we can wait till Slavek comes back from his holiday and then discuss together |
| [11:00] | Fat-Zer: hmm... the more I think about it the more I tend to agree with you... |
| [11:02] | Fat-Zer: the proper fix for it would be to make it work independent of tdm in kdesktop, but current sak implementation seems to be quite hacky and in general it seems to me a feature of quite dubious security value, so I don't feel a lot of incentive to actually do it.. |
| [11:04] | Fat-Zer: so installing tsak/tdmsak alongside with tdm sounds more appealing now... |
| [11:07] | Fat-Zer: by the work if we are moving stuff around, I'd suggest to also build `tdekbdledsync` alongside tdm... and `krootbacking` alongside the ksmserver |
| [13:07] | micheleC: I tend to agree with you on SAK being of dubious security value |
| [13:08] | micheleC: I don't think we can have SAK working on kdesktop and not in tdm, because it would undervalue the whole concept of SAK if the user could simply switch to another tdm console and not having SAK there... |
| [13:10] | micheleC: regarding `tdekbdledsync` and `krootbacking` I don't have any objection, but also haven't looked into any code. again something we can discuss with Slavek during the week |
| [13:12] | micheleC: btw TDE/krusade#44 also waiting for review. minor change, but I am starting to prepare the code for future cmake conversion |
| [13:49] | SlavekB has joined |
| [13:54] | Fat-Zer: as for TDE/krusade#44, to be frankly, I'm not sure about the slack-desc... I suspect it might be used by slackware somehow |
| [13:56] | micheleC: all packaging stuff should go into tde-packaging. We have already removed distro-speciic files in the past. But you can leave it to Slavek to approve if you want |
| [14:00] | Fat-Zer has quit (Ping timeout: 256 seconds) |
| [14:11] | micheleC has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org) |
| [14:14] | Fat-Zer has joined |
| [15:17] | SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org) |
| [15:42] | SlavekB has joined |
| [21:03] | SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org) |
| [21:32] | SlavekB has joined |
| [22:28] | SlavekB has quit (Ping timeout: 258 seconds) |
| [22:41] | SlavekB has joined |
#tde-devs < 2025/08/25 > |
|---|
