Unfortunately large chunks of the story are only explained if you read the books for it. If you read the book "Contact Harvest" for example, you learn that the aliens are annihilating humanity because their leaders find out that humans ARE the "gods" of their religion. And finding out that your so called gods didn't actually ascend to another plane of existence sort of ruins a good religion don't you think?
To answer one of your other points... accident? Coming out beside the ring was intentional (the AI did it).
Also, the GP was wrong on several points. One, the enemy is not aware the rings are weapons, they think they're religious artefacts which will launch them on a "journey to another plane of existence".
Second, you don't rescue your captain, he gets absorbed by the nasty Flood, so you kill him.
The fact that NTFS supports file streams is nothing to do with the Windows NT security model whatsoever, just as the fact that HFS+ supports data and resource forks has nothing to do with the Mac OS security model. I also wouldn't be surprised if there were some way to embed crud tons of meta data into an alternative fork on the ext file systems (which would again have nothing to do with the Unix/Linux security model). The Windows NT security model for NTFS file systems is actually far more granular - and if you ask me, preferable to that of Linux with the ext file system.
Considering the iPod is even slower than a Windows machine at booting (about 90 seconds on mine), I'd hardly hold it up as a paragon of speed. The only thing I own that boots slower is my Windows Mobile phone.
Interesting, are you 100% sure that HPFS and FAT32 are the related ones? I mean, if you open FDISK (the old DOS partitioning tool) it recognises all HPFS partitions as NTFS ones.
While true, a hardware firewall will stop inbound traffic, and that is what most "unattended" compromises rely on - the ability to hit a service on the unpatched computer directly. If you basically just plugged it in and started updating with a hardware firewall, there is (virtually) no vector for attack in the first place.
No, TRIDENT is. You can remove Internet Explorer all you like.
And before you whine that you should be able to remove Trident, try remove KHTML from KDE (without apt-get offering to remove the K Desktop Environment because KHTML is a dependency) or WebKit from OS X.
It does remove them, but it doesn't nuke them from the installation image. Basically, (bear in mind that "disk is cheap") when you install Windows Vista or later, it dumps a copy of the installation media on your hard drive so that you don't need the DVD to install or remove stuff. When you remove a component, the installed version is deleted and the copy of it in the image is left alone so that you can easily put it back. Think of it as apt-get with a local repository if it helps any. I can't speak for whether it keeps the install image security-updated though - that I don't know.
The IWebBrowser interface, it's documented in MSDN. All a library has to do is expose that to replace Trident. But like I said before, it's a little unfair to expect that when Apple is perfectly OK to tie WebKit into anything that moves and KDE uses KHTML for a bunch of stuff too. You can't remove (or replace) the rendering engines on those. Well, maybe you can on KDE.
There is a real API. All you need to do is properly implement the IWebBrowser interface. No one does though. But then again, why should they make it so you can replace Trident? No one is claiming that Apple should let you replace WebKit or that the KDE project should let you replace KHTML.
Because Windows 7 (like Vista before it) maintains a copy of the install image on the disk. They don't mean the files are left in place, they mean the install image on the disk still contains the files, and they're removed from Program Files (or wherever).
Put an unpatched Linux from 2001 on the net and you'll highly likely achieve the same result. Does that mean Linux is an open sore waiting for the pus to come out? No. You can't expect to hold up an 8 year old version of an OS as the paragon of its security.
That said, no machine should be exposed directly to the internet anyway. A firewall should always be in play whether it's a standalone router or a Smoothwall/whatever install.
No, that definitely doesn't count as broken. That means that Gmail permitted too many spammers to abuse their network, and was blacklisted as a result. Nothing broken about that, except Google not taking a hard enough stance with spammers.
HPFS or HFS+? This is very important, HPFS is the OS/2 file system and HFS+ is the Mac OS file system. I'm sure you can guess why the Mac OS file system isn't supported, but an HPFS volume could theoretically mount fine - after all, HPFS by any other name is... you guessed it, NTFS.
Unfortunately large chunks of the story are only explained if you read the books for it. If you read the book "Contact Harvest" for example, you learn that the aliens are annihilating humanity because their leaders find out that humans ARE the "gods" of their religion. And finding out that your so called gods didn't actually ascend to another plane of existence sort of ruins a good religion don't you think?
To answer one of your other points... accident? Coming out beside the ring was intentional (the AI did it).
Also, the GP was wrong on several points. One, the enemy is not aware the rings are weapons, they think they're religious artefacts which will launch them on a "journey to another plane of existence".
Second, you don't rescue your captain, he gets absorbed by the nasty Flood, so you kill him.
The fact that NTFS supports file streams is nothing to do with the Windows NT security model whatsoever, just as the fact that HFS+ supports data and resource forks has nothing to do with the Mac OS security model. I also wouldn't be surprised if there were some way to embed crud tons of meta data into an alternative fork on the ext file systems (which would again have nothing to do with the Unix/Linux security model). The Windows NT security model for NTFS file systems is actually far more granular - and if you ask me, preferable to that of Linux with the ext file system.
Ah, that would explain it. I assumed it was considerably more intelligent than it actually is.
Who said that my signature relates to the content of discussions?
(It doesn't by the way, it refers to Slashdots insistence on changing the discussion interface weekly)
If they haven't "cracked" the protocol by now, they aren't going to.
Considering the iPod is even slower than a Windows machine at booting (about 90 seconds on mine), I'd hardly hold it up as a paragon of speed. The only thing I own that boots slower is my Windows Mobile phone.
Got DHCP enabled in Windows with no DHCP server perhaps? Doing that adds about 20 seconds to your boot time.
I can't find a real moderation for this, so I'll settle for a virtual moderation of "-1 Huh?"
That's a lake.
Interesting, are you 100% sure that HPFS and FAT32 are the related ones? I mean, if you open FDISK (the old DOS partitioning tool) it recognises all HPFS partitions as NTFS ones.
While true, a hardware firewall will stop inbound traffic, and that is what most "unattended" compromises rely on - the ability to hit a service on the unpatched computer directly. If you basically just plugged it in and started updating with a hardware firewall, there is (virtually) no vector for attack in the first place.
No, TRIDENT is. You can remove Internet Explorer all you like.
And before you whine that you should be able to remove Trident, try remove KHTML from KDE (without apt-get offering to remove the K Desktop Environment because KHTML is a dependency) or WebKit from OS X.
VLite does it wrong, and so does NLite.
Actually, it's a violation of the HDMI specification to not implement HDCP.
It does remove them, but it doesn't nuke them from the installation image. Basically, (bear in mind that "disk is cheap") when you install Windows Vista or later, it dumps a copy of the installation media on your hard drive so that you don't need the DVD to install or remove stuff. When you remove a component, the installed version is deleted and the copy of it in the image is left alone so that you can easily put it back. Think of it as apt-get with a local repository if it helps any. I can't speak for whether it keeps the install image security-updated though - that I don't know.
The IWebBrowser interface, it's documented in MSDN. All a library has to do is expose that to replace Trident. But like I said before, it's a little unfair to expect that when Apple is perfectly OK to tie WebKit into anything that moves and KDE uses KHTML for a bunch of stuff too. You can't remove (or replace) the rendering engines on those. Well, maybe you can on KDE.
There is a real API. All you need to do is properly implement the IWebBrowser interface. No one does though. But then again, why should they make it so you can replace Trident? No one is claiming that Apple should let you replace WebKit or that the KDE project should let you replace KHTML.
Tried it. No it doesn't, it boots up Firefox like I expected.
Because Windows 7 (like Vista before it) maintains a copy of the install image on the disk. They don't mean the files are left in place, they mean the install image on the disk still contains the files, and they're removed from Program Files (or wherever).
Put an unpatched Linux from 2001 on the net and you'll highly likely achieve the same result. Does that mean Linux is an open sore waiting for the pus to come out? No. You can't expect to hold up an 8 year old version of an OS as the paragon of its security.
That said, no machine should be exposed directly to the internet anyway. A firewall should always be in play whether it's a standalone router or a Smoothwall/whatever install.
Careful there man, Symantec Antivirus is pretty decent. It's Norton Antivirus that sucks. SAV is the corporate version.
What do the violet and mauve AV products use to scare people though?
No, that definitely doesn't count as broken. That means that Gmail permitted too many spammers to abuse their network, and was blacklisted as a result. Nothing broken about that, except Google not taking a hard enough stance with spammers.
Kazaa? Seriously? That shit's still around?
He must think Australia is a US government department.
It pretty much is, but that's not the point.
HPFS or HFS+? This is very important, HPFS is the OS/2 file system and HFS+ is the Mac OS file system. I'm sure you can guess why the Mac OS file system isn't supported, but an HPFS volume could theoretically mount fine - after all, HPFS by any other name is... you guessed it, NTFS.