Apple's choice of algorithm defrags files as it encounters them. If you are upgrading a drive, it may have a lot of fragmented files that need to be defragmented. So initially, it will be very slow.
Once the code has been exercised for a while, yeah, it'll be much faster.
Similiar situation here. There were a few shows I tried to keep track of (Enterprise, Smallville), but when one of them moved timeslots (Smallville) I lost it for a full year before bothering to look up where it had moved to...
I hope for their sake it does. They've spent a lot of time on their product, and I'm not sure they've even reached the closed source PROFIT step yet...
Ouch. That's a good point. I never even considered investigating @stake's past advisories. From the link you posted, it looks like they have a long history of being a grey hat.
I doubt they told @stake they weren't going to fix them. I doubt they told @stake they were going to fix them. In fact, I doubt they even told @stake that the flaws didn't affect Panther... @stake probably found that out and told Apple.
Apple doesn't talk details in unreleased products.
There's a couple reasons we're seeing this press release:
@Stake acted unethically and went to the press early to get their name seen.
Ethical reporting of security flaws involves going to the company and giving them time to get a patch out. Then, one or both companies announces the flaw... and includes details of the patch. @stake jumped the gun and did not use white hat practices.
ZDNet engaged in wild speculation with typical bias.
ZDNet decided that @stake's announcement meant Apple wasn't going to fix the problem, and decided to give it a spin. As they actually indicated in their story, they did not wait for a comment from Apple before rushing the thing to press.
Hopefully, @stake will do better next time. But I doubt their role in this will be examined very carefully.
I know ZDNet will do the same thing next time. They smell any blood around Apple, they're the first to paint a picture of mass destruction, mayhem and cats and dogs sleeping together.
If @stake hadn't jumped the gun, we'd have seen a press release some time next week on Apple's site about the security flaws, with a fix, and with credit to @stake for finding them. How do I know this? Because it's what they've done every other time, including with 10.1 after 10.2 was released!
I wasn't thinking of this earlier, but your comment reminded me of when Dan Quayle went head-to-head with Murphy Brown.
It resulted in some of the funniest television I'd seen. One of the best was Frank's line: "C'mon Murph. It's DAN QUAYLE! Next week, he'll get his head stuck in a golf bag..."
Murphy Brown's writers seemed to win the battle pretty overwhelmingly.
The source code is posted to that thread; the only conditions are (1) 3 minutes after the system time starts (i.e. avoid doing so when booting up), (2) less than 20 MB of size, (3) file isn't already opened.
The only negative consequence is a possible speed hit, though. There's no danger.
I'm pretty impressed by this. Sure, it's been done before. Sure, there are more elaborate methods. But this is just a simple little lump of code that'll defragment the worst files most of the time.
It's a matter of taste I suppose. I prefer to type my content and apply formatting after. I'd rather type an apostrophe than , I prefer shift enter to , I like being able to apply strong with a single keystroke. I like not having to check the size of gifs.
There are a number of nice things about Dreamweaver.
But if we were working together, I would happily agree to different tools as long as we were both validating and using the same pretty print settings.
That's funny. When I first saw the subject, I thought you were going to say that making an assumption that Apple is not going to fix these "security problems" after three days was unfair. I would have agreed.
Slashdot Mirror
Apple's choice of algorithm defrags files as it encounters them. If you are upgrading a drive, it may have a lot of fragmented files that need to be defragmented. So initially, it will be very slow.
Once the code has been exercised for a while, yeah, it'll be much faster.
It's also what a Microsoft system extension bundled with Mac Office 6. What was that, 7.6 era?
Similiar situation here. There were a few shows I tried to keep track of (Enterprise, Smallville), but when one of them moved timeslots (Smallville) I lost it for a full year before bothering to look up where it had moved to...
Right. It's the pay damages thing I'm referring to.
Also, you're just speculating on why it is fixed in Panther. For that matter, so is @stake if you've got this from them.
I hope for their sake it does. They've spent a lot of time on their product, and I'm not sure they've even reached the closed source PROFIT step yet...
But they didn't wait for the Jaguar patch.
Although Apple doesn't give direct credit, don't they usuall provide a link to the advisory or somesuch?
That code is almost always found and exploited around within a few weeks.
I'd like to think online game developers are getting smarter about this...
Yeah, same here.
Oh well. At least I'm getting my daily slime intake without it directly affecting me.
Ouch. That's a good point. I never even considered investigating @stake's past advisories. From the link you posted, it looks like they have a long history of being a grey hat.
So much for any hope they'll do better next time.
Thanks for the information!
RTFA. This is discussing whether or not security flaws in 10.2 (released a year ago) will be fixed, not 10.3. The flaws don't exist in 10.3.
I doubt they told @stake they weren't going to fix them. I doubt they told @stake they were going to fix them. In fact, I doubt they even told @stake that the flaws didn't affect Panther... @stake probably found that out and told Apple.
Apple doesn't talk details in unreleased products.
There's a couple reasons we're seeing this press release:
Ethical reporting of security flaws involves going to the company and giving them time to get a patch out. Then, one or both companies announces the flaw... and includes details of the patch. @stake jumped the gun and did not use white hat practices.
ZDNet decided that @stake's announcement meant Apple wasn't going to fix the problem, and decided to give it a spin. As they actually indicated in their story, they did not wait for a comment from Apple before rushing the thing to press.
Hopefully, @stake will do better next time. But I doubt their role in this will be examined very carefully.
I know ZDNet will do the same thing next time. They smell any blood around Apple, they're the first to paint a picture of mass destruction, mayhem and cats and dogs sleeping together.
If @stake hadn't jumped the gun, we'd have seen a press release some time next week on Apple's site about the security flaws, with a fix, and with credit to @stake for finding them. How do I know this? Because it's what they've done every other time, including with 10.1 after 10.2 was released!
I wasn't thinking of this earlier, but your comment reminded me of when Dan Quayle went head-to-head with Murphy Brown.
It resulted in some of the funniest television I'd seen. One of the best was Frank's line: "C'mon Murph. It's DAN QUAYLE! Next week, he'll get his head stuck in a golf bag..."
Murphy Brown's writers seemed to win the battle pretty overwhelmingly.
Riiight. Listen, there's no black magic in that defragmentation code. Look elsewhere for problems.
Definitely. I'm embarassed that it took me so long to recognize it. :)
I'm a bit less sure of this one, but I think the file must be severely fragmented (i.e. into 8 pieces).
On Mac OS X specifically, or as part of the protocol? I have to admit I haven't heard of DAV over https.
If it's Panther in particular and you have a server in mind, I'll be happy to check.
Oh, neat. Where's the option? Or is it always on?
The source code is posted to that thread; the only conditions are (1) 3 minutes after the system time starts (i.e. avoid doing so when booting up), (2) less than 20 MB of size, (3) file isn't already opened.
The only negative consequence is a possible speed hit, though. There's no danger.
I'm pretty impressed by this. Sure, it's been done before. Sure, there are more elaborate methods. But this is just a simple little lump of code that'll defragment the worst files most of the time.
I'm not even sure it'll ship then. How many times has Microsoft announced vaporware to kill off a competitor, then not followed through?
Funny. I could see any store that tried it in this area losing all their shoppers instantly... :)
Excuse the poor wrapping. Seems to be a Web Pro problem.
It's a matter of taste I suppose. I prefer to type my content and apply formatting after. I'd rather type an apostrophe than , I prefer shift enter to
, I like being able to apply strong with a single keystroke. I like not having to check the size of gifs.
There are a number of nice things about Dreamweaver.
But if we were working together, I would happily agree to different tools as long as we were both validating and using the same pretty print settings.
That's funny. When I first saw the subject, I thought you were going to say that making an assumption that Apple is not going to fix these "security problems" after three days was unfair. I would have agreed.