**** BEGIN LOGGING AT Thu Jan 26 02:59:57 2012 Jan 26 03:02:51 lol what are you doing? :) Jan 26 03:03:11 adding the appdir to the PATH of the spawned terminal? Jan 26 03:03:28 (is that not done already?) Jan 26 03:03:49 ya that is what im trying to do Jan 26 03:03:56 and its not already dont Jan 26 03:04:00 there is a profile.d file Jan 26 03:04:10 which only gets called after login Jan 26 03:04:25 but for exhibition mode which doesnt use login Jan 26 03:04:38 i want to add the bin dir from within the app path Jan 26 03:07:49 well i think you can just setenv+execvp, or do the more direct execvpe Jan 26 03:08:05 that is what i was doing Jan 26 03:08:14 and all i would get is a black screen, not prompt Jan 26 03:30:21 will someone checkout my last commit and tell me why it doesnt work Jan 26 03:36:09 (i assume wterm is actually invoked with the full path such that argv[0] contains the required path information?// i assume the debugging syslogs show the values you expect?) **** ENDING LOGGING AT Thu Jan 26 03:37:48 2012 **** BEGIN LOGGING AT Thu Jan 26 03:55:12 2012 Jan 26 03:47:14 well, even if that code did work (I haven't figured out why it doesn't just yet) it wouldn't work Jan 26 03:47:26 because we purposefully have login trash environment variables Jan 26 03:47:42 or at least, I don't think it would Jan 26 03:49:07 you'd have to clear LD_PRELOAD and stuff and then pass -p to login I think Jan 26 03:53:28 Brybry: oh i thought he was just trying to use that code for invoking the dock app Jan 26 03:53:31 (which presuambly isn't login?) Jan 26 03:57:39 true, I guess it work would in that case Jan 26 04:07:16 ah, I guess the path is trashed so the login doesn't work right Jan 26 04:12:06 alright, well PSA: we'll see how long this lasts, but I'm gonna be offline for the next *time period* (days?) because i really really need to focus on my studying and internets are way too distracting. and fantastically interesting projects like wterm ...i'm too weak ;) :D Jan 26 04:12:14 can't imagine anyone will, but i'll of course be reachable via email Jan 26 04:12:26 good luck and take care :) Jan 26 04:13:58 I hope it helps :) Jan 26 04:14:24 yeah, ...me too. Jan 26 04:14:38 a desparate act to salvage my focus, if it wasn't transparent enough :) Jan 26 04:15:30 i think you guys miss the points Jan 26 04:15:33 point Jan 26 04:15:34 oooooh, nevermind. Ignore my previous comment about the path getting trash Jan 26 04:15:45 I was running from command line :( Jan 26 04:15:46 this is pre login :D Jan 26 04:16:14 I assume you wanted us to look at Terminal::start() Jan 26 04:16:47 so exhibition mode works Jan 26 04:17:15 Brybry, ya start() Jan 26 04:17:51 ya exhibition mode works if i just pass cmatrix without the full path Jan 26 04:18:01 which was the point of the change Jan 26 04:18:12 but i dont get why login would fail Jan 26 04:38:43 heh Jan 26 04:38:51 guess setenv is the problem Jan 26 04:38:59 i switched to putenv and it works Jan 26 04:40:10 hmmm Jan 26 04:40:11 no Jan 26 04:40:20 putenv does not work Jan 26 04:44:53 I'm so confused right now Jan 26 04:44:55 I commented it all out Jan 26 04:45:00 and it still doesn't work for me Jan 26 04:45:05 lol Jan 26 04:50:27 yay i got it for real Jan 26 04:53:04 Brybry, see last commit Jan 26 04:54:03 works Jan 26 04:55:54 quitting cmatrix with q in exhibition doesn't seem to respawn anymore (it did ~2 commits ago) Jan 26 04:55:57 not that anyone will run into that Jan 26 04:56:26 you and your bt keyboard Jan 26 04:56:49 whoa, does exhibition never actually close? Jan 26 04:56:58 basically Jan 26 04:57:18 thats why i added the code to suspend the app that runs when its inactive Jan 26 04:57:24 cant be having it waste cpu Jan 26 04:57:26 also... Jan 26 04:57:35 when u change the exhibition mode app in the prefs... Jan 26 04:57:50 i close the exhibition mode window if it exists Jan 26 05:00:30 Brybry, do you remember how far back you could kill cmatrix in dock mode? Jan 26 05:00:33 was it really just 2 Jan 26 05:00:46 or was it farther back, like before i did the headless rewrite Jan 26 05:02:40 I dunno but I can probably figure out real quick Jan 26 05:03:27 if it was before the headless conversion that would sorta make sense Jan 26 05:04:43 works on 1cf5a32 headless works (possible race condition?) Jan 26 05:09:02 so what about the stripped out env breaks that Jan 26 05:09:18 it works in standalone Jan 26 05:09:27 if u do something like "./wterm 14 cmatrix" Jan 26 05:09:55 well, does cmatrix need the environment stuff to run now? Jan 26 05:10:01 hmm Jan 26 05:10:33 i needs TERM Jan 26 05:10:56 but it doesnt run at all if i dont clearenv Jan 26 05:11:17 ah, see the respawn code doesn't use start() Jan 26 05:11:32 it uses the function below that (newLogin() which I guess was poorly named) Jan 26 05:12:44 thats ok Jan 26 05:12:53 respawning works in standalone Jan 26 05:13:31 wtf Jan 26 05:13:38 i commented out clearenv Jan 26 05:13:55 so it only sets path Jan 26 05:14:01 and now its working Jan 26 05:14:18 note that exhibition mode like never closes Jan 26 05:14:18 ever Jan 26 05:14:38 but why wouldnt it respond to keyboard Jan 26 05:15:10 it always responded for me it just hung at the starting new terminal bit Jan 26 05:15:30 it just doesnt respond for me Jan 26 05:16:29 tap the screen Jan 26 05:16:31 to set focus Jan 26 05:17:00 doh Jan 26 05:17:04 "D Jan 26 05:17:08 I dunno if I had to do that before but I did when I just retested it Jan 26 05:17:17 ok so that worked Jan 26 05:17:56 huh Jan 26 05:18:04 so it constantly tries to restart as I tap input Jan 26 05:18:06 interesting Jan 26 05:18:41 'cannot execute child shell' :D Jan 26 05:18:42 we probably should be trying to respawn in exhibition mode Jan 26 05:19:05 I wonder what the path is there Jan 26 05:19:34 ok i fixed it Jan 26 05:23:49 pushed Jan 26 05:33:44 it definitely doesn't sleep when exhibition isn't active Jan 26 05:34:40 hmm what broke that Jan 26 05:34:48 like, I think it yields Jan 26 05:34:56 but I'm not sure it's sleeping Jan 26 05:37:19 i think i have an idea Jan 26 05:37:32 if I put my touchpad to sleep with the power button it gets better but cmatrix still runs full blast (and I guess the terminal thread/select is still happening but not the graphics event thread) Jan 26 05:37:47 ya i can see that Jan 26 05:37:48 how would you even tell cmatrix to sleep? Jan 26 05:38:03 we have the pid I guess Jan 26 05:38:07 well before i converted to headless Jan 26 05:38:14 and before it was a true dock app Jan 26 05:38:28 it got windowActivate/Deactivated events (like a normal app) Jan 26 05:38:35 and I would insert into the term ^S Jan 26 05:38:38 and ^Q Jan 26 05:38:48 ah, ok Jan 26 05:39:12 but i think its not getting those events now Jan 26 05:50:23 there's an enyo example in the pdk share Jan 26 05:50:30 err sdk sharE* Jan 26 05:50:49 example of what? Jan 26 05:50:55 exhibition app Jan 26 05:51:06 i have an exhibition app Jan 26 06:07:20 Brybry, pushed a fix for you to test Jan 26 06:11:18 :) Jan 26 06:11:26 works great Jan 26 06:53:35 Brybry, 0.3.5 is out the door Jan 26 08:22:34 PuffTheMagic, did you remove the external keyboard option in wTerm? Jan 26 08:43:38 ka6sox, what do you mean? bt keyboard stuff should still work fine/the same Jan 26 08:44:41 its not where rememberd it Jan 26 08:44:44 but it works fine Jan 26 08:45:13 ctrl+shift+[ escapes from insert on vi Jan 26 08:46:31 good morning :) Jan 26 11:18:02 i guess i can only use 7 bits per color value (for integer precision) Jan 26 15:24:03 ka6sox, remove no, what makes you think so? Jan 26 15:35:44 stbuehler, morn Jan 26 15:43:56 stbuehler, got a question about your parser Jan 26 17:20:41 almost have scroll buffer working Jan 26 17:37:46 PuffTheMagic, because I forgot where it was hidden Jan 26 17:38:00 hidden? Jan 26 17:38:45 PuffTheMagic, your makefile in build.git is wrong Jan 26 17:39:00 which makefile? Jan 26 17:39:04 the last screenshot line has a comma at the end, that's not valid JSON Jan 26 17:39:09 http://git.webos-internals.org/preware/build/tree/apps/wterm/Makefile Jan 26 17:39:11 ohh Jan 26 17:39:16 line 42 Jan 26 17:39:23 thanks Jan 26 17:39:34 I can fix it Jan 26 17:39:41 I only found it because you broke my ipkg api Jan 26 17:39:42 lol Jan 26 17:39:45 i need to fix something else too Jan 26 17:40:05 it can't properly parse the Source line in the Packages.gz file for wterm, which makes it die Jan 26 17:40:07 forget to prevent it from packaging the screenshots dir Jan 26 17:40:13 * cryptk blames you Jan 26 17:42:19 ok fixed Jan 26 17:42:26 also removed all the source it was packaging Jan 26 17:42:33 ipk went from 2.9mb to 900k Jan 26 17:43:26 nice, lol Jan 26 17:43:38 after the next autobuilder pass my api should be working again Jan 26 17:44:48 so i know the trailing comma is not technically valid Jan 26 17:44:54 but what lib are you using that breaks on that Jan 26 17:45:06 the only json lib i've ever used that enforces that was cl-json **** ENDING LOGGING AT Thu Jan 26 17:46:57 2012 **** BEGIN LOGGING AT Thu Jan 26 17:48:19 2012 Jan 26 17:51:55 i'll be back later, if you still have a question just ping me with it Jan 26 17:52:28 PuffTheMagic, your sources line validates in jsonlint now, once the autobuilder finishes, I will let you know the verdict Jan 26 17:54:21 what verdict? Jan 26 18:15:04 heh Jan 26 18:15:05 us.ryanhope.wterm_0.3.5-1_arm.ipk 26-Jan-2012 07:03 2482194 Jan 26 18:15:05 us.ryanhope.wterm_0.3.5-2_arm.ipk 26-Jan-2012 17:48 458632 Jan 26 18:26:13 woot Jan 26 18:26:17 scroll buffer works Jan 26 18:44:55 anyone around to test? Jan 26 19:38:04 PuffTheMagic, you pushed that scrollback buffer mod? Jan 26 19:38:13 okay I'll test Jan 26 19:38:23 is that in the feeds or just in box? Jan 26 19:39:44 havent released it Jan 26 19:39:47 yet Jan 26 19:39:51 so you would have to build it Jan 26 19:39:56 or i could send a ipk to you Jan 26 19:40:13 please send it... Jan 26 19:40:14 I will test Jan 26 19:40:28 * ka6sox brings up TP Jan 26 19:44:58 https://www.box.com/s/0r0z6ln1zyu9y37bfbmc Jan 26 19:48:13 PuffTheMagic, check this out... Jan 26 19:48:14 http://ipkgapi.cryptkcoding.com/v1.0/db-contents.php Jan 26 19:48:27 every bit of data about every package in any of our feeds Jan 26 19:48:30 all in one place, lol Jan 26 19:49:02 with my tweaks to the Packages.gz parser to account for the autobuilder not knowing what valid JSON is, it works again! Jan 26 19:49:41 you should parse the screenshots Jan 26 19:49:48 as a heads up, there is a TON of data there, the long loading time isn't lag coming from my server, it is all the data lagging your browser Jan 26 19:49:49 and turn it into a
    Jan 26 19:49:52 with actual links Jan 26 19:50:00 PuffTheMagic, that is just a dump of the data in the table Jan 26 19:50:40 that page doesn't even use the API Jan 26 19:50:51 it literally just does a "SELECT * from iapi_packages" Jan 26 19:51:15 but all of that data is query-able with my API though Jan 26 19:52:28 ka6sox, so I know of 2 issues you might bring up, when scrolled back, pressing a non modifier key should snap to bottom, and when scrolled, the cursor should not render Jan 26 19:52:30 im fixing those now Jan 26 19:54:10 is shift up/down supposed to scroll? Jan 26 19:54:33 ah Jan 26 19:54:35 fn+shift+up Jan 26 19:54:36 shift+pg up Jan 26 19:54:43 so ya you need fn Jan 26 19:55:11 might just change that to ctrl+up/dn Jan 26 19:55:26 or we could just make it use touch input =p Jan 26 19:55:28 i pushed those 2 fixes i just mentioned btw Jan 26 19:55:45 Brybry, idk how that will interact with my plans for mouse support Jan 26 19:56:05 mmm Jan 26 19:56:10 do it only on the far right side maybe Jan 26 19:56:45 and only for some sort of swipe gesture detection perhaps Jan 26 19:57:00 it might not be easy Jan 26 19:57:00 * PuffTheMagic isnt touching gestures with a 10 foot poll Jan 26 19:59:19 well scroll buffer just opened up a whole new door of usability Jan 26 20:00:02 I see it. Jan 26 20:00:06 getting now Jan 26 20:01:47 PuffTheMagic, scroll bar on the right side Jan 26 20:01:52 a scrubber of sorts Jan 26 20:02:21 tap it to snap to whatever position you tapped, drag on it to slide it... Jan 26 20:02:30 cryptk, trying to implement a scrollbar in Tide was a nightmare Jan 26 20:02:30 basically, keep it wherever your finger is... Jan 26 20:02:33 hehe Jan 26 20:03:10 but i suppose we could sacrifice a column of text for a scollbar Jan 26 20:10:52 just got a nice jolt of 110v Jan 26 20:18:35 Brybry, ka6sox thoughts? any glaring issues? safe to release? Jan 26 20:22:37 just getting off the phone...brb...looking Jan 26 20:27:14 I haven't run into anything yet Jan 26 20:28:13 PuffTheMagic, wTerm is not longer useful to me. Jan 26 20:29:27 changing the scrollbuffer size in prefs might be an issue Jan 26 20:29:41 but that's more usability Jan 26 20:30:10 sudo is not installed, and su - does not work because the app is not suid Jan 26 20:30:23 heyo, crashed it :D Jan 26 20:30:30 kewl! Jan 26 20:30:46 set scrollbuffer to smaller size than current scroll buffer in prefs :D Jan 26 20:31:05 I understand completely why its being done...but that makes it not useful. Jan 26 20:31:31 hm, though that isn't in all cases Jan 26 20:31:52 ka6sox: read the readme Jan 26 20:32:04 ka6sox: just go to misc prefs, and change wterm to root Jan 26 20:32:09 or that Jan 26 20:32:17 but you can also add the wterm use to the root gruop Jan 26 20:32:20 as it says in the readme Jan 26 20:32:39 it's ok, I fell for this problem too Jan 26 20:33:31 https://github.com/PuffTheMagic/wTerm#readme Jan 26 20:35:19 I broke luna :D Jan 26 20:35:27 ka6sox, you need to add wterm user to the root group Jan 26 20:35:28 OR Jan 26 20:35:37 change the default exec command to use root Jan 26 20:35:52 setting scrollbuffer to -1 and then 99 caused bad things to happen Jan 26 20:36:00 :D Jan 26 20:36:06 i didnt check for negatives :D Jan 26 20:36:37 and when I put like lets say 500 lines in there with a 1000 default scrollbuffer, then scrolled somewhere in the middle, then set my scrollbuffer size to 100 it crashed the plugin Jan 26 20:36:49 but I got distracted and haven't tried a second time Jan 26 20:37:11 going from 100 to 50 on the next startup with no lines added worked fine Jan 26 20:37:17 ka6sox, you fix your term for safe root access and then take back your statement ;) Jan 26 20:37:51 and I'm starving so afk a bit Jan 26 20:38:30 Brybry, im gonna move the safe root stuff in the readme to the wiki so that I can direct link to it Jan 26 20:41:33 PuffTheMagic, there is no help screen on the device, if Brybry hadn't put the link in here I would have had to go dig around github to find it, and when I started asking about working on a help screen for wTerm was told we didn't need one. Jan 26 20:42:34 ka6sox, sorry, i never ment to imply it didnt need a help scene, just it shouldnt need a list of dedicated keybindings since the prefs list itself could act as one Jan 26 20:42:42 a help scene would be useful Jan 26 20:42:57 people don't have time to have to go digging thru websites to figure out how to use an app...and assuming that you will always be online while working with an app like wTerm so they can get this info from there is a fallacy Jan 26 20:43:37 I agree a help scene is needed, never said one wasnt Jan 26 20:44:11 ka6sox, i would be happy if you wanted to work on one Jan 26 21:11:48 PuffTheMagic, have we verified that if you add a root password it wont' break anything else? Jan 26 21:12:08 and you are aware that the password will be wiped out again most likely with the next OTA update Jan 26 21:23:53 we don't set a root password Jan 26 21:25:03 oh, the instructions Jan 26 21:25:03 hmm Jan 26 21:32:16 Brybry, ya, thats an issue Jan 26 21:32:24 I opted to skip that step Jan 26 21:32:24 but Jan 26 21:32:42 you bring up an interesting point/if it does bad things then we shouldn't be suggesting that to our users Jan 26 21:33:02 the main thing I remember is that an OTA wipes it out Jan 26 21:33:12 so its kind of useless Jan 26 21:33:29 much better to make sudo work I suspect Jan 26 21:36:13 su works Jan 26 21:36:13 what happens if you set a root password and still use login root in wterm? Jan 26 21:36:23 it should prompt for a password Jan 26 21:36:29 well.. should :) Jan 26 21:36:31 it used to Jan 26 21:37:58 Brybry, try su - Jan 26 21:38:05 at worst login will kick your to a login: prompt Jan 26 21:38:08 su works for me Jan 26 21:38:11 okay Jan 26 21:38:30 I have wterm added to the root group but no root password set Jan 26 21:39:10 and I can't do bad things unless I su first Jan 26 21:39:11 thats cheating Jan 26 21:39:20 its not what the OOB one does Jan 26 21:39:26 su Jan 26 21:39:33 we package our own su Jan 26 21:39:38 su: must be suid to work properly Jan 26 21:39:48 I think we do at least Jan 26 21:39:53 or we copy the default one and set permissions Jan 26 21:39:53 or something Jan 26 21:39:59 Brybry, this will be wiped out when they OTA Jan 26 21:40:08 ie: its not OTA safe Jan 26 21:40:20 they fix up things like users and groups Jan 26 21:40:37 so they see our meddling as "damage" and attempt to correct it. Jan 26 21:40:40 well, test it, and if it doesn't work think of a way to make it work :P Jan 26 21:41:02 the first solution, the one in the readme works. Jan 26 21:41:06 and perhaps we can get them to include a nice "default" user in the next update Jan 26 21:41:22 yup, maybe we can. Jan 26 21:41:38 and then we perhaps can make wterm "safe" and remove the command option Jan 26 21:41:47 I'm confused Jan 26 21:41:51 as setting a root pw is pretty useless if i can just specify a shell... Jan 26 21:42:17 that is the issue... Jan 26 21:42:37 it wasn't intended to work the way we are trying to make wTerm work. Jan 26 21:42:47 well Jan 26 21:42:56 not running as root by default is a good choice imho Jan 26 21:43:10 i don't think a root pw is needed right now Jan 26 21:43:19 when we have sources for the base OS and can push a change that includes a "safe" user and get them to accept it...we can fix it. Jan 26 21:43:24 its not Jan 26 21:44:14 set a root pw and remove the command option, and it is probably safe (at least wterm - but you can just install xterm or similar, but we can't fix that) Jan 26 21:44:48 also i'd be nice to have different lock levels Jan 26 21:45:04 iirc... the issue is. Jan 26 21:45:10 for example i have no problem with other people playing angry birds on my tp, but reading my mails.. well. Jan 26 21:45:15 /bin/su can't be setuid without a root pw otherwise every other app can su to root Jan 26 21:45:28 also, once su to root, breaking chroots is trivial Jan 26 21:45:31 I'd guess that for now we should just abandon any pretext of being "safe" Jan 26 21:45:44 su shipped in $APPDIR was tried, but the cryptofs is mounted nosetuid Jan 26 21:45:46 since any fiddling we do won't survived a OTA Jan 26 21:46:29 so a root pw actually is important, hm Jan 26 21:46:48 its not Jan 26 21:46:50 not used Jan 26 21:46:52 will be wiped out Jan 26 21:47:00 stfu Jan 26 21:48:27 what might work is a setuid root:wterm /usr/local/bin/su that doesn't use /etc/passwd Jan 26 21:49:06 that also does a getuid() check or something Jan 26 21:49:08 people that use wterm and set root passwords can also be reminded after an ota to set a new password Jan 26 21:49:13 problem solved Jan 26 21:49:19 but that would mean the uid has to be fixed-ish Jan 26 21:49:21 the only concept of "security" is putting things in a Jail. Jan 26 21:50:38 and only giving the app what is whitelisted. Jan 26 21:51:40 I would think the only time you'd even need a root password would be with the just type stuff (and needing to su alone might stop that, I'll have to test) Jan 26 22:04:17 ka6sox, setting root pw doesnt break anything Jan 26 22:05:27 and I don't really understand the OTA issue, they are so rare Jan 26 22:06:39 Brybry, we dont package a su Jan 26 22:06:59 what I do is cp busybox to a new location that is at the head of path Jan 26 22:07:07 hey, we've had 4 or so of them in the last couple months or so, no? Jan 26 22:07:07 and I chmod ug+s it Jan 26 22:07:12 yeah, that's what I said I think afterwards Jan 26 22:08:17 hey, I know... can run a Root Shell service. Jan 26 22:08:38 and only allow wterm to connect to it Jan 26 22:08:42 lame Jan 26 22:08:43 and it'll run commands as root and return the output Jan 26 22:08:52 can call it... rshd Jan 26 22:10:16 and then you can add authentication to it. Maybe some encryption. Make it more Secure... Jan 26 22:10:19 at least make it listen on a unix socket so you can send the fd instead of piping all data Jan 26 22:10:28 why all of the extra hastle Jan 26 22:10:41 on an OTA the passwd and group will get wipes Jan 26 22:10:47 so there is no security issue Jan 26 22:10:51 and your user Jan 26 22:11:17 well I can move creating the wterm user to inside the app Jan 26 22:11:25 so it make sure it exists each start Jan 26 22:11:30 * dwc- doens't think anyone got his joke :( Jan 26 22:11:44 :P Jan 26 22:11:58 PuffTheMagic, a good idea Jan 26 22:13:47 read the prefs, if you use the wterm user, create it Jan 26 22:13:50 if root don't Jan 26 22:14:10 yes! ondemand font rendering works again. Jan 26 22:14:57 you could even make a dropdown box that chooses between the 2 :D Jan 26 22:15:39 ka6sox, the command that gets exec'd is already configurable, i dont think a forced choice drop down is the best idea Jan 26 22:15:52 i mean, idk what most people would use otherwise Jan 26 22:16:13 the choice is really whether to use a "safe user" or a root one Jan 26 22:16:29 ya I suppose Jan 26 22:16:41 i guess thats a reasonable change Jan 26 22:17:34 forget the concept of a rootpw Jan 26 22:18:06 no the root pw is still needed Jan 26 22:18:08 better to let them have multiple cards...one priv, one non-priv Jan 26 22:18:14 why? Jan 26 22:18:25 su is unsafe with out a root passwd Jan 26 22:18:41 why su? Jan 26 22:18:59 just tell them to start a privileged wterm instead of a normal+su? Jan 26 22:19:02 wait wait wait Jan 26 22:19:02 if you instantiate one as priv and a separate one as non-priv Jan 26 22:19:05 ka6sox has a point: just provide a menu entry "start root terminal" Jan 26 22:19:10 why is su unsafe without a root password Jan 26 22:19:14 in this instance Jan 26 22:19:25 Brybry: other apps could use it to break out of their jails Jan 26 22:19:27 Brybry: su is unsafe because it allows other chrooted apps to su to root and break the jail Jan 26 22:19:45 ka6sox, i dont want to have to create a new card to do something as root Jan 26 22:19:50 thats why su Jan 26 22:19:58 alias su='ssh root@localhost' Jan 26 22:20:12 PuffTheMagic, that isn't OTA safe Jan 26 22:20:23 and after a OTA the box is vulnerable Jan 26 22:20:29 ka6sox, no, its not Jan 26 22:20:34 *till* you set your password. Jan 26 22:20:43 but other apps wouldn't be in the root group? Jan 26 22:20:52 and aren't they still in their jails Jan 26 22:21:04 ka6sox, both /etc/passwd and /etc/group will get erased, that causes su to not work Jan 26 22:21:14 s/erased/replaced/ Jan 26 22:21:35 after OTA there is no vulnerability Jan 26 22:21:36 better to not attempt privilege escalation. Jan 26 22:21:53 I thought the whole point of the jail was they couldn't access things not explicitly given to them in their jail Jan 26 22:21:53 better to just bring up a root console Jan 26 22:22:01 ka6sox, i can add an option for that Jan 26 22:22:06 but im not removing su Jan 26 22:22:13 Brybry: posix chroot()s are trivially breakable once you have uid=0 Jan 26 22:22:21 Brybry, wterm is not jailed Jan 26 22:22:39 I'm just talking about su and other apps Jan 26 22:22:41 not wterm Jan 26 22:23:06 the security issue is from launch args Jan 26 22:23:16 which other apps could use regardless of their jail Jan 26 22:23:17 PuffTheMagic: i actually like the "new tab" idea. could even make it a red background or font by default. Jan 26 22:24:03 the launch args thing I get but other apps can't run wterm directly and so the only thing they can do is call the 'just type' functionality, right? Jan 26 22:24:04 basically its a bad idea to attempt privilege escalation, better to start with it explicitly Jan 26 22:24:18 and given how that works would it just run 'su' and nothing else, bringing up a root console? Jan 26 22:24:28 like I don't think they could send it 'su; blahblahblah' Jan 26 22:24:34 su -c "id" Jan 26 22:25:32 PuffTheMagic, so where to documents edited by the wTerm user end up? and who owns them? and what group are they in? Jan 26 22:25:33 ka6sox, if you dont want to mess with su then just set your default exec to login in as root and call it a day Jan 26 22:27:36 ka6sox, documents edited by the wTerm user end up? huh? Jan 26 22:27:56 vi foo.doc Jan 26 22:28:09 where does that live when you are done editing it? Jan 26 22:28:19 ka6sox, it lives in your pwd Jan 26 22:28:21 pwd...? Jan 26 22:28:21 who owns it, what group is it in, what are the permissions Jan 26 22:28:38 okay thats going to fail Jan 26 22:28:47 why? Jan 26 22:28:54 have you tried? Jan 26 22:29:05 unless you are putting yourself in the root group. Jan 26 22:29:29 which is a security hole too. Jan 26 22:29:45 how does it fail? Jan 26 22:31:59 I see Jan 26 22:32:12 when the wterm user gets wiped it reverts back to a UID/GID pair Jan 26 22:32:24 dwc-, su -c "ls" pops up a big warning notification saying the command it's about to run (but it does run), and you have to have manually added wterm to allow just type action... Jan 26 22:32:31 and things in /var/home/85 appear Jan 26 22:32:45 wfm Jan 26 22:33:18 so, prob shouldnt delete wterm user on postinst Jan 26 22:33:32 err, prerm Jan 26 22:33:45 nope Jan 26 22:33:47 I wouldn't Jan 26 22:34:51 PuffTheMagic, do you plan no having tabs in the future? Jan 26 22:34:59 or separate cards? Jan 26 22:35:06 already have separate card support Jan 26 22:35:09 we have separate card support Jan 26 22:35:37 then an option to start a root session would be a good one Jan 26 22:35:38 I can even launch/close/navigate wterms without touching my touchpad :D Jan 26 22:35:59 have it bring up a card, and put a RED border around it or something Jan 26 22:46:51 ya know, i believe there is a way once wterm is launched for the first time, to create a new icon in the launcher Jan 26 22:46:59 so I could have it craete a "root" term icon :D Jan 26 22:47:51 can't it be another scene that you bring up or is it more like bringing up another x-server? Jan 26 22:48:17 (ie like wIRC and another card for a separate channel/PM) Jan 26 22:55:40 PuffTheMagic: I think oil knows how to do additional launchpoints Jan 26 23:02:00 ka6sox, the new launchpoint would just spawn a new card with specific command to log in as root Jan 26 23:02:05 so sorta like wirc multi card Jan 26 23:02:07 except Jan 26 23:02:21 wirc dies when it looses its main card cause it only uses 1 plugin Jan 26 23:02:32 wterm uses a new plugin instance for each "visible" card Jan 26 23:03:43 PuffTheMagic, that sounds like the trick. Jan 26 23:04:10 trick? Jan 26 23:04:20 so being able to ID a root card in the cardview mode would be helpful Jan 26 23:05:16 trick= way to go Jan 26 23:05:30 ka6sox, that is also on my todo list, when apps are in card view i want to overlay a scrim of some sort that has the window title as set by the tmer Jan 26 23:05:50 i might be able to tell if its root idk Jan 26 23:07:30 if you start it as root then you will know Jan 26 23:08:08 yes, but i am also trying to consider what to do if someone becomes root after it starts Jan 26 23:08:23 right, thats tougher Jan 26 23:08:25 much Jan 26 23:08:31 happens with xterms too Jan 26 23:08:55 i need to fix the buffer lines crashing and input validation Jan 26 23:09:04 then i will get on some of these user/root issues Jan 26 23:09:38 okay I leave you alone so you can play...thanks! Jan 26 23:25:40 Brybry, can you pull and see if you can crash wterm/luna when changing scollbuffer Jan 26 23:30:13 ka6sox, ping Jan 26 23:31:41 PuffTheMagic, pong? Jan 26 23:32:04 when you were talking about deleting the wterm user what did you mean by /var/home/85 Jan 26 23:46:30 when a user/group gets deleted from a system what is left is the UID/GID instead of a username Jan 26 23:47:12 so instead of /var/home/wterm its /var/home/{UID} Jan 26 23:47:26 sorry Jan 26 23:47:36 the owner and group come out that way Jan 26 23:47:38 sorry Jan 26 23:47:47 too many things happening @ 1 time Jan 26 23:53:23 i did not experience that when I deleted wterm Jan 26 23:53:29 the perms changed yes Jan 26 23:53:41 but the home name did not Jan 26 23:54:44 as im adding this code to create the wterm user, i could also check to see if a root passwd is set and make the user set one Jan 26 23:55:21 then i could set the wterm user to root group when I create it and avoid all the extra user steps Jan 27 00:01:59 that doesnt' happen when you delete wterm Jan 27 00:02:18 when passwd and groups are reset Jan 27 00:16:30 oops Jan 27 00:16:37 i just 'make -j87 test' Jan 27 00:16:39 lol Jan 27 01:09:12 hrmpf Jan 27 01:09:30 something doesn't work with resizing Jan 27 01:09:43 like? Jan 27 01:10:29 it tries to access lines that doesn't exist Jan 27 01:10:36 i'm still not on curren thead Jan 27 01:10:55 stbuehler, have you pulled in my code for the scroll buffer? Jan 27 01:11:24 nope Jan 27 01:11:39 hmmm ok Jan 27 01:12:49 i didn't pull cmatrix source/ncurses deps as i don't have build.git yet Jan 27 01:19:24 somehow the added lines get removed immediately Jan 27 01:22:42 ah. Jan 27 01:22:46 savescreen i guess Jan 27 01:25:24 you still dont have build.git? Jan 27 01:25:25 :/ Jan 27 01:26:27 worked very well for me until now :) Jan 27 01:26:51 you want setNumBufferLines(m_displayScreenSize.getY()); in void TerminalState::restoreScreen() before the unlock Jan 27 01:29:35 is there really no way around resetting opengl after resize? i hate that part :) Jan 27 01:30:02 no way that I know of Jan 27 01:30:09 damn Jan 27 01:30:14 but im no expert Jan 27 01:30:19 feel free to explore the issue Jan 27 01:30:40 perhaps we could cache the glyphs in memory Jan 27 01:31:46 would use 0.5-1mb Jan 27 02:15:54 hrmpf. when i get the resizing fixed i probably could push my changes... Jan 27 02:16:12 but first i should get some sleep :) n8 **** ENDING LOGGING AT Fri Jan 27 02:59:57 2012