The slashdot spin on this seems to be that it's a good thing.
How is this a good thing? Sure it may make being able to notarize things more convenient. And having it recognized as 'official' may be beneficial for many people. Especially businesses and other types of organizations who often need something to be canonized before they can embrace it.
What does this really mean though? If my key is compromised and someone uses it to 'sign' a contract, does that mean I'm bound by it?
Sure, and microsoft-bashing is silly at this stage.
The problem is not just allowing 'idiots' to easily run MS servers -- It's having these services run by default. And this applies for any OS. Remember how lots of old unices (many still do) used to run shitloads of cr*p from inetd, et al, by default? Same story, new faces.
Its a nice gesture, but I can't see how it will really make much of a difference... as much as I hate lawsuits, a better solution is to try and find the people behind these attacks, and sue them for all the wasted network resources caused by their attacks. Sure, that won't stop new attackers, but it will at least help them with some money to buy extra bandwidth to deal with it.
That's a nice idea.. however you're forgetting that the typical people performing these denial of service attacks, especially related to IRC, are in their teens, and do not have any money to speak of.
This isn't like patching a daemon and restarting it - networks are living, breathing entities who want to transfer data to each other.
Maybe if most network administrators/CIO's/etc were conscious of what is flowing through their networks - sure MRTG makes pretty graphs, but what does that traffic consist of? With effective traffic monitoring, routing, filtering policies in place by everyone, securing of internal networks, especially broadband customers - now that things like TFN/trin00/et al are in wide dispersal, simply blocking broadcasts at key routers is not going to do the trick -- know what travels through your network, don't just keep buying bigger pipes.
It very well may be (I don't have numbers, so I won't pull any out of the air).
But I don't think the typical "desktop consumer" will care a great deal if his Operating System has some BSD core, etc. Server market also means dealing less with individual lusers (no offense:), wrapping up some ($$$) nice maintenance contracts, upgrade plans, hardware upgrades, etc.
Large companies, once they choose an architecture to go with, oft' like to throw money a bit more readily than the typical desktop consumer who just wants to check his mail, play games, browse the WWW, etc. Desktop users probably not going to be as impressed by "robust networking features for making it a great server arch", etc.
Slashdot Mirror
The slashdot spin on this seems to be that it's a good thing.
How is this a good thing? Sure it may make being able to notarize things more convenient. And having it recognized as 'official' may be beneficial for many people. Especially businesses and other types of organizations who often need something to be canonized before they can embrace it.
What does this really mean though? If my key is compromised and someone uses it to 'sign' a contract, does that mean I'm bound by it?
Or will duress-like provisions apply?
have you considered using a mosix cluster
Sure, and microsoft-bashing is silly at this stage.
The problem is not just allowing 'idiots' to easily run MS servers -- It's having these services run by default. And this applies for any OS. Remember how lots of old unices (many still do) used to run shitloads of cr*p from inetd, et al, by default? Same story, new faces.
That's a nice idea.. however you're forgetting that the typical people performing these denial of service attacks, especially related to IRC, are in their teens, and do not have any money to speak of.
This isn't like patching a daemon and restarting it - networks are living, breathing entities who want to transfer data to each other.
Maybe if most network administrators/CIO's/etc were conscious of what is flowing through their networks - sure MRTG makes pretty graphs, but what does that traffic consist of? With effective traffic monitoring, routing, filtering policies in place by everyone, securing of internal networks, especially broadband customers - now that things like TFN/trin00/et al are in wide dispersal, simply blocking broadcasts at key routers is not going to do the trick -- know what travels through your network, don't just keep buying bigger pipes.
My $0.02 (tax exclusive)
-- Brian RIt very well may be (I don't have numbers, so I won't pull any out of the air).
:), wrapping up some ($$$) nice maintenance contracts, upgrade plans, hardware upgrades, etc.
But I don't think the typical "desktop consumer" will care a great deal if his Operating System has some BSD core, etc. Server market also means dealing less with individual lusers (no offense
Large companies, once they choose an architecture to go with, oft' like to throw money a bit more readily than the typical desktop consumer who just wants to check his mail, play games, browse the WWW, etc. Desktop users probably not going to be as impressed by "robust networking features for making it a great server arch", etc.
My $0.02 (plus tax)