The advantage ARM has over x86 is that is much more efficient when it comes to power requirements. This comes at a trade off in regards to speed. When Apple went Intel they had at least equivalent processors, and Rosetta often was quite a bit of a dog.

Running an x86 emulator on ARM doesn't sound like a very good idea at all. Binaries made for very fast processors running emulated on a slow processor would be a bad user experience, and there's quite a lot of evidence that in the mobile space the average person values user experience over everything else.

Uhm, because it's a different CPU instruction set?

Is there some joke I'm missing here?

That's a very narrow definition of denial of service attacks, and not usually used in security circles. The class of denials of service attacks is usually assumed to include every attack that, well, denies you the opportunity to use a service. That would include blowing up a transformer that is instrumental to providing power to the service that you're trying to consume, or setting the server room on fire and burning down the servers, which may well contain the only copy of the service they're hosting if the admins are particularly stupid.

Denial of service attacks don't necessarily temporarily deny access to the service, it can absolutely be permanent.

> The only thing I can think of is that the neighbor starts finding this suspicious stuff about them online. Calls the cops (or the cops call him) and then start pulling records off the wireless router.. Like you said the MAC address should be recorded. They may have been able to subpoena (or not, thanks patriot act) the local ISP's and start pulling mac addresses from the neighborhood.

That isn't how networks work.

MAC addresses are used on layer 2 broadcast domains. For an ISP to have seen the MAC address of his wireless card he would have to use that wireless card to directly connect to the ISP. That is fairly unlikely.

http://www.openwall.com/Owl/ARCHITECTURES.shtml
> Cross-builds are not supported: it is not possible to build packages for an architecture different than that of the build host, nor for a flavor of the architecture newer than that implemented in the build host's CPU.

No, it can't do cross-compiling. And ARM is not supported.

The camera of an iPhone has a lot higher resolution than 960x720. The screen of an iPhone 4 is 960x720, but the OCR algorithm wouldn't run on what the app eventually outputs to the screen.

Sounds like they're letting their customers benefit from Open Source just fine:

> Here is an incomplete sampling of the projects we utilize, we have contributed back to most of them: Hudson, Hadoop, Hive, Honu, Apache, Tomcat, Ant, Ivy, Cassandra, HBase, etc, etc.

That's a lot more than many companies that use Open Source (and have Linux clients or applications) do. Contributing back to the projects benefits everyone - not just users of FOSS desktop systems, but everyone that interacts with a system built on those projects.

Any application that could log your keystrokes can also monitor your clipboard. And - while we're at it - take screenshots periodically and record the coordinates of mouse clicks, potentially defeating on screen keyboards.

No.

But that's because they're bound by patient confidentiality, and not a boilerplate 10 year "don't talk about anything you learned at work" NDA.

So the two cases don't really compare. At all.

Help & Preferences > Classic Index > Use Classix Index

Help & Preferences > Discussion > Discussion Style > D1, also tweak D1 options as required.

Because reputation based systems (i.e., anyone hosting more than 1,000 mail accounts, and some smaller systems) are going to see that you don't own that IP, and don't own the reverse lookup on that IP. So they will score you badly.

On top of that it's virtually guaranteed that your ISP explicitly forbids running services on your home Internet connection, and probably even mentions email as a service you're not allowed to run. Most large ISPs also block all TCP/25 traffic going through their networks that is not aimed at their own email servers (which is why TCP/587 is so popular for SMTP submission with third party email providers), and you HAVE to use that port for server to server email traffic.

Those are just some reasons.

> Stallman warns would-be hackers not to download the LOIC software being pushed as a method of expressing anger with sites that have acted against Wikileaks - not because he thinks the protest is wrong, but because the tool's code is not visible to the user. "It seems to me that running LOIC is the network equivalent of the protests against the tax-avoiders' stores in London. We must not allow that to constrict the right to protest," he notes. "[But] if users can't recompile it, users should not trust it."

LOIC's source code is available on SourceForge.
http://sourceforge.net/projects/loic/

> I'm sure the book is more nuanced than this

Have you read it? That's an odd way to phrase things if you had read it, though. But why would you recommend it if you hadn't?

> It's none of their business if I jailbreak my phone.

Agreed. It is, however, your company's business if you jailbreak the phone they gave you. THEIR phone. Which is what the article is about - enterprise software detecting whether you jailbroke THEIR phone.

Damn skippy you don't jailbreak the phone that your workplace gave you. After all, they own that phone. Literally.

Which is what the article is actually about - functionality that allows enterprise software to detect whether a phone deployed through that enterprise has been jailbroken. It's a simple part of compliance testing of work issued equipment.