[Mr. Blur]

...check your software update!

Security Update 2005-001 delivers a number of security enhancements and is recommended for all Macintosh users. This update includes the following components:

at commands
ColorSync
libxml2
Mail
PHP
Safari

[ManOfSteal]

OMG OMG OMG!!!!1!!!!!! My uptime!!!!!

[rjenkinson]

what's up with the "001"? no more dates?

-r.

[Ganesha]

Originally posted by rjenkinson:
what's up with the "001"? no more dates?

-r.

Clearly, Apple expects more then 100 security updates this year...

[AKcrab]

Originally posted by rjenkinson:
what's up with the "001"? no more dates?

-r.

"Enjoy uncertainty�"

[Tyre MacAdmin]

Thanks Mr. Blur... it would have been all but a blur without you!

[andretan]

This update broke my Web Sharing.

Now the Personal Web Sharing pane in System Preferences will show "Web sharing starting up", and just stay there.

Logged out and back in and it was the same.

[placebo1969]

Originally posted by ManOfSteal:
OMG OMG OMG!!!!1!!!!!! My uptime!!!!!

33 days for me.

[ptitus]

Hmmm... Weird: doesn't show up in Software Update on my machine
I'm using Safari 1.3 DP, could this be the problem?

UPDATE: For anyone interested, I just installed the package (downloaded from Apple's web site) and everything went fine

[mdc]

20 days here. and i thought i would make it to 31. oh well.

[akuma-x]

Originally posted by ptitus:
Hmmm... Weird: doesn't show up in Software Update on my machine
I'm using Safari 1.3 DP, could this be the problem?

Same goes for me. DP 1.3 as well and not showing in SW update.

[Amorya]

Originally posted by andretan:
This update broke my Web Sharing.

Now the Personal Web Sharing pane in System Preferences will show "Web sharing starting up", and just stay there.

Logged out and back in and it was the same.

Mine's done that for ages. Never did work out how to fix it

For me it's not to do with this update though

[spiky_dog]

people with broken web sharing:

go to the terminal. type in this:

apachectl configtest

and then report what it says. chances are there's an error on some line, and editing /etc/httpd/httpd.conf appropriately (say commenting out the line with # at the beginning) will fix the startup problem.

[piracy]

From: [email protected]
Subject: Security Update naming
Date: January 25, 2005 2:10:20 PM CST
To: [email protected]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

The naming scheme of Apple Security Updates has changed from a date
format (e.g., "Security Update 2004-12-02") to a format based on the
year and a sequence number: Security Update YYYY-NNN. For example,
the update released today is named "Security Update 2005-001", the
next would be "Security Update 2005-002" and so on.

The Security Update web site at
http://docs.info.apple.com/article.html?artnum=61798 has been
improved to provide a list of the releases in a more user-friendly
format. The details for each release will be contained in its own
separate page to improve clarity and readability.

Best regards,

Apple Product Security team
http://www.apple.com/support/security/

[Disgruntled Head of C-3PO]

Originally posted by placebo1969:
33 days for me.

If you had a girlfriend, she would dump you.

[andretan]

Originally posted by spiky_dog:
people with broken web sharing:

go to the terminal. type in this:

apachectl configtest

and then report what it says. chances are there's an error on some line, and editing /etc/httpd/httpd.conf appropriately (say commenting out the line with # at the beginning) will fix the startup problem.

Code:
$ apachectl configtest
Syntax error on line 238 of /etc/httpd/httpd.conf:
API module structure `php4_module' in file /usr/libexec/httpd/libphp4.so
 is garbled - perhaps this is not an Apache module DSO?

I looked up the macosxhints forums, and found this, so I sudo chmod 755 libphp4.so but it doesn't work.

[Amorya]

amorya$ apachectl configtest
Processing config directory: /private/etc/httpd/users/*.conf
Processing config file: /private/etc/httpd/users/temp.conf
[Wed Jan 26 13:09:57 2005] [warn] module mod_php4.c is already added, skipping
[Wed Jan 26 13:09:58 2005] [warn] module mod_WebObjects.c is already added, skipping
Syntax OK

[Dougmc]

There's an interesting caveat with this security update after running Disk Utility to repair permissions. On two different machines that I've updated and run Disck Utility I'm now getting a message "We are using a special uid for the file or directory ./private/var/at/jobs. New uid is 1" The other line is exactly the same, however, it's referencing ./private/var/at/spool.

I found that interesting. Mostly because I have no idea what that means.

If while using these machines I start smelling smoke, I'll report back.

[Theodour]

Originally posted by andretan:

Code:
$ apachectl configtest
Syntax error on line 238 of /etc/httpd/httpd.conf:
API module structure `php4_module' in file /usr/libexec/httpd/libphp4.so
 is garbled - perhaps this is not an Apache module DSO?

Do you have a custom PHP installation?

I have Marc Liyanage's binaries, and wondered if this security update -- since one of the fixes is Apple's included PHP -- will clash with this.

[andretan]

Originally posted by Theodour:
Do you have a custom PHP installation?

I have Marc Liyanage's binaries, and wondered if this security update -- since one of the fixes is Apple's included PHP -- will clash with this.

I'm using the same one as well.

[piracy]

Originally posted by andretan:
I'm using the same one as well.

*Sigh*

NO, this update will not "clash" with Marc Liyanage's PHP. Marc Liyanage's PHP installs itself in /usr/local/php. Apple's does not. Need anything more be said?

This update will update *Apple's* PHP install. Marc Liyanage's will still be in /usr/local/php, untouched. Marc Liyanage's install also modifies your /etc/httpd/httpd.conf to point it at the PHP in /usr/local/php, so if you ever want to change back to Apple's, those changes need to be reverted (the original file is saved at /etc/httpd/httpd.conf-entropy-backupXXXX.

Since Apple has now moved to PHP 4.3.10, and it's a hell of a lot easier to let Apple's software updates update your software, I'd switch back to Apple's PHP unless there is a specific reason to still use Marc Liyanage's version (such as something he's compiled into it, etc...)

[andretan]

Originally posted by piracy:
*Sigh*

NO, this update will not "clash" with Marc Liyanage's PHP. Marc Liyanage's PHP installs itself in /usr/local/php. Apple's does not. Need anything more be said?

Any idea how to get my Personal Web Sharing working again then?

[cpt kangarooski]

Originally posted by Ganesha:
Clearly, Apple expects more then 100 security updates this year...

No, if that were the case, then the old one would've been fine. What this means is that Apple expects more than 365 updates this year! That doesn't sound good.

[piracy]

Originally posted by andretan:
Any idea how to get my Personal Web Sharing working again then?

Yes. Find out why it's not starting.

Learn enough about your configuration file to fix it.

But it has *nothing* to do with the third party PHP (IF you didn't break anything in your configuration file yourself).

I hope you people know that Marc Liyanage's install modifies httpd.conf, comments out Apple's php lines, and adds some lines for itself. Marc Liyanage's stuff is still in the same place, and Apple's stuff is still in the same place it lives after an update. Just look at your httpd.conf, and check to ensure that the

#LoadModule php4_module /usr/libexec/httpd/libphp4.so

line (or something like it) is still commented out, and that you have

LoadModule php4_module /usr/local/php/libphp4.so

and

AddModule mod_php4.c

lines somewhere. Is your apache failure perhaps *related* to something that was done when you installed Marc Liyanage's PHP? Probably. Might it also have been a situation where you had no clue what you were doing? Probably. But when Marc Liyanage's PHP is properly installed, it DOES NOT clash with Apple's PHP, and DOES NOT clash with Security Update 2005-001. Marc Liyanage's PHP is completely segregated from the OSes PHP, and there is really only one line in httpd.conf that makes this delineation.

[Phil Sherry]

piracy, can you fix the scroll wheel on my mouse, please? i think Security Update 2005-001 bwoke it

then there's a lightbulb which blew at the same time, so can you fix that too?

[andretan]

Originally posted by piracy:
Yes. Find out why it's not starting.

Learn enough about your configuration file to fix it.

But it has *nothing* to do with the third party PHP (IF you didn't break anything in your configuration file yourself).

Sorry.

Anyway, I commented out the "offending" lines in /etc/httpd/httpd.conf and /usr/local/php/httpd.conf.php and now Apache and my Personal Web Sharing is fixed now.

[Theodour]

Originally posted by piracy:
Might it also have been a situation where you had no clue what you were doing? Probably. But when Marc Liyanage's PHP is properly installed, it DOES NOT clash with Apple's PHP, and DOES NOT clash with Security Update 2005-001. Marc Liyanage's PHP is completely segregated from the OSes PHP, and there is really only one line in httpd.conf that makes this delineation.

Oh, I'm sorry. I didn't realize these were the abuse forums. I guess the MacOS forums are down the hall ...

[hcorf]

it wont seem to let me get it either.

The patch doesnt appear in software update, having managed to dl a copy off the apple site, it said my computer didnt meet the requirements to install it.

I have a:

iBook G4 800MHz
OS 10.3.7
All other updates
Safari is the standard version.

The whole thing is behaving strangely, when i put iWork on the machine, pages crashes before it has started, but keynote 2.0 works fine.

Now the iPod 3G on the emac stops taking on songs after it reaches about 1500, then it hangs itunes. The iPod is fine apparently.

Makes me think that there is a mac virus out or something.

Anyone else seen these problems>?

Will a clean OS install probably clear some of these issues up?

[piracy]

Originally posted by Theodour:
Oh, I'm sorry. I didn't realize these were the abuse forums. I guess the MacOS forums are down the hall ...

Oh, I'm sorry, I didn't realize that people come and whine in these forums all the time, blaming things they broke themselves on Apple's updates when in fact it was their own ignorance that caused the problem! My mistake!

I also didn't realize that I'm the only one in this thread so far that has actually given accurate information on the topic at hand! My deepest apologies!

*Cough*

[piracy]

Originally posted by hcorf:
it wont seem to let me get it either.

The patch doesnt appear in software update, having managed to dl a copy off the apple site, it said my computer didnt meet the requirements to install it.

I have a:

iBook G4 800MHz
OS 10.3.7
All other updates
Safari is the standard version.

The whole thing is behaving strangely, when i put iWork on the machine, pages crashes before it has started, but keynote 2.0 works fine.

Now the iPod 3G on the emac stops taking on songs after it reaches about 1500, then it hangs itunes. The iPod is fine apparently.

Makes me think that there is a mac virus out or something.

Anyone else seen these problems>?

Will a clean OS install probably clear some of these issues up?

Argggh.

No, there is not a "Mac virus", for f*ck's sake, just because a single update won't install on your computer.

I'm going to say this very carefully, so as not to offend anyone:

Something is wrong with YOUR particular installation. It may or may not be through any fault of your own. You do not have a "virus". But if you're starting to have odd problems, something is wrong with your install. This could be anything from corrupted local prerferences, global preferences, filesystem issues, a partial/incomplete previous installation of an update or other OS component, etc. First order of business would be to boot off your OS X CD and do normal housekeeping tasks, like checking the filesystem and repairing permissions. If problems were found, and sucessully fixed, try installing the update again. If no problems were found, you have a more subtle problem. Next steps are things like Archive and Install (covered at length elsewhere in these forums). But if you're starting to have odd problems, you've got something going on, and it's not a "virus".

[Theodour]

Originally posted by piracy:
Oh, I'm sorry, I didn't realize that people come and whine in these forums all the time, blaming things they broke themselves on Apple's updates when in fact it was their own ignorance that caused the problem! My mistake!

I also didn't realize that I'm the only one in this thread so far that has actually given accurate information on the topic at hand! My deepest apologies!

*Cough*

My humblest apologies, oh great one!

[placebo1969]

Originally posted by Disgruntled Head of C-3PO:
If you had a girlfriend, she would dump you.

Glad I'm married then.

[Phil Sherry]

Originally posted by piracy:
I also didn't realize that I'm the only one in this thread so far that has actually given accurate information on the topic at hand! My deepest apologies!

*Cough*

fix my bloody lightbulb then, smartarse.

[piracy]

Originally posted by Phil Sherry:
fix my bloody lightbulb then, smartarse.

[Dale Sorel]

Originally posted by akuma-x:
Same goes for me. DP 1.3 as well and not showing in SW update.

Ditto�

[Person Man]

Originally posted by Dale Sorel:
Ditto�

Not to be an a**hole or anything, but shouldn't that tell you something about Safari 1.3DP?

Like how you really shouldn't be running in in a production environment? (I'm not getting into the developer/non-developer argument).

[Ganesha]

Doesn't the 1.3 DP license state its not forward compatible to the official release?

[Person Man]

Originally posted by Ganesha:
Doesn't the 1.3 DP license state its not forward compatible to the official release?

Bingo! In fact, most prerelease software is not guaranteed to be forward compatible. That's why you shouldn't use it on a day-to-day basis.

Apple certainly won't provide you with technical support on these problems if they know you're running Safari 1.3 DP (even if you're a developer under NDA). Their response will be something along the lines of, try it on a system that DOESN'T have 1.3 DP on it.

[Disgruntled Head of C-3PO]

Originally posted by placebo1969:
Glad I'm married then.

Don't be, now she gets 50%.

[alphasubzero949]

Originally posted by Person Man:
Bingo! In fact, most prerelease software is not guaranteed to be forward compatible. That's why you shouldn't use it on a day-to-day basis.

Apple certainly won't provide you with technical support on these problems if they know you're running Safari 1.3 DP (even if you're a developer under NDA). Their response will be something along the lines of, try it on a system that DOESN'T have 1.3 DP on it.

Funny, if you're a seed tester you are expected to use the pre-release software on a day-to-day basis (of course, at your own risk if running on your main workhorse).

[Phil Sherry]

Originally posted by alphasubzero949:
Funny, if you're a seed tester you are expected to use the pre-release software on a day-to-day basis (of course, at your own risk if running on your main workhorse).

exactly. how else are testers supposed to test things? duh.

[Webscreamer]

Yes, but iof you're a seed tester, then don't b*tch about it here. Report it to Apple and shut up.

[Disgruntled Head of C-3PO]

Strange, at work we are registered developers and at one point Safari 1.3 was installed but trashed long ago. All other software updates show up fine so I am wondering why this one doesn't?

Does anyone know what file needs to be trashed to get it to work?

[Person Man]

Originally posted by alphasubzero949:
Funny, if you're a seed tester you are expected to use the pre-release software on a day-to-day basis (of course, at your own risk if running on your main workhorse).

Yes, you are expected to run it on a day-to-day basis... ON YOUR TEST SYSTEM (OR TEST PARTITION). To use prerelease software as your ONLY copy of the system is irresponsible. (Most developers know this anyway, and if they don't do it that way they should be willing to accept that risk on their own). This is what I'm getting at.

Still (without pointing fingers at anyone specific here), many people on these forums who tend to say things like, "I have (or had and then deleted) DP 1.3 (or whatever prerelease software) on my system and now update x doesn't work or won't install," generally aren't developers and generally aren't intended to have it.

If you have it and aren't intended to have it, then don't whine about it breaking your system (on a public forum such as this). Suck it up, and reinstall the operating system from scratch. If you are going to run prerelease software anyways (and are not a developer, because apple won't accept bug reports on prerelease software from people who haven't signed an NDA), then be responsible and DON'T INSTALL THE SOFTWARE ON YOUR DAY-TO-DAY SYSTEM. Use it on a copy of your main install. If not, AMF YOYO (Adios my friend, you're on your own).

[piracy]

Originally posted by Disgruntled Head of C-3PO:
Strange, at work we are registered developers and at one point Safari 1.3 was installed but trashed long ago. All other software updates show up fine so I am wondering why this one doesn't?

Does anyone know what file needs to be trashed to get it to work?

Probably the receipt for it in /Library/Receipts, not to mention insuring that there is a properly functioning, current, non-beta version of Safari on the system as well.

[Severed Hand of Skywalker]

Originally posted by piracy:
Probably the receipt for it in /Library/Receipts, not to mention insuring that there is a properly functioning, current, non-beta version of Safari on the system as well.

I trashed the receipt and copied a sarafi from another computer over to be sure. Still a no go.

[alphasubzero949]

Originally posted by Webscreamer:
Yes, but iof you're a seed tester, then don't b*tch about it here. Report it to Apple and shut up.

No one was bitching about seed testing here.