experiments in which laboratory rats are kept isolated in cramped metal cages, tethered to self-injection apparatus, show only that "severely distressed animals, like severely distressed people, will relieve their distress pharmacologically if they can."
So this study demonstrates that the legalization of drugs would result in every cubicle worker in the country becoming a drug addict?
So you and your friends all know a questionable doctor who has figured out how to game the system and get you all a hook-up?
I'm not saying there are no medical applications for those drugs, but among any group of friends, the probability of multiple people in the group being prescribed those sorts of drugs is almost 0.
All of this should raise at least as many questions about Obama as Mitt Romney's Mormonism raises about him.
I don't see how they compare. In relatively recent history, the Mormon church tried to establish a theocratic state, and even executed non-mormons who entered their state (in front of their children). Only a few decades ago, the head of the Mormon church said that black people were representatives or Satan.
Obama's church has some "us vs them" and otherwise regressive philosophies, but they don't even begin to compare with what the Mormon church has done in the past 200 years.
The recent Mormon push to adopt some (but not all) of what would be considered ethical main-stream philosophies is progress, but cultures can't turn around as quickly as the Mormon PR machine would have you believe. Even today, the LDS is admittedly anti-intellectual. That is a pretty terrible property for a government to have.
Linux's terrible support for SATA cards is a pretty good reason to upgrade. If the drivers ever actually materialize./me looks over at 3 partially-supported SATA cards and weeps
Gentoo is like going to a restaurant, ordering your dinner, and having the chef take you back into the kitchen and put you to work making your own meal.
No, it's like a Mongolian Barbecue, where you put all the meat and veggies you want in a bowl, then hand it to a chef to cook it for you.
Your ubuntu installation can't really be called AMD64 if one of your primary pieces of software, firefox, has been compiled for 32 bit. Flash doesn't work with 64 bit firefox. Do I need to say it again?
They have the right to protect their IP. They do not have the right to harrass people left and right, peppering the population with lawsuits in a "sue them all, let the courts sort them out" way.
If they police aren't enforcing the law, and you think "they do not have the right" to use the courts to enforce the law, how do you think the law should be enforced?
Why would you want to contribute? Class action lawsuits are typically funded entirely by the lawyers themselves. It's the lawyers who get all the money from the settlements, and the defendants they "represent" end up with gift certificates.
The CD is 25 years old, yet my parents still refer to every recording (audio, video, digital or not) as a "tape." They also refer to all acts of recording as "taping."
Technology progresses quickly, but humans aren't quite as fast, it seems:-(
Kids are already taught not to take candy from strangers. Do we really need to tell them not to take sex from "sugardaddy69"? Isn't the second statement implied by the first?
When I was a kid, I played in the dirt and ate bugs. Now, I never get sick and I have no allergies.
Truly, you have established a strong correlation and proven causation. Now that you have a strongly-supported scientific hypothesis based on your overwhelming sample size of one, you should publish your findings to Nature. I have no doubt your rigorous scientific methodology will hold up to the scrutiny of peer review.
Please continue to offer your expert medical advice about eating dirt. Perhaps you could go on tour with Kevin Trudeau.
I can already tell you the results: Every failure is a result of both management and engineer failures.
You are suggesting that all of senior management and many of the engineers at Boeing should all go bankrupt when a plane crashes due to a design flaw (because some jury awarded 10 billion for pain and suffering), then I would no longer invest, work, or serve in the US. I wouldn't be the only one.
Basically, you are suggesting the economic suicide for an entire country.
There is certainly a gray area while language changes. But I think "hack" has moved far beyond this gray area. For my entire adult life, almost everyone I knew, most of who are unarguably not morons, understood the new common meaning of the word "hack," not the old meaning.
"Two plus two equals four" and "To me, two plus two equals for" are equivalent statements.
The word "responsible" refers ENTIRELY to the researcher, not to the vendor. Any definition of full disclosure which depends on whether or not a vendor choses to act is therefore an invalid definition.
In your own cursory examination of articles and blogs, what term did you find the industry uses for disclosures in which the researcher gave a company advance notice of a publication, but not as much lead time as some would prefer? If the term "responsible disclosure" does not fit, which term does fit?
I didn't say it implied that; I said, "To me, "responsible disclosure" implies that
This is a contradiction. The phrase "to me" prepended to a factual predicate does not change the meaning of the statement. If you aren't a native English speaker, and I am misunderstanding what you mean to say, I apologize.
It is every vendor's dream to have security researchers work as free consultants, hand-holding them through fixing security problems. The reality is that researchers are under no obligation to do anything other than publish directly to bugtraq--aka full disclosure.
If they give vendors lead-time on the publication, the researchers are being somewhat responsible--an act of charity. It is a continuum--some durations are more responsible than others, but they all fall under "responsible disclosure."
Waiting TOO LONG starts becoming less responsible. The users of a vendor's software would want to know if there are flaws the vendor is neglecting to fix.
Whether a disclosure is somewhat responsible or optimally responsible can be debated on a case-by-case basis, but it is all best described by the term "responsible disclosure."
Realistically, if two people discover a vulnerability independently, one of them is likely to know about this long before the other. In such cases, one additional month is a negligible amount of time compared to the overall time the initial discover had free reign of the affected systems.
Additionally, most companies can't immediately implement work-arounds on the day of a 0-day publication. They have to wait until a patch is released from a vendor. In such cases, the black hat has the same amount of time to hack the target systems, and a thousand other black hats have a window of opportunity to attack which they would not have had under responsible disclosure.
What you are saying is correct--but only for some rare and contrived scenario, and not when you consider the bigger picture.
No. I'm saying that today, "hack" ACTUALLY MEANS "to bypass digital security." Insisting we use the older definition of the word because we are not "common idiots" is analogous to an English teachers' website requiring all posts be made in Olde English. Or worse, Middle English. I don't see you advocating we all write like Chaucer so that we can differentiate ourselves from "common idiots."
To me, "responsible disclosure" implies that a patch is made available BEFORE the detailed disclosure of the vulnerability happens
No. Wrong. It's not a matter of opinion. With responsible disclosure, a security researcher notifies a vendor before publishing his research. It absolutely DOES NOT imply that a patch is made available before the researcher publishes his findings. A vendor is still free to shoot itself in the foot under responsible disclosure.
The only gray area is determining just how much time is reasonable to release a patch. The standard accepted period these days seems to be between two weeks and two months. Mozilla's CEO would say "ten fucking days." Escaping part of an SQL string or recompiling code with a buffer overflow check doesn't take all that long to do.
If a vendor chooses to ignore a researcher, it does not change that fact that the researcher acted responsibly by providing the vendor with the courtesy of a "heads up" warning.
Slashdot Mirror
So you and your friends all know a questionable doctor who has figured out how to game the system and get you all a hook-up?
I'm not saying there are no medical applications for those drugs, but among any group of friends, the probability of multiple people in the group being prescribed those sorts of drugs is almost 0.
That may be for security, not for privacy. The secret service can't search inside a sewage pipe to check for chemical weapons or bombs.
Obama's church has some "us vs them" and otherwise regressive philosophies, but they don't even begin to compare with what the Mormon church has done in the past 200 years.
The recent Mormon push to adopt some (but not all) of what would be considered ethical main-stream philosophies is progress, but cultures can't turn around as quickly as the Mormon PR machine would have you believe. Even today, the LDS is admittedly anti-intellectual. That is a pretty terrible property for a government to have.
Thank you. That was the joke.
Linux's terrible support for SATA cards is a pretty good reason to upgrade. If the drivers ever actually materialize. /me looks over at 3 partially-supported SATA cards and weeps
Your ubuntu installation can't really be called AMD64 if one of your primary pieces of software, firefox, has been compiled for 32 bit. Flash doesn't work with 64 bit firefox. Do I need to say it again?
You can't use a 64 bit browser with nspluginwrapper. Sorry, doesn't cut it.
Actually, the word "record" predates vinyl. Ship captains recorded progress in the log books, but that had nothing to do with turntables.
The CD is 25 years old, yet my parents still refer to every recording (audio, video, digital or not) as a "tape." They also refer to all acts of recording as "taping."
:-(
Technology progresses quickly, but humans aren't quite as fast, it seems
Kids are already taught not to take candy from strangers. Do we really need to tell them not to take sex from "sugardaddy69"? Isn't the second statement implied by the first?
You wanted an argument? Oh, I'm sorry, but this is abuse, you want room 12A, just along the corridor. Stupid git.
Please continue to offer your expert medical advice about eating dirt. Perhaps you could go on tour with Kevin Trudeau.
Board members are typically paid high salaries? Are you sure?
I can already tell you the results: Every failure is a result of both management and engineer failures.
You are suggesting that all of senior management and many of the engineers at Boeing should all go bankrupt when a plane crashes due to a design flaw (because some jury awarded 10 billion for pain and suffering), then I would no longer invest, work, or serve in the US. I wouldn't be the only one.
Basically, you are suggesting the economic suicide for an entire country.
There is certainly a gray area while language changes. But I think "hack" has moved far beyond this gray area. For my entire adult life, almost everyone I knew, most of who are unarguably not morons, understood the new common meaning of the word "hack," not the old meaning.
"Two plus two equals four" and "To me, two plus two equals for" are equivalent statements.
The word "responsible" refers ENTIRELY to the researcher, not to the vendor. Any definition of full disclosure which depends on whether or not a vendor choses to act is therefore an invalid definition.
In your own cursory examination of articles and blogs, what term did you find the industry uses for disclosures in which the researcher gave a company advance notice of a publication, but not as much lead time as some would prefer? If the term "responsible disclosure" does not fit, which term does fit?
It is every vendor's dream to have security researchers work as free consultants, hand-holding them through fixing security problems. The reality is that researchers are under no obligation to do anything other than publish directly to bugtraq--aka full disclosure.
If they give vendors lead-time on the publication, the researchers are being somewhat responsible--an act of charity. It is a continuum--some durations are more responsible than others, but they all fall under "responsible disclosure."
Waiting TOO LONG starts becoming less responsible. The users of a vendor's software would want to know if there are flaws the vendor is neglecting to fix.
Whether a disclosure is somewhat responsible or optimally responsible can be debated on a case-by-case basis, but it is all best described by the term "responsible disclosure."
Realistically, if two people discover a vulnerability independently, one of them is likely to know about this long before the other. In such cases, one additional month is a negligible amount of time compared to the overall time the initial discover had free reign of the affected systems.
Additionally, most companies can't immediately implement work-arounds on the day of a 0-day publication. They have to wait until a patch is released from a vendor. In such cases, the black hat has the same amount of time to hack the target systems, and a thousand other black hats have a window of opportunity to attack which they would not have had under responsible disclosure.
What you are saying is correct--but only for some rare and contrived scenario, and not when you consider the bigger picture.
No. I'm saying that today, "hack" ACTUALLY MEANS "to bypass digital security." Insisting we use the older definition of the word because we are not "common idiots" is analogous to an English teachers' website requiring all posts be made in Olde English. Or worse, Middle English. I don't see you advocating we all write like Chaucer so that we can differentiate ourselves from "common idiots."
The only gray area is determining just how much time is reasonable to release a patch. The standard accepted period these days seems to be between two weeks and two months. Mozilla's CEO would say "ten fucking days." Escaping part of an SQL string or recompiling code with a buffer overflow check doesn't take all that long to do.
If a vendor chooses to ignore a researcher, it does not change that fact that the researcher acted responsibly by providing the vendor with the courtesy of a "heads up" warning.