October 2008 - Darwin-dev - lists.apple.com

Re: locale and file functions
by Kevin Van Vechten 01 Oct '08

01 Oct '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On Oct 1, 2008, at 1:43 AM, Jonas Maebe wrote: More information is available at: http://developer.apple.com/qa/qa2001/qa1173.html http://developer.apple.com/qa/qa2001/qa1235.html - Kevin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… What is the extent of the interaction between the current locale setting (as in the LANG, LC_TYPE, etc environment variables) and the encoding expected/returned by posix functions such as open(), stat() etc? Are they always to be encoded using the current LC_TYPE, always using UTF-8, or yet something else? I also recently discovered http://developer.apple.com/documentation/CoreFoundation/Reference/CFStringR… (CFStringGetFileSystemRepresentation). It's perfectly usable when passing stuff to the posix api's, but when getting something back you still have to know what the used encoding was if you want to operate further on it. Mac OS X's posix filesystem API (open(2), stat(2), etc.) always expect path names to be UTF-8 encoded (the system will normalize them to be decomposed), and return path names which are UTF-8 encoded (decomposed). This email sent to site_archiver(a)lists.apple.com

1 0

Re: Open Firmware on Pismo
by Josh de Cesare 01 Oct '08

01 Oct '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com James, You can build up properties with encode+. The following code: Josh On Oct 1, 2008, at 4:16 AM, James Little wrote: Hi, I hope this is not too off-topic: I can write one value by using the following command: [code]12345678 encode-int " thermal-info" property[/code] Thanks (and sorry for the rambling post), James. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/decesare%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… 0 encode-int 1 encode-int encode+ 2 encode-int encode+ 3 encode-int encode+ should leave on the stack the length 4*4 and address of 16 bytes containing the long words 0, 1, 2, and 3. I've been delving around in open firmware on my Pismo to see if I can control the internal fan, or at least set a better temp. for it to come on at. In the device tree I've found the via-pmu, and under this is a node called 'power-mgt'. A property of this is called 'thermal-info'. As far as I know this must be related to the temp sensor in the Pismo because the G4 chip I have in it doesn't have the thermal assist temp diode on the chip enabled. To check that this was specific to the Pismo I found the same 'power- mgt' property on a Digital Audio G4, which had everything listed the same, apart from the 'thermal-info', which was missing. I've now hit a problem. There are 4 values of data encoded in open firmware for the 'thermal-info'. I believe they are the limits for the fan, as they do not change from boot up o when the computer is definitely toasty. However, I need to be able to write all 4 values - and I don't know the open firmware commands to do this... could anyone help? This email sent to decesare(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Open Firmware on Pismo
by James Little 01 Oct '08

01 Oct '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=talk21.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=h54x+TDNNvqCsdCJgMf5kUnEwCALiZ0ED8XuLfNmetTsKnTUlzGZUhDM5go0OJv0lDpe5YtRs6jrjI6y2zaRCxRcsUVpd0eVTvpMN5xvcnCovQvuyP9yFjvUou2XxQObwJ47XbbvXUbJtd/2HcC7AuW47tNsYJZ5vCihiIl8wx4=; Hi, I hope this is not too off-topic: I've been delving around in open firmware on my Pismo to see if I can control the internal fan, or at least set a better temp. for it to come on at. In the device tree I've found the via-pmu, and under this is a node called 'power-mgt'. A property of this is called 'thermal-info'. As far as I know this must be related to the temp sensor in the Pismo because the G4 chip I have in it doesn't have the thermal assist temp diode on the chip enabled. To check that this was specific to the Pismo I found the same 'power-mgt' property on a Digital Audio G4, which had everything listed the same, apart from the 'thermal-info', which was missing. I've now hit a problem. There are 4 values of data encoded in open firmware for the 'thermal-info'. I believe they are the limits for the fan, as they do not change from boot up o when the computer is definitely toasty. I can write one value by using the following command: [code]12345678 encode-int " thermal-info" property[/code] However, I need to be able to write all 4 values - and I don't know the open firmware commands to do this... could anyone help? Thanks (and sorry for the rambling post), James. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: launchd daemon, spawning children?
by Mario Emmenlauer 01 Oct '08

01 Oct '08

site_archiver(a)lists.apple.com Delivered-To: Darwin-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.17 (Macintosh/20080914) Hi Terry and List, You name it. I will look for a good tutorial, though Terry's suggestion contained a nice start. The primary paper on UNIX setuid() is: Setuid Demystified Hao Chen, David Wagner, Drew Dean Proceedings of the 11th USENIX Security Symposium <www.cs.berkeley.edu/~daw/papers/setuid-usenix02.pdf> Thanks a lot, the paper is great! I finally ended up with something like (pseudocode): fork(); if(pid == 0) { setgroups(); setgid(); setuid(); close_nonstd_file_descriptors(); execve("/path/to/worker"); _exit(); } else { while(1) { waitpid(WNONBLOCK); usleep(1000); } } This works very well, and makes sure the worker process can not gain higher permissions than it should have. Don't mind the while(1) above, in practice I have a network connection open between worker and server to get error-feedback, so the server won't get stuck. Your suggestion to use login seems reasonable. Can someone sketch an outline how an application (daemon) would use login to start a new process as a certain user? Is that what you meant: execve("/bin/login -f worker_user /path/to/worker") One last question: If "worker_user" is the current GUI-user, all his applications get killed on logout. Is there a way around this (or would using 'login' also solve this issue?) Thanks again, Mario Emmenlauer _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… Terry Lambert wrote: On Sep 26, 2008, at 2:37 AM, Mario Emmenlauer wrote: Damien Sorresso wrote: The rules of setuid(2) have evolved into a vastly complex morass with subtle variations on different platforms. Entire papers have been written about this behavior. In general, we do not want you to establish your own sessions, and would prefer that you use /bin/login to do session management and support the utmp/utmpx interfaces for process accounting and knowing who is logged into your system, etc.; otherwise, things get more complicated fast, in order to support those interfaces, since you have to (1) maintain privilege in order to access the files to write out the closure records on sessions started by you (login does this - it hangs around until its children go away), and (2) deal with PAM and all the other things login deals with for authenticating you to the system. This email sent to site_archiver(a)lists.apple.com

1 0

locale and file functions
by Jonas Maebe 01 Oct '08

01 Oct '08

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Hello, Thanks, Jonas _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… What is the extent of the interaction between the current locale setting (as in the LANG, LC_TYPE, etc environment variables) and the encoding expected/returned by posix functions such as open(), stat() etc? Are they always to be encoded using the current LC_TYPE, always using UTF-8, or yet something else? I also recently discovered http://developer.apple.com/documentation/CoreFoundation/Reference/CFStringR… /apple_ref/c/func/CFStringGetFileSystemRepresentation (CFStringGetFileSystemRepresentation). It's perfectly usable when passing stuff to the posix api's, but when getting something back you still have to know what the used encoding was if you want to operate further on it. This email sent to site_archiver(a)lists.apple.com

1 0