July 2006 - Darwin-dev - lists.apple.com

Re: Use of the NetInfo passwd attribute for users
by Finlay Dobbie 19 Jul '06

19 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=d7Jc9ursas823aQ5O0jiZiN0tizKKWsin71fQqoxKgP4clYcAcXy5xw+zjJGy54bn8641ELEtBT5FmMOdjjZaNiig0W//I6McEEpOs25WRPW23IBPggpzm1kxssoKAA9Kgsiyug03ZadYDjGv7QSdZG/yfqjBUm7AMXDBCqrn9A= On Jul 17, 2006, at 11:12 AM, Paul Nelson wrote: > Is this field used at all in 10.4.x? > > Will the OS ever use it during authentication for password > verification? Only if the authentication_authority for that user is either not present or is set to ";basic;". However, you can read this attribute using POSIX level calls like getpwnam(), so it is possible that legacy software might assume a crypt password even when the auth authority indicates it should not. This is the reason for the conventional "********" marker value which is not a valid crypt password. And also it's different from "*" which is traditionally used to indicate accounts which cannot be logged in to. -- Finlay _______________________________________________ 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… On 19/07/06, Jason Townsend <jtownsend(a)opendarwin.org> wrote: This email sent to site_archiver(a)lists.apple.com

1 0

Re: Use of the NetInfo passwd attribute for users
by Jason Townsend 19 Jul '06

19 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Is this field used at all in 10.4.x? Hope that helps, -Jason _______________________________________________ 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… On Jul 17, 2006, at 11:12 AM, Paul Nelson wrote: Will the OS ever use it during authentication for password verification? Only if the authentication_authority for that user is either not present or is set to ";basic;". However, you can read this attribute using POSIX level calls like getpwnam(), so it is possible that legacy software might assume a crypt password even when the auth authority indicates it should not. This is the reason for the conventional "********" marker value which is not a valid crypt password. If you don't want your users to be able to change the passwd attribute, you can simply remove the _writers_passwd attribute which is allowing them to do so. This email sent to site_archiver(a)lists.apple.com

1 0

Re: dlsym(...) and Intel Macs
by Graham J Lee 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com User-agent: Thunderbird 1.5.0.4 (Macintosh/20060530) On Jul 17, 2006, at 8:29 PM, Damien Sorresso wrote: pedagogue:~/devel/nextstep leeg$ file uname-q uname-q: Mach-O fat file with 4 architectures uname-q (for architecture i386): Mach-O executable i386 uname-q (for architecture ppc): Mach-O executable ppc uname-q (for architecture ppc64): Mach-O 64-bit executable ppc64 uname-q (for architecture m68k): Mach-O executable for m68k architecture On 18/7/06 04:35, Eric Albert wrote: On 17 Jul, 2006, at 10:16 PM, Eric Albert wrote: On Jul 17, 2006, at 8:08 PM, Damien Sorresso wrote: No, they're two separate binaries. (Trust me there's a good reason for this.) I hate to say this, but I don't quite trust you on that. :) What's the reason? I've seen an awful lot of cases over the past year where folks thought they needed separate binaries but I've yet to see one which actually did. Maybe you'll be the first.... Because the application I'm writing has to run on all versions of Panther, down to 10.3.0. (Part of its function is to make sure the user is up-to-date on point releases.) To compile a universal binary, you need to use gcc 4.0, and in order to run applications compiled with gcc 4.0, you must be running 10.3.9. How's that work for you? :) Not too well. :) You only need to use gcc 4.0 for the Intel side, but the PowerPC side of your binary can use any Mach-O compiler at all, including gcc 2.95.3 or even CodeWarrior. In fact, any Mach-O thin file for any operating system and any architecture can be combined in a fat file with any other, I think the only constraint is that the arch should differ. I used that in a demo: there's definitely no way that any gcc 4.x I've ever used can produce Mach-O files for the m68k ;-) -- Graham Lee UNIX Systems Manager, Oxford Physics Practical Course http://iamleeg.blogspot.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… This email sent to site_archiver(a)lists.apple.com

1 0

Re: dlsym(...) and Intel Macs
by Damien Sorresso 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Damien Sorresso Macintosh Developer Computer Infrastructure Support Services Illinois State University damien.sorresso(a)ilstu.edu _______________________________________________ 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 On 18 Jul, 2006, at 10:57 AM, Andrew Pinski wrote: On Jul 19, 2006, at 12:52 AM, Damien Sorresso wrote: Turns out that gcc 4.0 was setting all symbols to `private extern' by default and hiding the exported symbols. So be weary of the "Symbols Hidden by Default" build option. I'm guessing that the PowerPC side would've broken if compiled with gcc 4.0 as well. That option enables -fvisibility=hidden so yes you should understand what that option does before using it. It's enabled by default. I certainly wouldn't have turned it on. It was just a matter of looking in the right place, not a problem of understanding. As soon as I saw it, I knew it was the problem. -- smime.p7s

1 0

Re: dlsym(...) and Intel Macs
by Andrew Pinski 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On Jul 19, 2006, at 12:52 AM, Damien Sorresso wrote: -- Pinski _______________________________________________ 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… Turns out that gcc 4.0 was setting all symbols to `private extern' by default and hiding the exported symbols. So be weary of the "Symbols Hidden by Default" build option. I'm guessing that the PowerPC side would've broken if compiled with gcc 4.0 as well. That option enables -fvisibility=hidden so yes you should understand what that option does before using it. This email sent to site_archiver(a)lists.apple.com

1 0

Re: dlsym(...) and Intel Macs
by Damien Sorresso 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Damien Sorresso Macintosh Developer Computer Infrastructure Support Services Illinois State University damien.sorresso(a)ilstu.edu _______________________________________________ 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 Turns out that gcc 4.0 was setting all symbols to `private extern' by default and hiding the exported symbols. So be weary of the "Symbols Hidden by Default" build option. I'm guessing that the PowerPC side would've broken if compiled with gcc 4.0 as well. -- smime.p7s PGP.sig

1 0

Re: Extracting macbin format without stuffit.
by André-John Mas 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com You may be interested in this project, with regards to MacBinary http://sourceforge.net/projects/macbinconv and with regards to creating DMGs: Also, if you are on another platform, then the following pages http://baghira.sourceforge.net/dmg.htm Andre On 18-Jul-06, at 05:16 , Markus Hitter wrote: Am 17.07.2006 um 22:23 schrieb matt jaffa: Is there a way to extract .bin files to a usable format that OS X recognizes. It seems safari can convert the .bin files to .dmg files if you download the file through the web. HopeThatHelps, Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ 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/ajmas%40sympatico.ca _______________________________________________ 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… http://gemma.apple.com/documentation/Porting/Conceptual/ PortingUnix/distributing/chapter_9_section_4.html indicates that DMG files are 'Disk Images of the Apple FS HFS'. So the solution would involve creating an HFS disk image, mounting it read/write and then adding the files to it. .bin files are in MacBinary format. Alternative software exists (e.g. macbin) and the format is documented. Writing your own solution shouldn't be that hard either. Unless the .bin contains a .dmg, this would be a rarther complex conversion. I've found a man page <http://developer.apple.com/documentation/ Darwin/Reference/Manpages/man8/macbin.8.html>, but failed to find a copy of this page on my 10.4.7 installation. This email sent to ajmas(a)sympatico.ca This email sent to site_archiver(a)lists.apple.com

1 0

Re: Extracting macbin format without stuffit.
by Markus Hitter 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Am 17.07.2006 um 22:23 schrieb matt jaffa: Is there a way to extract .bin files to a usable format that OS X recognizes. It seems safari can convert the .bin files to .dmg files if you download the file through the web. HopeThatHelps, Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ 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… .bin files are in MacBinary format. Alternative software exists (e.g. macbin) and the format is documented. Writing your own solution shouldn't be that hard either. Unless the .bin contains a .dmg, this would be a rarther complex conversion. I've found a man page <http://developer.apple.com/documentation/ Darwin/Reference/Manpages/man8/macbin.8.html>, but failed to find a copy of this page on my 10.4.7 installation. This email sent to site_archiver(a)lists.apple.com

1 0

Re: dlsym(...) and Intel Macs
by Peter O'Gorman 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On Tue, 2006-07-18 at 00:18 -0500, Damien Sorresso wrote: > On 18 Jul, 2006, at 12:14 AM, Peter O'Gorman wrote: > > On Mon, 2006-07-17 at 23:39 -0500, Damien Sorresso wrote: > >> On 17 Jul, 2006, at 11:33 PM, Jordan K. Hubbard wrote: > >>> Wouldn't dlopen() be the first thing to fail if the bundle wasn't > >>> of the appropriate architecture? I assume Damien is also properly > >>> checking the value of mainHandle against NULL when it's returned... > >> > >> Yes, there is a NULL check in place for `dlopen(...)'. The bundle > >> executes just fine until it has to grab that symbol. And no, the > >> underscore rules have not changed as far as I know. The actual symbol > >> has an extra underscore added upon export, but `dlsym(...)' takes the > >> name of the symbol without the underscore prefix for an argument. > >> Besides, the symbol shows up just fine with `nm'. > > > > In that case, dlerror() must be telling you something after the failed > > dlsym() call. What does it say? > > Already checked. It returns a null string. Apparently that means > nothing went wrong. Even though something has. > Okay, that's pretty strange. Since you seem to be looking up symbols in the main executable, have you tried dlsym(RTLD_DEFAULT,"Symbol"); ? If so does it give you the same (blank) error? Peter _______________________________________________ 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 signature.asc

1 0

Re: dlsym(...) and Intel Macs
by Damien Sorresso 18 Jul '06

18 Jul '06

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Wouldn't dlopen() be the first thing to fail if the bundle wasn't of the appropriate architecture? I assume Damien is also properly checking the value of mainHandle against NULL when it's returned... Yes, there is a NULL check in place for `dlopen(...)'. The bundle executes just fine until it has to grab that symbol. And no, the underscore rules have not changed as far as I know. The actual symbol has an extra underscore added upon export, but `dlsym(...)' takes the name of the symbol without the underscore prefix for an argument. Besides, the symbol shows up just fine with `nm'. In that case, dlerror() must be telling you something after the failed dlsym() call. What does it say? -- Damien Sorresso Mac OS X Developer Computer Infrastructure Support Services Illinois State University E-mail: damien.sorresso(a)ilstu.edu _______________________________________________ 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 On 18 Jul, 2006, at 12:14 AM, Peter O'Gorman wrote: On Mon, 2006-07-17 at 23:39 -0500, Damien Sorresso wrote: On 17 Jul, 2006, at 11:33 PM, Jordan K. Hubbard wrote: Already checked. It returns a null string. Apparently that means nothing went wrong. Even though something has. smime.p7s

1 0