but I because freedom can be destroyed by too much freedom.
Freedom can't be destroyed by too much freedom, rather, by the abuse of it. In the ideal world, there would be no danger in open-sourcing schematics of dangerous machinery because no one would abuse that information to try and harm others. Restrictions on freedom (laws and punishments) are only justifiable because people abuse their freedom.
A big problem with a lot of Slashdotters - and a non-negligible portion of the general public - is that they read "freedom" and think "license."
This article is telling me that somehow, completely independently of one another, every major record label suddenly decided to make apple change their pricing model to the exact same thing at the exact same time? I don't think so. These labels are not in competition at all.
If, as you suggest, the labels did not independently arrive at their demands upon Apple, and instead had an agreement to make such demands, they've engaged in price fixing, which is NOT capitalistic and IS illegal.
What the hell? They're selling a frickin' commodity - a virtually unnecessary and frequently crappy one at that - so let them charge whatever they want.
kickbacks to corrupt legislators to take your house off you for petty copyright infringement/me shrugs. This is a surprise?
I agree with you, though, that it's all about control.
In fact, the grandparent probably recognized, as I did, that Vicissidude, through CowboyNeal, was trying to crack a joke.
However, the grandparent clearly recognized, as I and a host of other Slashdot readers also recognize, that this is still the Stupidest. Slashdot. Article. Ever.
The "joke" is so bent, so disconnected from anything in the common experience, I am inclined to think Vicissidude and CowboyNeal suffer from some mental pathology... or have lived in solitary confinement - self-imposed or not - for quite some time.
Yes. Simple observation tells us that there is no way, with Trillian encryption, to verify the authenticity of the key to which you're encrypting.
If you just want to scramble your IMs to prevent a casual, I-wonder-what-big-plans- nzhavok-has-for-spring-break network sniffing attack, Trillian is fine. However, if you want to prevent your unethical business competitor from capturing your communications and finding out your trade secrets, you'd be insane to rely on Trillian encryption.
I suggest you do some basic reading on how PKI works. Google/Yahoo/MSN/etc. is your friend.
You must be thinking of Trillian encryption, which, last I checked, is snake oil. Gaim-encryption uses a reasonable implementation of PKI... the key is supposed to be passed in the clear, hence its designation as the "public key." It's still not trusted unless you can verify the key's fingerprint with the key's owner.
Just do a search for "public key infrastructure" (PKI).
In fact, it'd be sufficient if they just installed a few call boxes out in the hallways.
That would be convenient for all sorts of criminals. All they'd have to do to keep anyone on the entire floor from calling the cops is yell down the hall, "crazy killer on the loose!" and hope they're in a gun-free haven like Washington, DC.
No no no no no! That's the best part about publishing the source (under a GPL/BSD/MIT license) (imho)! Any random person can submit improvements, start maintaining their own version or whatever. If you're too embarrassed (don't be), you could publish in under a pseudonym or something. All you have to do to publish it is put it up on a website and say, "here it is, and here's the license (preferably GPL, BSD or MIT) you have to abide by." Just put a comment at the top of each source file saying "this is distributed under such-and-such license" and give a URL to the license, put in the whole license in the case of MIT or BSD (they're short) or put the license in its own text file.
Heck, you could even put up a tip jar link asking for donations so you can devote time to improving it, if people so desire. Sourceforge could even provide the webspace.
I'm not familiar with sshd_sentry, but some iptables rules will block port 22 only. Also, if I understand the --rttl flag correctly, it would prevent a DoS attack like the one you mention from having any effect.
Slashdot Mirror
Eh, that's what I thought. Should've went with that instinct instead of lazily trying to track down a citation.
"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety." -FDR
Oops, someone needs to review percentages...
:)
8760 - (~8760 hours in a year) x (99.9/100 [this is where the "per cent" comes in]) = 8.76 hours downtime per 365-day year
Anyhow, is there anyone else that didn't read "99.9% uptime is expected" as "requires virtually no downtime?"
Try telling that to the lawyers. :)
Do I even need to say it?
Ever since the midwest blackout I've been meaning to get an operator's license... for 2m if nothing else.
but I because freedom can be destroyed by too much freedom.
Freedom can't be destroyed by too much freedom, rather, by the abuse of it. In the ideal world, there would be no danger in open-sourcing schematics of dangerous machinery because no one would abuse that information to try and harm others. Restrictions on freedom (laws and punishments) are only justifiable because people abuse their freedom.
A big problem with a lot of Slashdotters - and a non-negligible portion of the general public - is that they read "freedom" and think "license."
This article is telling me that somehow, completely independently of one another, every major record label suddenly decided to make apple change their pricing model to the exact same thing at the exact same time? I don't think so. These labels are not in competition at all.
If, as you suggest, the labels did not independently arrive at their demands upon Apple, and instead had an agreement to make such demands, they've engaged in price fixing, which is NOT capitalistic and IS illegal.
They want to go back to gouging the customers
/me shrugs. This is a surprise?
What the hell? They're selling a frickin' commodity - a virtually unnecessary and frequently crappy one at that - so let them charge whatever they want.
kickbacks to corrupt legislators to take your house off you for petty copyright infringement
I agree with you, though, that it's all about control.
Yep. Tonight I will finally follow the advice in my sig.
I concur! MOD PARENT UP!!!
In fact, the grandparent probably recognized, as I did, that Vicissidude, through CowboyNeal, was trying to crack a joke.
However, the grandparent clearly recognized, as I and a host of other Slashdot readers also recognize, that this is still the Stupidest. Slashdot. Article. Ever.
The "joke" is so bent, so disconnected from anything in the common experience, I am inclined to think Vicissidude and CowboyNeal suffer from some mental pathology... or have lived in solitary confinement - self-imposed or not - for quite some time.
I for one, welcome our new borg overlord.
Wait a minute...
Yes. Simple observation tells us that there is no way, with Trillian encryption, to verify the authenticity of the key to which you're encrypting.
If you just want to scramble your IMs to prevent a casual, I-wonder-what-big-plans- nzhavok-has-for-spring-break network sniffing attack, Trillian is fine. However, if you want to prevent your unethical business competitor from capturing your communications and finding out your trade secrets, you'd be insane to rely on Trillian encryption.
I suggest you do some basic reading on how PKI works. Google/Yahoo/MSN/etc. is your friend.
Encryption products. At least that's what they try to sell me when I send/receive a PGP encrypted email in Gmail.
Google's still reading your email and gleaning market knowledge from it...
You must be thinking of Trillian encryption, which, last I checked, is snake oil. Gaim-encryption uses a reasonable implementation of PKI... the key is supposed to be passed in the clear, hence its designation as the "public key." It's still not trusted unless you can verify the key's fingerprint with the key's owner.
Just do a search for "public key infrastructure" (PKI).
Actually, his usage of dyslectic is correct... dyslectic and dyslexic are synonymous.
And false. We use the Gregorian Calendar, which was instituted by Pope Gregory XIII. So he's really the last one to mess with the calendar, and as far as I know, he died a natural death.
Not that a little reality will get in the way of bashing the US...
What I'm looking forward to is when the stock Konqueror will pass the acid2 test. Anyone know when that's slated to happen?
Exactly.
In fact, it'd be sufficient if they just installed a few call boxes out in the hallways.
That would be convenient for all sorts of criminals. All they'd have to do to keep anyone on the entire floor from calling the cops is yell down the hall, "crazy killer on the loose!" and hope they're in a gun-free haven like Washington, DC.
That is the major problem with local courts IMO. The small-time judges act as if they are god's and rulers of their domain.
That's a problem with more than just local courts...
No no no no no! That's the best part about publishing the source (under a GPL/BSD/MIT license) (imho)! Any random person can submit improvements, start maintaining their own version or whatever. If you're too embarrassed (don't be), you could publish in under a pseudonym or something. All you have to do to publish it is put it up on a website and say, "here it is, and here's the license (preferably GPL, BSD or MIT) you have to abide by." Just put a comment at the top of each source file saying "this is distributed under such-and-such license" and give a URL to the license, put in the whole license in the case of MIT or BSD (they're short) or put the license in its own text file.
Heck, you could even put up a tip jar link asking for donations so you can devote time to improving it, if people so desire. Sourceforge could even provide the webspace.
I think he just wanted to parrot the phrase "unmitigated [livestock]shit," perhaps in an attempt to whore himself or herself for karma.
I'm not familiar with sshd_sentry, but some iptables rules will block port 22 only. Also, if I understand the --rttl flag correctly, it would prevent a DoS attack like the one you mention from having any effect.