There's no reason not to use anti-virus on Macs. Expect that not running them will make you more secure. (Have you seen all the recent exploits for common archive scanning libraries lately?)
If your Mac runs MS-Office software... you are vulnerable to some Macro viruses. Good news then. Office 2008 for Mac doesn't support VBA or VSTO, so those macro viruses won't run. Office 2004's support was piss poor, so only some of the older macro viruses would run.
Leave it to MS to innovate the cross platform virus...
I still think it's because they oversold their network capacity and don't want to spend any new money on upgrading their infrastructure to match the capacity they advertise. The fix to this is to implement network filtering that prevents customer from using the bandwidth AT&T has sold them.
I don't understand how this could be for Win32 compatibility. Just being able to load the PE executable format does not mean you can actually use anything in PE executables. It's required before anything else is done, sure, but it doesn't mean compatibility. Especially since you'd still need PE files to load. And then you'd need shims. Lots of shims. Just look at WINE, loading PEs doesn't seem to be a huge part of it. It could just be necessary support so a third party can finish the job (kind of like all the VPC-specific stuff they had for PowerPC Mac OS X).
I'd normally say Apple would never finish the rest of this. But they switched to Intel.
Re:Great show, decent movie
on
Futurama Returns!
·
· Score: 3, Informative
I'll never watch "Jurassic Bark" again. Saddest. Ending. EVER.
Eh, spoiler, but the movie makes it a lot less sad. Perhaps it's for people that couldn't watch the episode without crying.
The root cause (the manufacturing defects) are thankfully limited to high-capacity cutting edge cells.
And since electric vehicles don't have the same weight/power/small size requirements as a cell phone battery, their cells don't have to be nearly as dense or "high-capacity".
I hope that there's a way to turn this stuff off. Huh? Mac OS X has always has prebinding. This made a lot of system libraries load at semi-random addresses (except for libSystem). In 10.5, they make it intentional and add libSystem into the mix.
There's currently a massive bug that accidently implements ASLR on PowerPCs in 10.4.x, but it's per process and completely screws with the shared memory benefits. Of course, 10.5 doesn't have this issue.
A user can unplug a device at any time, even in the middle of a catalog write. It only seems prudent to checksum the data to make sure you don't have a corrupt file. Or the user could be using a piece of third party software that writes bad data to the iPod db, causing the iPod to crash when it tries to access said bad data. An integrity checksum would help prevent this as well (assuming said bad software doesn't include a checksum for a bad db write...)
I, for one, hate it when my iPod crashes and spontaneously reboots while I'm totally in the groove.
but as for US VATs, what are normal VAT rates? wikipedia suggest between 0-9.75%, typically 8.5% We do not have VAT in the US. We have a sales tax, which is different. Merchants selling to other merchants items (or components like hard drives for inclusion in a computer box the second merchant sells) for resale are not subjected to sales tax. Sales tax isn't applied until it gets to the consumer. VAT is applied at each exchange.
which still ends up being less then half the VAT of what we pay here, so we still get screwed Don't blame Sony or anyone else on that, blame it on the policies of the silly countries you live in. This is why the VAT needs to be removed before you do any such compare. It removes some of the silliness of the countries. (But doesn't remove duty fees, shipping fees, custom fees, or other fees a company might have to pay to get the product into the country first...)
Sony: if you add PVR capabilities to your US models, I will buy the PS3. That's a flat-out lie and you know it.
Even if Sony did add this to the US models, you'd have some other silly reason for not purchasing the PS3. You have no intention of buying a PS3, no matter what Sony does.
We europeans pay around 700-900 USD for the PS3 Before you start complaining about the US price vs the European prices, always remember to remove the VAT from the European prices. Why can't Europeans bother to remember such a simple thing? List prices in the US do not include tax.
Apple didn't disable Bonjour, they disabled one of the components of Bonjour. That's not like disabling loading, it's like refusing to load certain files. Actually, it's not even really a component of Bonjour. It just happened to be a service in the mDNSResponder process, which also does Bonjour. Non-Mac OS X mDNSResponder clients do not have this recently disabled UPnP service.
I call bullshit. You are saying it's not possible to implement UPnP without being vulnerable to a buffer overflow that may lead to remote code execution? Because that's one of the (at least) two issues at hand. Nice try on passing the responsibility for this bug to the spec writers (mentioning Microsoft seems to help too), Uhm, UPnP is a microsoft created and controlled spec, this is why I specifically mentioned Microsoft. Some people think it's not microsoft related because Microsoft hides their name from being easily found on the site (they do the same thing with the Zune). But, do a whois on upnp.org or look at many of the UPnP documents and you will see Microsoft's name plastered all over.
Can you show me an implementation of UPnP that hasn't had bugs? According to wikipedia security is a problem with the spec itself. It's getting so bad that some major router manufacturers are disabling the routing of UPnP packets by default on their non-consumer (and a few consumer) networking appliances.
And my list was more of a dig at OOXML rather than being security related.
I'm not opposed to temporarily disabling functionality to fix something potentially disastorous. There are three options when implementing UPnP:
1. Implement it to Microsoft's spec. 2. Implement it correctly (by choosing a direction in places the spec contradicts itself or real implementations). 3. Implement it securely.
Choose only one.
I do not think it is possible to implement UPnP securely and have it based on the spec. Also, the specific code they removed existed only for legacy NAT traversals and may not even be needed any more.
I've heard people saying that HFS+ can't really handle hard links properly pre Leopard. Citation needed. Where did you here that? (And don't link to some crazy nutjob idiot cracker that likes to rant about stuff he doesn't understand).
Do hard links work on HFS+? Yes. So what's it matter how they are implemented?
In this case, Mac OS X 10.5 'Leopard', only when running on Intel Macs, not PPC Macs or any other box was found to meet the UNIX 03 specification. And this is what confuses me. There is no 10.5 for ICBMs and 10.5 for PPC Macs. It's all one, single, unified version with one SKU. It's odd they explicitly mention ICBMs.
If someone has missed ReBoot and has no idea what's going on, see this happy video it is quite informative (or search the internets for "Daemon Rising", after all, daemon is the word...)
For example, when placed under a heat lamp, it could easily take 5 seconds before "pain" was registered, it doesn't mean that the heat wasn't hurting you 5 seconds ago, it means it takes a while for the sub-dermal layers to heat up. So it's entirely possible that prolonged exposure to the radiation is causing them problems. Except these people often claim immediate relief when there is no cell mast around. I'm not saying it's completely psychological (like all sleeping pills have a risk of psychological dependancy), This study suggests they need to rule out cell masts as the cause and do more to study the baseline cause of their ills. I imagine there is pornography involved.
Can someone confirm if Safari is actually vulnerable, or if it is just that the author thinks that "all open source browsers are just the same"? It only works if form autofill is turned on for usernames and passwords. I have all of autofill turned off (because it's a huge privacy risk in my mind, for accidental forms when I am not paying attention) and the tests don't work. Form autofill for usernames and passwords can be disabled separately from other autofill in safari.
Slashdot Mirror
Office 2004's support was piss poor, so only some of the older macro viruses would run.
Leave it to MS to innovate the cross platform virus...
I still think it's because they oversold their network capacity and don't want to spend any new money on upgrading their infrastructure to match the capacity they advertise. The fix to this is to implement network filtering that prevents customer from using the bandwidth AT&T has sold them.
Yup. The solution to Apple being accused of being a monopolist is to have them license DRM from a convicted monopolist. Seems simple enough.
If Best Buy copies the porn off of HDs of PCs that go in for repair, just imagine what Apple does with your sensitive data.
Uhm, mine do.
I don't understand how this could be for Win32 compatibility. Just being able to load the PE executable format does not mean you can actually use anything in PE executables. It's required before anything else is done, sure, but it doesn't mean compatibility. Especially since you'd still need PE files to load. And then you'd need shims. Lots of shims. Just look at WINE, loading PEs doesn't seem to be a huge part of it. It could just be necessary support so a third party can finish the job (kind of like all the VPC-specific stuff they had for PowerPC Mac OS X).
I'd normally say Apple would never finish the rest of this. But they switched to Intel.
Eh, spoiler, but the movie makes it a lot less sad. Perhaps it's for people that couldn't watch the episode without crying.
Indeed. They're so quick to complain about a problem and usually unwilling to do anything to try to solve their problem.
And since electric vehicles don't have the same weight/power/small size requirements as a cell phone battery, their cells don't have to be nearly as dense or "high-capacity".
At least a year come November 1st.
You meant why doesn't APE do this?
SInt32 vers = 0;
err = Gestalt(gestaltSystemVersion, &vers);
if (err or (vers >= 0x1050))
{
return paramErr;
}
(which I just took from the APE source code).
There's currently a massive bug that accidently implements ASLR on PowerPCs in 10.4.x, but it's per process and completely screws with the shared memory benefits. Of course, 10.5 doesn't have this issue.
I, for one, hate it when my iPod crashes and spontaneously reboots while I'm totally in the groove.
Even if Sony did add this to the US models, you'd have some other silly reason for not purchasing the PS3. You have no intention of buying a PS3, no matter what Sony does.
Can you show me an implementation of UPnP that hasn't had bugs? According to wikipedia security is a problem with the spec itself. It's getting so bad that some major router manufacturers are disabling the routing of UPnP packets by default on their non-consumer (and a few consumer) networking appliances.
And my list was more of a dig at OOXML rather than being security related.
1. Implement it to Microsoft's spec.
2. Implement it correctly (by choosing a direction in places the spec contradicts itself or real implementations).
3. Implement it securely.
Choose only one.
I do not think it is possible to implement UPnP securely and have it based on the spec. Also, the specific code they removed existed only for legacy NAT traversals and may not even be needed any more.
Do hard links work on HFS+? Yes. So what's it matter how they are implemented?
If someone has missed ReBoot and has no idea what's going on, see this happy video it is quite informative (or search the internets for "Daemon Rising", after all, daemon is the word...)