If it's making changes to PCs without their owners' permission, no matter what the motive, it's viral code, by definition.
Subject: Clickety-click!
Attachment:clickety.exe
Text:
Yeah, you know, the files you axed me for.
<SmallerFont> By starting the attached file, you agree to: A) have remote administration software installed on your computer, B) allow that remote administration software to replicate to other computers as well, C) have a mail relay installed on your computer, D) have software that might conflict with the remote administration software (e.g. anti-virus software) disabled, E) you're not reading this anymore, are you? F) have updates to the remote administration software automatically installed, G) this text is so boring, H) even if that updates fundamentally alter the functionality of the software (e.g. DDOS the shit out of macrohard.com or dashslot.org) I) why not check out the nice file i sent you instead. J) you agree to never sue the author or distributor of this remote administration software for anything. K) no, really. the file is so nice - maybe it even makes funny sounds when you click it? L) neither anyone who uses your computer to send electronic mail, no matter what quantity or content. </SmallerFont>
Unlike MyDoom, which is exploiting Microsoft
weaknesses, [...]
You misspelled "dumbasses". (MyDoom doesn't exploit software weaknesses but idiot users who click on everything that looks like it could make funny noises when clicked.)
But if you ever do an emerge -u portage and then etc-update make sure you know what you are doing. A lot of the updates you can simply do EXCEPT for the files wich you may have changed. Problem is you may have forgotten and then you could really break something. I had it happen once when I accidently overwrote the net configuration.
Just look at the diffs - it's pretty obvious then that something is machine-specific. (even better, when changing something in/etc, just add a comment right above your changes stating you made them - good practice anyway)
Even with only one human user using a computer, having different programs run on separate user accounts is a good thing, as it reduces and compartmentalizes their damage potential.
A) You have a backup from which you can restore the user data. (If you don't have a backup you obviously don't care for the data. Harddisks die sometimes.)
and
B) Modified user data is (more) easily detected (than modified system programs) since its used often and directly by the users and is "data", as opposed to "programs".
Changes to programs and to parts of the operating system can be used to camouflage manipulations of user data long enough to render all backups virtually useless.
Yeah, that was the whole point. And that whole multiuser thing with one user not being able to destroy/manipulate other users data, which isn't all that important on (non-server-)PCs nowadays.
Just a side note - apart from that being way before islam - the zero (and i think that whole way of writing numbers that is now known as "arabic", too) originally came to arabia from india (which nowadays is partially muslim), and from arabia to europe.
...accorded respect because the United States feels silly...
or maybe (in the case of germany, also france, probably less in the case of spain) it is because they are influential in europe and europe is a friggin big part of world economics and politics?
nah... it's just a little in-joke by the big US of fuckin' A:)
SysRq - Not sure on this one, never used it, - possibly from mainframe terminal keyboards.
SysRq has some special application on linux kernels (if compiled with support for it) - quote from Remote Serial Console HOWTO (not that magic sysrq key has much to do with remote serial consoles, just the first page that google gave me for "magic sysrq"):
The "magic SysRq key" is a key sequence that allows some basic commands to be passed directly to the kernel. Kernel software developers use this interface to debug their software. Under most circumstances it can also be used to uncleanly reboot the computer, something that is otherwise difficult or expensive to do remotely.
Finding such letters, he'd present them to the boss and try to make the case for euthanasia. It worked; Hitler thought it was such a good idea that it [euthanasia for old people] was implemented nationally.
WTF... Never heared about that before. Are you sure about it? Any references?
Firstly, case sensitivity makes the compiler's work easier, hence compiling is faster. Good thing, really, except maybe for HelloWorld.java;)
Another point: case sensitivty improves code readability by removing ambiguity. For example, the java practice of namingMethodsAndVariablesInCamelCase, starting with a lowercase letter and TheSameWithAnUppercaseStartLetter for classes allows a variable to have the same name as a class, which i often use in code like this:
class SomeClass {
private Something something;
private Connection connection;//jdbc connection for this object
private SomeOtherThing someOtherThing; //... }
The case-sensitivity of java, combined with coding standards, enables me to do this. Obviously, something could also be named mySomething, but i find it much simpler and cleaner this way.
And finally, the slippery slope argument: If we allow incorrect capitalization in code, what next? A compiler with automagic spellchecking and -correction?
As Charlton Heston would put it: From my cold, case sensitive hands!
Even better, just send a bunch of unclosed, empty envelopes to yourself and a few months later fill them with stuff from sourceforge that was developed AFTER that date;)
Slashdot Mirror
So instead of being "yes"/"no", bits should offer more possibilities, like "maybe", "can i call a friend?" and "CowboyNeal"?
"The Wookie Offense"... hmm... that does not make sense.
:)
seems like the perfect name
Maybe SCOs lawyers invent the plaintiff's equivalent of the chewbacca defense?
Subject: Clickety-click!
Attachment:clickety.exe
Text:
Yeah, you know, the files you axed me for.
<SmallerFont>
By starting the attached file, you agree to: A) have remote administration software installed on your computer, B) allow that remote administration software to replicate to other computers as well, C) have a mail relay installed on your computer, D) have software that might conflict with the remote administration software (e.g. anti-virus software) disabled, E) you're not reading this anymore, are you? F) have updates to the remote administration software automatically installed, G) this text is so boring, H) even if that updates fundamentally alter the functionality of the software (e.g. DDOS the shit out of macrohard.com or dashslot.org) I) why not check out the nice file i sent you instead. J) you agree to never sue the author or distributor of this remote administration software for anything. K) no, really. the file is so nice - maybe it even makes funny sounds when you click it? L) neither anyone who uses your computer to send electronic mail, no matter what quantity or content.
</SmallerFont>
We all know, nobody reads those EULAs
You misspelled "dumbasses". (MyDoom doesn't exploit software weaknesses but idiot users who click on everything that looks like it could make funny noises when clicked.)
evil feature creep. makes poor IIS so vulnerable. bad, bad feature creep.
Yeah they should have used some of that sample-enlargement cream i see advertised so often.
Just look at the diffs - it's pretty obvious then that something is machine-specific. (even better, when changing something in
Kill all humans... kill all humans *snore* kill all humans...
Hey sexy mama!
I, for one, welcome our new ... ah, you get the picture!
I, for one, welcome our new nano-rules!
Even with only one human user using a computer, having different programs run on separate user accounts is a good thing, as it reduces and compartmentalizes their damage potential.
The point is that
A) You have a backup from which you can restore the user data. (If you don't have a backup you obviously don't care for the data. Harddisks die sometimes.)
and
B) Modified user data is (more) easily detected (than modified system programs) since its used often and directly by the users and is "data", as opposed to "programs".
Changes to programs and to parts of the operating system can be used to camouflage manipulations of user data long enough to render all backups virtually useless.
Yeah, that was the whole point. And that whole multiuser thing with one user not being able to destroy/manipulate other users data, which isn't all that important on (non-server-)PCs nowadays.
some might tend to think you don't want privacy if you broadcast videos of your life all over the place
you're right. shoulda asked google before risking my club geek membership. :)
I offer 15 lines of code. From System V.
can't be bothered to look it up right now, but if my memory serves me right, shouldn't it be 3.1415296... ?
Just a side note - apart from that being way before islam - the zero (and i think that whole way of writing numbers that is now known as "arabic", too) originally came to arabia from india (which nowadays is partially muslim), and from arabia to europe.
or maybe (in the case of germany, also france, probably less in the case of spain) it is because they are influential in europe and europe is a friggin big part of world economics and politics?
nah... it's just a little in-joke by the big US of fuckin' A
SysRq has some special application on linux kernels (if compiled with support for it) - quote from Remote Serial Console HOWTO (not that magic sysrq key has much to do with remote serial consoles, just the first page that google gave me for "magic sysrq"):
Finding such letters, he'd present them to the boss and try to make the case for euthanasia. It worked; Hitler thought it was such a good idea that it [euthanasia for old people] was implemented nationally.
WTF... Never heared about that before. Are you sure about it? Any references?
Another point: case sensitivty improves code readability by removing ambiguity. For example, the java practice of namingMethodsAndVariablesInCamelCase, starting with a lowercase letter and TheSameWithAnUppercaseStartLetter for classes allows a variable to have the same name as a class, which i often use in code like this:The case-sensitivity of java, combined with coding standards, enables me to do this. Obviously, something could also be named mySomething, but i find it much simpler and cleaner this way.
And finally, the slippery slope argument: If we allow incorrect capitalization in code, what next? A compiler with automagic spellchecking and -correction?
As Charlton Heston would put it: From my cold, case sensitive hands!
One time pads are uncrackable if employed correctly. But this thing surely should be vulnerable given enough time.
Even better, just send a bunch of unclosed, empty envelopes to yourself and a few months later fill them with stuff from sourceforge that was developed AFTER that date ;)
2. PROFIT!!!