August 2012 - Installer-dev

Re: Run flat package postscript as root
by Stephane Sudre 22 Aug '12

22 Aug '12

I would guess the domain option supersedes the authentication option as when you install items into the current user's home directory, root permissions are not needed. That's the design issue of this domain/installation destination option: it affects all the packages within a distribution. There's no way to install packages both in / and ~ with this option. On Wed, Aug 22, 2012 at 2:44 PM, Harald Dersch <Harald.Dersch(a)vasco.com> wrote: > I'm afraid you're right. I prepared a package without using domains by installing to the user folder via the 'tmp folder hack'. This is awful, but it works. > The script runs as root, the executable has administrative privileges and works correctly. I wonder why it's called root/admin authentication, then. > > Thanks, > >> Subject: Re: Run flat package postscript as root >> From: Stephane Sudre <email@hidden> >> Date: Wed, 22 Aug 2012 12:18:28 +0200 >> Authentication-results: symauth.service.identifier >> Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; >> bh=18iyTVYnaIeRCWQWkRj5eSpFQ77kr+o0tw1m5EPxiac=; b=VzOboSVDdg5B4JB5UqaTllToUWYpI6+sYaWUSOX/b7PS414a960JnY770zmENYxXZt CDbfwDHFCi8jEPNnWoLaY8pkyzUE7jjGgyO3jIruJdCa/Y9cpF/HMmMmW9hxz8OPqFLv >BUL+8rx9gXgk8CXdLhQIXJSZBv7Om7kHfGleKSmqrVfAU/9X80bLICF73JL+BJe0P2BO RAp4BcXqUKJvv8Vxr0JabqoNuapYQcuv0Q6+Rl9CVpWCyEHp016bv4JpY6P6Lhv1rzk+ >Y5mK8c+b10fj+ObYi98wg0DOGq2bRQI0HK7nuNwNFPOdod+ho4No3e1H2+GmFU+bwDZ9 2ySg== >> >> It's probably related to the use of the "current user/user home >> directory" domain/install Destination. >> >> >> >> On Wed, Aug 22, 2012 at 9:44 AM, Harald Dersch <email@hidden> wrote: >> > Hello, >> > I'm currently developing a setup targeting flat packages. The setup installs a browser plug-in to the user home folder (via current user domain), >> > but needs to change a global registration. The registration is done by an executable included as an additional resource in the setup and supposed >> > to be launched by the postinstallation script. >> > >> > I did a project with one package where I enabled "Require admin password for installation". I get a credential prompt, and the plug-in is correctly >> > installed to the current user folder. However, postinstallation is not executed as root, no matter which credentials I provide, hence the executable >> > fails. If I try to launch the executable explicitly using sudo, I get "sudo: no tty present and no askpass program specified" (in the log). >> > >> > It doesn't matter, if I use PackageMaker or sudre's Packages. >> > >> > From the Packages user manual (Section "Defining a package pre- and post-installation scripts"): " >> If the installation process requests an admin >> > password, the pre- and post-installation scripts will be run as root." -> Obviously this is wrong, or do I miss something? >> > >> > Thanks for any input, >> > Harry >> > >> > _______________________________________________ >> > Do not post admin requests to the list. They will be ignored. >> > Installer-dev mailing list (email@hidden) >> > Help/Unsubscribe/Update your Subscription: >> > >> > This email sent to email@hidden >> >> >> >> -- >> Packaging Resources - http://s.sudre.free.fr/Packaging.html >> > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/dev.iceberg%40gmail.c… > > This email sent to dev.iceberg(a)gmail.com -- Packaging Resources - http://s.sudre.free.fr/Packaging.html _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Run flat package postscript as root
by Harald Dersch 22 Aug '12

22 Aug '12

I'm afraid you're right. I prepared a package without using domains by installing to the user folder via the 'tmp folder hack'. This is awful, but it works. The script runs as root, the executable has administrative privileges and works correctly. I wonder why it's called root/admin authentication, then. Thanks, > Subject: Re: Run flat package postscript as root > From: Stephane Sudre <email@hidden> > Date: Wed, 22 Aug 2012 12:18:28 +0200 > Authentication-results: symauth.service.identifier > Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; > bh=18iyTVYnaIeRCWQWkRj5eSpFQ77kr+o0tw1m5EPxiac=; b=VzOboSVDdg5B4JB5UqaTllToUWYpI6+sYaWUSOX/b7PS414a960JnY770zmENYxXZt CDbfwDHFCi8jEPNnWoLaY8pkyzUE7jjGgyO3jIruJdCa/Y9cpF/HMmMmW9hxz8OPqFLv >BUL+8rx9gXgk8CXdLhQIXJSZBv7Om7kHfGleKSmqrVfAU/9X80bLICF73JL+BJe0P2BO RAp4BcXqUKJvv8Vxr0JabqoNuapYQcuv0Q6+Rl9CVpWCyEHp016bv4JpY6P6Lhv1rzk+ >Y5mK8c+b10fj+ObYi98wg0DOGq2bRQI0HK7nuNwNFPOdod+ho4No3e1H2+GmFU+bwDZ9 2ySg== > > It's probably related to the use of the "current user/user home > directory" domain/install Destination. > > > > On Wed, Aug 22, 2012 at 9:44 AM, Harald Dersch <email@hidden> wrote: > > Hello, > > I'm currently developing a setup targeting flat packages. The setup installs a browser plug-in to the user home folder (via current user domain), > > but needs to change a global registration. The registration is done by an executable included as an additional resource in the setup and supposed > > to be launched by the postinstallation script. > > > > I did a project with one package where I enabled "Require admin password for installation". I get a credential prompt, and the plug-in is correctly > > installed to the current user folder. However, postinstallation is not executed as root, no matter which credentials I provide, hence the executable > > fails. If I try to launch the executable explicitly using sudo, I get "sudo: no tty present and no askpass program specified" (in the log). > > > > It doesn't matter, if I use PackageMaker or sudre's Packages. > > > > From the Packages user manual (Section "Defining a package pre- and post-installation scripts"): " >> If the installation process requests an admin > > password, the pre- and post-installation scripts will be run as root." -> Obviously this is wrong, or do I miss something? > > > > Thanks for any input, > > Harry > > > > _______________________________________________ > > Do not post admin requests to the list. They will be ignored. > > Installer-dev mailing list (email@hidden) > > Help/Unsubscribe/Update your Subscription: > > > > This email sent to email@hidden > > > > -- > Packaging Resources - http://s.sudre.free.fr/Packaging.html > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Run flat package postscript as root
by Stephane Sudre 22 Aug '12

22 Aug '12

It's probably related to the use of the "current user/user home directory" domain/install Destination. On Wed, Aug 22, 2012 at 9:44 AM, Harald Dersch <Harald.Dersch(a)vasco.com> wrote: > Hello, > I'm currently developing a setup targeting flat packages. The setup installs a browser plug-in to the user home folder (via current user domain), but needs to change a global registration. The registration is done by an executable included as an additional resource in the setup and supposed to be launched by the postinstallation script. > > I did a project with one package where I enabled "Require admin password for installation". I get a credential prompt, and the plug-in is correctly installed to the current user folder. However, postinstallation is not executed as root, no matter which credentials I provide, hence the executable fails. If I try to launch the executable explicitly using sudo, I get "sudo: no tty present and no askpass program specified" (in the log). > > It doesn't matter, if I use PackageMaker or sudre's Packages. > > From the Packages user manual (Section "Defining a package pre- and post-installation scripts"): " >> If the installation process requests an admin password, the pre- and post-installation scripts will be run as root." -> Obviously this is wrong, or do I miss something? > > Thanks for any input, > Harry > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/dev.iceberg%40gmail.c… > > This email sent to dev.iceberg(a)gmail.com -- Packaging Resources - http://s.sudre.free.fr/Packaging.html _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Run flat package postscript as root
by Harald Dersch 22 Aug '12

22 Aug '12

Hello, I'm currently developing a setup targeting flat packages. The setup installs a browser plug-in to the user home folder (via current user domain), but needs to change a global registration. The registration is done by an executable included as an additional resource in the setup and supposed to be launched by the postinstallation script. I did a project with one package where I enabled "Require admin password for installation". I get a credential prompt, and the plug-in is correctly installed to the current user folder. However, postinstallation is not executed as root, no matter which credentials I provide, hence the executable fails. If I try to launch the executable explicitly using sudo, I get "sudo: no tty present and no askpass program specified" (in the log). It doesn't matter, if I use PackageMaker or sudre's Packages. >From the Packages user manual (Section "Defining a package pre- and post-installation scripts"): " >> If the installation process requests an admin password, the pre- and post-installation scripts will be run as root." -> Obviously this is wrong, or do I miss something? Thanks for any input, Harry _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Invalid certificate???
by Howard Moon 17 Aug '12

17 Aug '12

That's it! I was missing that intermediate certificate. Thanks much, Stephane! Regards, Howard On Aug 17, 2012, at 12:32 AM, Stephane Sudre wrote: > Signing would even work on Mac OS X 10.5.8 if productsign was > compatible with it (codesign works on 10.5.8 and Gatekeeper compatible > binaries can be built). > > From your description, it looks like an intermediate certificate is missing. > > You should have the "Developer ID Certification Authority" certificate > installed on your signing system. > > On Thu, Aug 16, 2012 at 7:11 PM, Howard Moon <howard(a)antarestech.com> wrote: >> I suspect signing my installer WOULD have worked on my Snow Leopard machine, >> IF that certificate didn't say it was signed by an unknown authority. What I >> don't know is why it says that. >> >> On Aug 16, 2012, at 9:54 AM, Rustam Muginov wrote: >> >> Signing on 10.6.8 does work for me, >> I just need to use command-line invocation of signing utilities (codesign >> for binaries, productsign for installer packages). >> >> -- >> Sincerely, >> Rustam Muginov >> >> On Aug 16, 2012, at 9:43 AM, George Taylor wrote: >> >> Hi Howard, >> >> I had a very similar issue and this is what Apple DTS instructed me to do: >> >> Developer ID signing is only supported on OS X 10.7.3 and later >> with Xcode 4.3 and later. You may need to sign your app by hand on >> a 10.7.3 or later system. >> >> If you do that (instead of using Xcode 4.3+), create a small test >> project and have Xcode sign it. Then pass the same designated >> requirement to codesign, changing the identifier to match your >> app's bundle ID. >> >> >> >> So apparently signing in SL is a no-go. >> >> George >> >> >> >> On Aug 16, 2012, at 11:56 AM, Howard Moon wrote: >> >> Well, if I do the actual signing on my Mountain Lion machine, everything >> works perfectly. Not sure why my certificate says it's signed by an unknown >> authority on my Snow Leopard machine, but that appears to be the cause for >> the signing itself to fail. For now, I'll just take it to my other box to >> sign and move on from there. >> >> Thanks, >> Howard >> >> On Aug 15, 2012, at 6:44 PM, Rustam Muginov wrote: >> >> That would be very easy to test. >> Create a small simple installer, sign it, put on web server and post link >> here. >> Someone would try and report. >> -- >> Sincerely, >> Rustam Muginov >> >> >> >> On Aug 14, 2012, at 2:04 PM, Howard Moon wrote: >> >> Well, that didn't solve the problem. His machine still pops up that dialog. >> >> I looked in my Keychain Access app on my development machine, and I see that >> the Developer ID Installer certificate says "This certificate was signed by >> an unknown authority." I removed that, rebooted, and re-imported it from my >> Mountain Lion machine, but it still says that. Could this be the problem? >> Do I need to sign the installers from my Mountain Lion machine, instead of >> my development Snow Leopard machine? Or is this a problem on HIS end??? >> >> -Howard >> >> On Aug 14, 2012, at 11:25 AM, Howard Moon wrote: >> >> I *think* I know the answer. Since I do my development on a Snow Leopard >> machine using Xcode 3.2.x, I had exported my Developer and Installer >> certificates and imported them on my Snow Leopard machine. I think I need >> the "intermediate" certificate mentioned in the online docs in order to have >> productsign properly embed it so that users' machines don't have to already >> have that on their machines. That should allow the installers to run on >> machines that haven't installed that certificate already, right? >> >> >> Can I just export that certificate and import it on my Snow Leopard machine, >> or do I have to actually do the signing on my Mountain Lion machine? >> >> >> Thanks, >> >> -Howard >> >> >> On Aug 14, 2012, at 11:10 AM, Howard Moon wrote: >> >> >> The installer works fine on that same co-worker's Mountain Lion OS, so it >> looks like an OS issue. >> >> >> He's going to test in Snow Leopard and Leopard, but so far it's only failing >> on Lion (and he can choose to Continue, anyway, but we don't want *users* to >> have to make that decision!). >> >> >> Thanks, >> >> Howard >> >> >> >> On Aug 14, 2012, at 10:49 AM, Howard Moon wrote: >> >> >> Hi all, >> >> >> I made a signed installer that checks out fine for me, using a "clean" >> Mountain Lion OS. But a co-worker who has downloaded the installer to test >> it is getting a "signed with an invalid certificate" error when running the >> installer in Lion. What could be the problem? >> >> >> Could the server he's taking it from have caused a problem somehow? The .pkg >> file is in a .zip file (so that I can label it by date and version, for >> internal testing, and also to prevent the Windows server at our main >> facility from messing with the file in any way). I don't see how the server >> could affect the .pkg file when it's contained in a .zip file, though. >> >> >> I'm downloading that zip file from my own local server, unzipping it, and >> then running the resulting .pkg file with no problem on my machines, but >> could using a zip file have anything to do with why he's getting this error? >> I wouldn't think so, but I'm grasping at straws here. >> >> >> Thanks, >> >> Howard >> >> >> >> >> >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Installer-dev mailing list (Installer-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/installer-dev/rmuginov%40gmail.com >> >> This email sent to rmuginov(a)gmail.com >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Installer-dev mailing list (Installer-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/installer-dev/gmt%40synthogy.com >> >> This email sent to gmt(a)synthogy.com >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Installer-dev mailing list (Installer-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/installer-dev/rmuginov%40gmail.com >> >> This email sent to rmuginov(a)gmail.com >> >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Installer-dev mailing list (Installer-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/installer-dev/dev.iceberg%40gmail.c… >> >> This email sent to dev.iceberg(a)gmail.com >> > > > > -- > Packaging Resources - http://s.sudre.free.fr/Packaging.html > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/howard%40antarestech.… > > This email sent to howard(a)antarestech.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Invalid certificate???
by Stephane Sudre 17 Aug '12

17 Aug '12

Signing would even work on Mac OS X 10.5.8 if productsign was compatible with it (codesign works on 10.5.8 and Gatekeeper compatible binaries can be built). >From your description, it looks like an intermediate certificate is missing. You should have the "Developer ID Certification Authority" certificate installed on your signing system. On Thu, Aug 16, 2012 at 7:11 PM, Howard Moon <howard(a)antarestech.com> wrote: > I suspect signing my installer WOULD have worked on my Snow Leopard machine, > IF that certificate didn't say it was signed by an unknown authority. What I > don't know is why it says that. > > On Aug 16, 2012, at 9:54 AM, Rustam Muginov wrote: > > Signing on 10.6.8 does work for me, > I just need to use command-line invocation of signing utilities (codesign > for binaries, productsign for installer packages). > > -- > Sincerely, > Rustam Muginov > > On Aug 16, 2012, at 9:43 AM, George Taylor wrote: > > Hi Howard, > > I had a very similar issue and this is what Apple DTS instructed me to do: > > Developer ID signing is only supported on OS X 10.7.3 and later > with Xcode 4.3 and later. You may need to sign your app by hand on > a 10.7.3 or later system. > > If you do that (instead of using Xcode 4.3+), create a small test > project and have Xcode sign it. Then pass the same designated > requirement to codesign, changing the identifier to match your > app's bundle ID. > > > > So apparently signing in SL is a no-go. > > George > > > > On Aug 16, 2012, at 11:56 AM, Howard Moon wrote: > > Well, if I do the actual signing on my Mountain Lion machine, everything > works perfectly. Not sure why my certificate says it's signed by an unknown > authority on my Snow Leopard machine, but that appears to be the cause for > the signing itself to fail. For now, I'll just take it to my other box to > sign and move on from there. > > Thanks, > Howard > > On Aug 15, 2012, at 6:44 PM, Rustam Muginov wrote: > > That would be very easy to test. > Create a small simple installer, sign it, put on web server and post link > here. > Someone would try and report. > -- > Sincerely, > Rustam Muginov > > > > On Aug 14, 2012, at 2:04 PM, Howard Moon wrote: > > Well, that didn't solve the problem. His machine still pops up that dialog. > > I looked in my Keychain Access app on my development machine, and I see that > the Developer ID Installer certificate says "This certificate was signed by > an unknown authority." I removed that, rebooted, and re-imported it from my > Mountain Lion machine, but it still says that. Could this be the problem? > Do I need to sign the installers from my Mountain Lion machine, instead of > my development Snow Leopard machine? Or is this a problem on HIS end??? > > -Howard > > On Aug 14, 2012, at 11:25 AM, Howard Moon wrote: > > I *think* I know the answer. Since I do my development on a Snow Leopard > machine using Xcode 3.2.x, I had exported my Developer and Installer > certificates and imported them on my Snow Leopard machine. I think I need > the "intermediate" certificate mentioned in the online docs in order to have > productsign properly embed it so that users' machines don't have to already > have that on their machines. That should allow the installers to run on > machines that haven't installed that certificate already, right? > > > Can I just export that certificate and import it on my Snow Leopard machine, > or do I have to actually do the signing on my Mountain Lion machine? > > > Thanks, > > -Howard > > > On Aug 14, 2012, at 11:10 AM, Howard Moon wrote: > > > The installer works fine on that same co-worker's Mountain Lion OS, so it > looks like an OS issue. > > > He's going to test in Snow Leopard and Leopard, but so far it's only failing > on Lion (and he can choose to Continue, anyway, but we don't want *users* to > have to make that decision!). > > > Thanks, > > Howard > > > > On Aug 14, 2012, at 10:49 AM, Howard Moon wrote: > > > Hi all, > > > I made a signed installer that checks out fine for me, using a "clean" > Mountain Lion OS. But a co-worker who has downloaded the installer to test > it is getting a "signed with an invalid certificate" error when running the > installer in Lion. What could be the problem? > > > Could the server he's taking it from have caused a problem somehow? The .pkg > file is in a .zip file (so that I can label it by date and version, for > internal testing, and also to prevent the Windows server at our main > facility from messing with the file in any way). I don't see how the server > could affect the .pkg file when it's contained in a .zip file, though. > > > I'm downloading that zip file from my own local server, unzipping it, and > then running the resulting .pkg file with no problem on my machines, but > could using a zip file have anything to do with why he's getting this error? > I wouldn't think so, but I'm grasping at straws here. > > > Thanks, > > Howard > > > > > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/rmuginov%40gmail.com > > This email sent to rmuginov(a)gmail.com > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/gmt%40synthogy.com > > This email sent to gmt(a)synthogy.com > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/rmuginov%40gmail.com > > This email sent to rmuginov(a)gmail.com > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/installer-dev/dev.iceberg%40gmail.c… > > This email sent to dev.iceberg(a)gmail.com > -- Packaging Resources - http://s.sudre.free.fr/Packaging.html _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Invalid certificate???
by Howard Moon 16 Aug '12

16 Aug '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Invalid certificate???
by Rustam Muginov 16 Aug '12

16 Aug '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Invalid certificate???
by George Taylor 16 Aug '12

16 Aug '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Invalid certificate???
by Howard Moon 16 Aug '12

16 Aug '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0