Great. First the plugin requests to get a bunch of registry keys, then bombs out with an illegal operation (WinXP,FireFox 1.5RC3). Keep working on it guys, because I do like being able to update without using IE.
... "You see, man thinks about a little baby girls and a baby boys Man makes then happy 'cause man makes them toys And after man makes everything he can You know that man makes money to buy from other man" [James Brown, and later Brilliant: "It's a man's man's man's world"]
Perhaps not even there, unless used only by trusted operators. Just imagine someone jotting down some javascript, opening it in IE, causing that instance to happily move off-screen, capturing everything the next schmuck types into other open instances, patiently waiting for the xyzzy password to play it all back.
It might be a case of Stockholm Syndrome. Actually, looking at the present state of world politics and economics in the world, I think there's a real pandemic going on.
That way you can record anything that blasts pixels at you (preferrably already in digital format, like the input to the display matrix in your LCD/Plasma monitor. Audio may be somewhat more difficult, because you would need to hack the DAC to get at DRM-free data.
1. Buy cheapo Webcam 2. Disassemble it and get out CCD/objective part 3. Download data sheet from Chinese/Korean/Taiwanese manufacturer 4. ??? (something with soldering iron, other parts, microcontroller dev tools etc) 5. Enjoy your new DRM-free video camera!
Of course I understand the words 'REMOVED' and 'unpacking'. The point is, how can I trust their meaning if they're used in a confusing, ambiguous way to say the least?
The sentence "After unpacking 307MB disk space will be freed." is problematic in more ways. It can be said to mean: "After unpacking, 307MB disk space will be freed." or "After unpacking 307MB, disk space will be freed."
IMHO, the word 'unpacking' should be replaced with the word 'processing', which better summarizes the compound actions (installing, (while) upgrading, (while) removing) that apt-get may perform. Also, a comma should be added after 'processing' to make absolutely clear that '307MB' belongs to 'disk space', not to 'processing'.
If people don't care about such things in software that is being used world-wide by many large businesses, even for mission critical systems (yes, it is!), then I won't care to write 'The nuclear reactor shutdown process has been cancelled. The operation completed successfully' in my reactor control SCADA software (if ever I'll write any), 'cause the world is going to go boom somehow anyway.
Anything which uses technical means of copy protection is not a CD.
Not true. There is exactly one type of copy protection allowed by the Red Book standard (in fact all implementations have to adhere to its technical specification, whether they enforce it or not), and it is a variant of SCMS.
Basically, SCMS defines whether a source is copy-restricted or not, as well as whether it is an original or a copy. The idea is that anyone can make at most one copy of a copy-restricted original, but not a copy of a copy-restricted copy. See also here.
A distinction was made between consumer-grade (stand-alone) CD copiers (which should always obey SCMS) and professional CD-writers (which were not required to obey SCMS). Strangely, CD-writers attached to computers were treated the same way as professional units (presumably to allow users to copy-restrict their own work).
This strange treatment of computer-attached CD-recorders, combined with most recording software ignoring SCMS altogether in case of direct CD-to-CD copying seems to me the root cause of the current problems with non-conforming copy-protected CD's.
It is an interesting question whether either or both parties are violating the DMCA. I think that either CD-reader/CD-recorder manufacturers should have disallowed ripping of audio-CD's altogether, or they should have output a DRM-ed data format which can only be written to audio-CD's again by software compliant with SCMS.
IMHO Someone who spends effort and time to slip under the radar is not going to waste time adding 180 and its ilk to the machine and ruin their newfound method of infection.
Perhaps because this is just an example of a less sophisticated worm? To draw attention away from the millions of more advanced worms lying dormant in that many infected PCs, waiting to do their thing on, say, 06/06/06?
University...hundreds of students...with this infection.
Zwzwzw, this makes my head spin. Who was that again talking about declining academic performance?
If you can't trust students not to click some bogus link in an IM, can you trust them not to push a big red button labeled "Emergency Power Off" (in a lab containing a running, very expensive, high performance vacuum pump) because it looks so pretty and shiny? (Trust me, this has happened, perhaps not exactly for the abovementioned reason but definitely not because of an emergency).
Your remark only concerns GAIM running on Windows with users running with Administrator privileges all the time.
On Unix-like OSes, patching/replacing an executable require root privileges (unless some headless chicken installs it world-writable, that is). Even if GAIM needs to run setuid, it should relinquish privileges as soon as it is done with them.
Fact remains that pregnancy is 100% preventable--it should not have to be stopped.
Consider the female of a couple trying to have kids (so she is off birth control) getting raped, resulting in her getting pregnant.
I'm not trying to argue that abortion should be warranted in this case (it is a very complex subject and I've not made up my mind about it yet), I'm just saying that pregnancy is not 100% preventable.
Yep, that's the electronic version of an ugly black rectangle covering some words in the sentence.
Just be glad they didn't use tags to hide <censored>zis verry secred infurmasiun</censored>, because all the spelling nazis complaining about it would be shoved into unmarked vans, hauled to a secret holding place, then charged with circumventing a censoring device by having their browsers not support those mandatory tags...
Scotty/Tkined seem to offer all that you need. Decent diagramming, real-time network monitoring and alerting, totally scriptable in Tcl. For graph drawing wizardry, take a look at GraphViz.
Slashdot Mirror
Please use this link instead, to avoid thrashing the search engine. My bad.
Yes. We need a Computer Owners' Right to Repair Act, modeled after this one, for car owners.
Great. First the plugin requests to get a bunch of registry keys, then bombs out with an illegal operation (WinXP,FireFox 1.5RC3).
Keep working on it guys, because I do like being able to update without using IE.
The crack probably helps.
Or you could look for a keygen...
...
"You see, man thinks about a little baby girls and a baby boys
Man makes then happy 'cause man makes them toys
And after man makes everything he can
You know that man makes money to buy from other man"
[James Brown, and later Brilliant: "It's a man's man's man's world"]
Patents regulate this trade.
--
TTKT
You're trying to make Coybow Neal spin in his grave aren't you?
Thanks for causing my beekchone lisdodge while laughing, you incensitive slod!
Regarding OpenWRT, take your pick: OpenWRT TableOfHardware. I'm quite sure there are other projects out there also.
Thanks goodness there is still the Kama Sutra to claim as prior art...
IE can only be safely used on a trusted intranet.
Perhaps not even there, unless used only by trusted operators.
Just imagine someone jotting down some javascript, opening it in IE, causing that instance to happily move off-screen, capturing everything the next schmuck types into other open instances, patiently waiting for the xyzzy password to play it all back.
It might be a case of Stockholm Syndrome. Actually, looking at the present state of world politics and economics in the world, I think there's a real pandemic going on.
3. ...for the digitizer
5. erm... digitizer !
That way you can record anything that blasts pixels at you (preferrably already in digital format, like the input to the display matrix in your LCD/Plasma monitor.
Audio may be somewhat more difficult, because you would need to hack the DAC to get at DRM-free data.
This is how it might go in future:
1. Buy cheapo Webcam
2. Disassemble it and get out CCD/objective part
3. Download data sheet from Chinese/Korean/Taiwanese manufacturer
4. ??? (something with soldering iron, other parts, microcontroller dev tools etc)
5. Enjoy your new DRM-free video camera!
Of course I understand the words 'REMOVED' and 'unpacking'. The point is, how can I trust their meaning if they're used in a confusing, ambiguous way to say the least?
The sentence "After unpacking 307MB disk space will be freed." is problematic in more ways.
It can be said to mean:
"After unpacking, 307MB disk space will be freed."
or
"After unpacking 307MB, disk space will be freed."
IMHO, the word 'unpacking' should be replaced with the word 'processing', which better summarizes the compound actions (installing, (while) upgrading, (while) removing) that apt-get may perform. Also, a comma should be added after 'processing' to make absolutely clear that '307MB' belongs to 'disk space', not to 'processing'.
If people don't care about such things in software that is being used world-wide by many large businesses, even for mission critical systems (yes, it is!), then I won't care to write 'The nuclear reactor shutdown process has been cancelled. The operation completed successfully' in my reactor control SCADA software (if ever I'll write any), 'cause the world is going to go boom somehow anyway.
After unpacking 307MB disk space will be freed.
How can unpacking something free up space? Ahh, I get it, this must be some new kind of archive format with a negative compression factor...
Anything which uses technical means of copy protection is not a CD.
Not true. There is exactly one type of copy protection allowed by the Red Book standard (in fact all implementations have to adhere to its technical specification, whether they enforce it or not), and it is a variant of SCMS.
Basically, SCMS defines whether a source is copy-restricted or not, as well as whether it is an original or a copy. The idea is that anyone can make at most one copy of a copy-restricted original, but not a copy of a copy-restricted copy. See also here.
A distinction was made between consumer-grade (stand-alone) CD copiers (which should always obey SCMS) and professional CD-writers (which were not required to obey SCMS). Strangely, CD-writers attached to computers were treated the same way as professional units (presumably to allow users to copy-restrict their own work).
This strange treatment of computer-attached CD-recorders, combined with most recording software ignoring SCMS altogether in case of direct CD-to-CD copying seems to me the root cause of the current problems with non-conforming copy-protected CD's.
It is an interesting question whether either or both parties are violating the DMCA. I think that either CD-reader/CD-recorder manufacturers should have disallowed ripping of audio-CD's altogether, or they should have output a DRM-ed data format which can only be written to audio-CD's again by software compliant with SCMS.
IMHO Someone who spends effort and time to slip under the radar is not going to waste time adding 180 and its ilk to the machine and ruin their newfound method of infection.
Perhaps because this is just an example of a less sophisticated worm? To draw attention away from the millions of more advanced worms lying dormant in that many infected PCs, waiting to do their thing on, say, 06/06/06?
University...hundreds of students...with this infection.
Zwzwzw, this makes my head spin.
Who was that again talking about declining academic performance?
If you can't trust students not to click some bogus link in an IM, can you trust them not to push a big red button labeled "Emergency Power Off" (in a lab containing a running, very expensive, high performance vacuum pump) because it looks so pretty and shiny? (Trust me, this has happened, perhaps not exactly for the abovementioned reason but definitely not because of an emergency).
Your remark only concerns GAIM running on Windows with users running with Administrator privileges all the time.
On Unix-like OSes, patching/replacing an executable require root privileges (unless some headless chicken installs it world-writable, that is). Even if GAIM needs to run setuid, it should relinquish privileges as soon as it is done with them.
Fact remains that pregnancy is 100% preventable--it should not have to be stopped.
Consider the female of a couple trying to have kids (so she is off birth control) getting raped, resulting in her getting pregnant.
I'm not trying to argue that abortion should be warranted in this case (it is a very complex subject and I've not made up my mind about it yet), I'm just saying that pregnancy is not 100% preventable.
Yep, that's the electronic version of an ugly black rectangle covering some words in the sentence.
Just be glad they didn't use tags to hide <censored>zis verry secred infurmasiun</censored>, because all the spelling nazis complaining about it would be shoved into unmarked vans, hauled to a secret holding place, then charged with circumventing a censoring device by having their browsers not support those mandatory tags...
Scotty/Tkined seem to offer all that you need. Decent diagramming, real-time network monitoring and alerting, totally scriptable in Tcl. For graph drawing wizardry, take a look at GraphViz.
T-220:12:42:12
Leviathan ...
TRIGGER: 0x3efc3a0e
Process started
_
post.mod(parent, Redundant)
=> D'uh
Add to this