Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
SC68Cal said:
I wonder what the update to OpenSSH was. I would update just for that fix.

OpenSSH

CVE-ID: CVE-2006-0393

Available for: Mac OS X v10.4.7, Mac OS X Server v10.4.7

Impact: When remote login is enabled, remote attackers may cause a denial of service or determine whether an account exists

Description: Attempting to log in to an OpenSSH server ("Remote Login") using a nonexistent account causes the authentication process to hang. An attacker can exploit this behavior to detect the existence of a particular account. A large number of such attempts may lead to a denial of service. This update addresses the issue by properly handling attempted logins by nonexistent users. This issue does not affect systems prior to Mac OS X v10.4. Credit to Rob Middleton of the Centenary Institute (Sydney, Australia) for reporting this issue.
 
Have to agree

shawnce said:
Actually I think his point was that running the repair permissions tool is more vodo then any real help (in most current situations)... and that is why Apple doesn't recommend it as part of system maintenance.

review among others (because I don't care to list the reasons)

(from the above link)

Actually, I don't think I'll ever repair the premissions on my PB. The only times I've EVER had problems with my (or my moms) Mac is when I did that. Also, note that the disk repair function in the utility will mess up your HD too. I really have no idea why those are even options - they just make things worse... In my experience anyway.
 
bigmc6000 said:
Also, note that the disk repair function in the utility will mess up your HD too.
If you ran disk repair and it "messed up your HD" then either the file system on your hard drive was in a very degraded state (you may have not run across it yet in your normal usage) and/or the HD itself was failing (surface defect, head failure, etc.).

I know of only one bug in disk repair that could cause problems (trying to recall the specifics...).

In other words it is far more likely that disk repair exposes hardware failures or highly damaged file systems when it runs then introduce failures itself.
 
SC68Cal said:
I wonder what the update to OpenSSH was. I would update just for that fix.

Impact: When remote login is enabled, remote attackers may cause a denial of service or determine whether an account exists

Description: Attempting to log in to an OpenSSH server ("Remote Login") using a nonexistent account causes the authentication process to hang. An attacker can exploit this behavior to detect the existence of a particular account. A large number of such attempts may lead to a denial of service. This update addresses the issue by properly handling attempted logins by nonexistent users. This issue does not affect systems prior to Mac OS X v10.4. Credit to Rob Middleton of the Centenary Institute (Sydney, Australia) for reporting this issue.
 
shawnce said:
If you ran disk repair and it "messed up your HD" then either the file system on your hard drive was in a very degraded state (you may have not run across it yet in your normal usage) and/or the HD itself was failing (surface defect, head failure, etc.).

I know of only one bug in disk repair that could cause problems (trying to recall the specifics...).

In other words it is far more likely that disk repair exposes hardware failures or highly damaged file systems when it runs then introduce failures itself.

Well all I can tell you is that before I ran it it was working fine - after I ran it my HD died and not even the data recovery people could rescue my data. So it obviously did something considering data recovery couldn't even get the volume to mount...
 
spicyapple said:
Is it a good idea to install this update at the same time as my new 2GB RAM installation? I hate to ruin my uptime, by rebooting twice.

Direct link to the article.

http://docs.info.apple.com/article.html?artnum=304063


Are you kidding? You're worried about rebooting twice? Dude come on. You're telling us that you think uptime is more important than a security update, or having to reboot twice? God forbid you have to restart 3 times.
 
Updates = New Products?

Just curious: anyone know if there is any connection (real or imagined) of Apple releasing updates (be it Security or OS) that foreshadow new product(s)?

I do seem to recall this being the case, at times, in the past.

Guess I'm just Jonesin' for that full fledged video iPod and/or mobile phone dealio.

Move along...
 
bigmc6000 said:
Well all I can tell you is that before I ran it it was working fine - after I ran it my HD died and not even the data recovery people could rescue my data. So it obviously did something considering data recovery couldn't even get the volume to mount...

...it exercised you disk such that it failed from a preexisting condition (if recovery folks couldn't get anything back then either they sucked or the HD platter was severely damaged).

It is unlikely it was the cause of the problem, it only exposed it.
 
lazyrighteye said:
Just curious: anyone know if there is any connection (real or imagined) of Apple releasing updates (be it Security or OS) that foreshadow new product(s)?
Operating system point updates are often required in order for new product support (provides a means to distribute new platform experts in the kernel).

Security updates will likely never be used for that.
 
Stridder44 said:
Are you kidding? You're worried about rebooting twice? Dude come on. You're telling us that you think uptime is more important than a security update, or having to reboot twice? God forbid you have to restart 3 times.

I'm pretty sure he was being sarcastic
 
jeff303 said:
I'm pretty sure he was being sarcastic
Too bad you couldn't detect my gender. ;) And no I was not being sarcastic, but it came off as such. I need to improve my writing skills. :eek: :eek:
 
still caused it to fail

shawnce said:
...it exercised you disk such that it failed from a preexisting condition (if recovery folks couldn't get anything back then either they sucked or the HD platter was severely damaged).

It is unlikely it was the cause of the problem, it only exposed it.


I'm sure if I ran my car at red line the whole time that it would fail - does that mean there's a problem with my car?
 
Weird thing happened when it wouldn't restart or shutdown until I relaunched the Finder after installing the update. The general awesomeness of my computer, however, seems unaffected.
 
Not the smoothest update for me.

15in AI didn't reboot properly. On reboot it was stuck in the black for a few minutes. I waited and waited, but nothing happened. Pressed the start button and tried again, but same thing happened. After three tries I pulled the plug, popped out the battery and unplugged my usb mouse. It then booted unusually fast and everything seems great.
 
bigmc6000 said:
I'm sure if I ran my car at red line the whole time that it would fail - does that mean there's a problem with my car?
Bad analogy... but if you want to use analogies...

It is like running your car's engine with to little oil and only taking it for limited trips and then one day taking it on a long trip only to have the engine seize on you. The long trip wasn't the problem the preexisting lack of oil was.
 
actually

shawnce said:
Bad analogy... but if you want to use analogies...

It is like running your car's engine with to little oil and only taking it for limited trips and then one day taking it on a long trip only to have the engine seize on you. The long trip wasn't the problem the preexisting lack of oil was.


My point is that I didn't need to EVER take it on long trip, disk utility made it do something that I never do. Regardless of it there was a pre-existing condition it made my HD perform irregullarly and thus exposed an otherwise unknown error.

To use a better analogy, it took my car that I will never take above 90 to about 110 and ran it there for a while. Mechanically speaking you are going to see a lot more stress and maintenance issues running at 110 than you are at 90...

Your turn ;)
 
arkhanjel said:
i would probably do the ram first and reboot, this way if you have any problems with the ram you'll be sure its the ram and not the security update.

good call.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.