Re: [Tails-dev] [gsoc] tails-greeter progress report
Hi again, Also I just notices intrigeri asked you a late question about your last week report on the tails-dev mailing list without any answer. Please see his last mail to you and tails-dev from August 04 about using a shell script. Did you answer to this question privately? bert. On Fri, Aug 05, 2011 at 05:25:22PM +0200, berta...@ptitcanardnoir.org wrote: Hi, I'm trying to catch up on this GSOC work, so I might be lacking some informations to correctly understand everything. Don't hesitate to correct me if I make any mistake. I've tested your previous 0.0.5 release as well as this week's one in a fresh VM, and read your previous exchanges with intrigeri. On Fri, Aug 05, 2011 at 02:15:52AM +0800, † wrote: Hello. Current progress: obtain list of kb layouts and variants available (via python-xklavier) - DONE. populate layout widget with kb variants - DONE. merge feature/better_root_access_control branch - DONE. Confirm the above three DONE items. Well done! apply correct layout after it's been chosen (both to present and following greeter widgets and to actual session) - postponed. verify that layout switching works after login - postponed version tag and update - DONE. As I understood, you were also supposed to upload a Debian package to your tails repo, which I can't find. Problems: tails-greeter is run under gdm's account but altering gdm PostLogon files (to set env variables) or locale compilation via localedef require root privileges. Seems like intrigeri already proposed a workaround to this last week, please read again his answer to your report last week. xklavier set and check layout without errors but it doesn't affect greeter nor following session. better_root_access_control feature requires env. variable to be set which is not possible yet. Near-future plans: wait for answer from gdm and xklavier devs to figure out workarounds for current problems Do you have pointers to this conversation? I might be interested to follow it, and eventually help you with it. replace 2 widgets with 1 panel with same functionality test the result with tails Sounds to me that the next step to this dev would be to implement a way to pass env variables too. Additional notes: right now there are 2 screens which user moves through by pressing next button. That's rather ugly and is planned to be replaced with one of the following: 1) single screen with requests for both at the same time 2) 2 screens with language and layout requests on first one and admin password request on second one Which do you think is better and why? Please feel free to discuss it on irc this Saturday during regular meeting time or whenever you'll see max-gsoc I think intrigeri already made that clear when you started with 2 screens that at the end we wanted to have only one screen with all options on it. We don't want to bother too much our users with multiple screens. Another question: reading your commits, you removed the babel module importation. Do you plan to put it back, or are you just getting rid of it? In the latter case, you should also consider removing it from the install dependencies of the Debian package in debian/control. See you tomorrow morning. bert. ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev
Re: [Tails-dev] [gsoc] tails-greeter progress report
On Sat, Aug 06, 2011 at 12:24:36AM +0800, † wrote: 05.08.2011 23:53, berta...@ptitcanardnoir.org пишет: Also I just notices intrigeri asked you a late question about your last week report on the tails-dev mailing list without any answer. Please see his last mail to you and tails-dev from August 04 about using a shell script. Did you answer to this question privately? He departed to vacation before that. In short - yes, rewriting sh to python is doable but the code which supposed to be rewritten is (or, to be more precise - will be) obsolete after some workaround to pass env. vars will be implemented anyway. Fair enough. We'll see if such a workaround exists though. bert. ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev
Re: [Tails-dev] [gsoc] tails-greeter progress report
On Sat, Aug 06, 2011 at 12:38:24AM +0800, † wrote: 05.08.2011 23:25, berta...@ptitcanardnoir.org пишет: As I understood, you were also supposed to upload a Debian package to your tails repo, which I can't find. Sorry, forgot to push it. Should be available now. Seems not really, can't find any new commit with the new Debian package. Seems like intrigeri already proposed a workaround to this last week, please read again his answer to your report last week. Just to get potential readers up-to-date: the idea is following tails-greeter writes some instructions (env. variables, locale generation parameters smth else) to the place writable for it's user (Debian-gdm) for example. Upon logon some startup script parse this file and execute them (as amnesia user or as root). That'll be next thing I'll try to implement and that's actually what I'd like to discuss: So that maybe should be added to your schedule for next week, it was my suggestion in my last email. - how good\safe is this approach? Using such tricks to have something executed by root might sure bring the question, and that's nice it pops up in your head. But well, we're talking about mostly predefined choices, and run once during the system boot time. I'm not sure to see what an attacker could do to take advantage of this and s/he is able to do this, s/he can do a lot more. - are there better alternatives? I'm out of idea for the moment, but will sleep on this. Note that at least some of the instructions from this file got to be executed with root privileges. Just to clarify: by executed I don't mean sh file.sh - it might be $ARG1 supplied to sudo ls $ARG1. Do you have pointers to this conversation? I might be interested to follow it, and eventually help you with it. http://mail.gnome.org/archives/gdm-list/2011-August/msg2.html Thanks. Looks like for the moment they don't really have answers to your issue, we'll see in the next days, but I suspect you won't have much choices. replace 2 widgets with 1 panel with same functionality test the result with tails Sounds to me that the next step to this dev would be to implement a way to pass env variables too. Not really sure what you mean. If you're talking about task priorities than - yes, that's true. The tasks are orthogonal though. I meant: add to the next week plan the work on implementing a way to pass env variables to the session. I'm not sure to get why this two tasks are orthogonal, I rather feel that the env thing is not that much related to how the widget/panel are organized and can be developed independently from the other one. But maybe I'm wrong and missing the big picture, and would be glad to have your input in this case. It seems that there is not much time left before the end of your GSOC, and this is a critical piece of the project I'd like to see getting forward. I'm not asking for this task to be completely done at the end of next week, but given the time spent on the GSOC your commits seems to reveal, I'd prefer to see some work going on in this area, and the plan you posted initially might have some room left to add it. But sure the panel reorganisation is also important. :) Another question: reading your commits, you removed the babel module importation. Do you plan to put it back, or are you just getting rid of it? In the latter case, you should also consider removing it from the install dependencies of the Debian package in debian/control. That was just part of pylint warnings cleanup. I didn't notice that it's completely gone now :) Great! bert. ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev