-Republicans and Democrats will still look up to you for your intelligence. ************** There, all better. Both kinds of sheeple drink too much koolaid and believe whatever politicians tell them.
Darwin's theory of evolution is a conclusion based on a collection of empirical observations. Darwin never theorized why or how it occurred. He never theorized about it beyond "evolution happens, here's what I've observed that makes me think so". Knowledge of DNA and mutations were still quite a way off in the future.
So in reality there's a lot of truth to it. He didn't make up his observations. They can still be observed today. Selective breeding artificially creates evolution every day. Has been for thousands of years since man domesticated the dog. Evolution can be demonstrated. If you own a dog you own a product of experimental evolution since without man that dog would still be a wolf.
Why and how it occurs in nature is still relatively unknown.
>unreasonable searches unless a warrant is obtained.
Actually you aren't being subjected to an unreasonable search. You choose to get on an airplane. It's optional. If your job forces you to fly, get a new one. If you don't want to be searched you can turn around and walk out of the airport. Airplanes have been hijacked and blown up. If you want to fly, loss of privacy comes with the territory because I want my flight to end in a landing, not an explosion. To me it's perfectly reasonable to search everyone before they get on and make sure they aren't going to blow up the plane, because it's happened before and it will happen again.
That being said, these scanners are security theater. They don't work. You can just put a gun up your ass. You can make your shoe soles out of C4 and hide the detonator in the lining of your luggage, or even your iPhone. You should be strip searched by a person. In fact to do it right, everyone needs to be strip searched and subjected to a mass spectrometer. Every electronic device needs to be disassembled and checked, or not allowed on the plane. These machines are worthless.
This is why I exercise my right to not be searched or blown up by refusing to fly.
This may be the best business idea I've heard in a very long time. I think I'll take some binding classes... Imagine being able to buy any book ever made, have it leather bound and printed on quality acid-free paper, on demand, for a reasonable price.
You could even offer paperback binding for less money. BTW a lot of stuff is in the public domain and available for free at project Gutenberg.
"ir" is a prefix that denotes "opposite of". Irresponsible and irrespective are examples of proper use of the prefix. Technically "irregardless" is a double negative. "Regardless", "irrespective" or "whether or not" have the meaning you are trying to convey.
You aren't alone though, we're heading into a new dark age, and during the last dark age is when this prefix started being abused. "irrigation", for example, made it into the Oxford English dictionary around 1608, most likely because the abuse was so widespread by then, it was too late.
"rigation", which was the proper English use of the word which originated from the latin "rigatio" (rain), was finally killed off in the 1800's. It's no wonder English is confusing to learn for non-native speakers. The language is retarded and backwards and is only getting worse.
Based on this trend, "regardless" will be gone by 2200. Radiate will meet a similar fate, replaced by irradiate. Ir will have been twisted from meaning "opposite" to mean the "opposite of opposite". Oh the irony!
I'm not sure how making words longer by adding prefixes which are meant to be ignored is better but apparently I'm in the minority. It's been the English way since at least the 1600's.
The boys over at Oxford really need to do an audit and start undoing the damage.
One day irregardless will probably be proper English. It already clears the spellchecker in this browser.
>and that whole self-insurance thing... yeah, doesn't actually work when the shit hits the fan.
Neither does buying insurance. My current girlfriend worked for the state and had health insurance. She got cancer and went bankrupt within 3 years. The state fired her, her insurance dropped her, and here we are. She's fully recovered, in remission for a couple of years etc, but she's still un-insurable and basically unemployable. She had to start her own company to get a job. She's doing fine without insurance.
You are better off not paying for health insurance because if something serious happens you are fucked anyway. There will be some loop-hole for your employer and your insurance to drop you. If something minor happens, you will be able to pay for it.
So what good does it do again? You've obviously never had a real problem or you wouldn't be writing this drivel.
I have a few points that are worth considering when taking this article with a grain of salt. My fellow programmers probably won't want to hear this stuff but it's true. I used to work for a large investment firm (3rd largest at the time I was working there).
a. it takes a hell of a lot more work, experience, and intelligence to get a CFA(chartered financial analyst) than a programming degree. The CFA is required if you are going to be a fund manager. Think of it as a much harder bar exam. Most people that manage to pass it have advanced degrees in economics and/or finance from an ivy league school.
b. Half the CFAs and traders I knew, could write code in their sleep. One of the more successful ones developed a whole suite of tools he used, in C. They can do your job if they have to, it's more lucrative for them to wheel and deal than deal with debugging and implementation issues. It boils down to what is the best use of their time. If every programmer disappeared tomorrow, they could learn programming and still get it done. They are Really Smart(tm)
c. CFAs and traders pretty much blow their career if they screw up and lose a billion dollars. A programmer can simply find a new job if their bug rates are too high. They also have a QA team to double check their work. You can see if software will or won't work easily. To know whether or not a market strategy will work requires a ton of research and risk. They are rewarded based on the amount of risk they take and the rewards they get when they are successful. When they fail big, they are truly effed. Your risk level as a programmer is nearly 0.
d. Their ivy league educations ensure that they have an old boys network with lots of friends in the same position to help with getting the best deals. If you don't have this, you aren't ever going to make the kind of money they do. The fact that they have this is invaluable to the firm they work for, and their clients. Hate to say this, but us programmers are replaceable. In the current job market we're a dime a hundred by comparison. Go ahead, quit. There will be 20 people lined up for your job, killing each other to get it, for less money than you make.
Bottom line, if you are unhappy these people make millions of dollars and you don't, go get your CFA. You won't beat them. The only way to play with the big boys is to become one. Getting your CFA and having connections is more valuable than landing an NFL player contract, and just as tough, if not tougher, because it takes talent and connections, not just talent. Good luck with that! If you managed to get your CFA, it's pretty likely without the connections, you'd end up as a research analyst making less than you do as a programmer.
Expecting to cash in on what *they* do with your software is a little unrealistic. If you wrote the same software tools for people without their talent and connections, it would be useless. You are basically like a trainer to an NFL athlete. It's the same kind of royalty->serf relationship. You are replaceable, they are one in 250,000. You can't do what they do and they would still be able to do what they do without you, just like a lawyer or a doctor.
No one's ever denied that it's getting warmer. The debate is over what's causing it.
Since the glaciers receded from North America and Europe 20000 years ago and have never stopped receding (which I learned in elementary school), my money is on the natural cycle theory.
See it's simple actually. No PhD scientists necessary. There's no way the glaciers, in what became the USA and Europe, melted because of anyone's v8 powered SUV (or even millions of them). FYI France used to be under several kilometers of ice. So did New York State.
Put that in your AGW pipe and smoke it. You'd have to be an idiot to believe that man is causing this. It is a cycle that was going on long before we came, and will still be going on after we're extinct. Incidentally, NASA has recorded warming trends on every planet in the solar system. I'm sure man caused that too./sarcasm off
Surely you are either kidding or you've never been responsible for a large MySQL replication setup. Correction: ever been responsible for a MySQL replication setup and actually audited it.
MySQL replication is a joke, the worst. If you actually do a large implementation and monitor it, and you have a modicum of database traffic, you'll watch it go out of sync over and over. Trying to get a reliable replication setup out of MySQL was the only thing I've ever failed at in my IT career. Granted, I am a developer, not a DBA, but I was picked to do it because we don't have an actual DBA. It simply doesn't work the way you need it to if you are responsible for data integrity. Of course you need to write a monitoring script and check every table to catch it and have enough volume to produce the problem. 4 other guys in my company tried and failed to do the same job. We have all the books on the subject and tried everything.
It's not a total fail, it does replicate. You just lose a row randomly here and there. Sure it's only one row out of 10s of thousands, but you lose data on the slave. Usually within a week we lost at least 10 rows. To bring it back in sync you need to schedule downtime, lock the tables, dump the DBs from your master, load them up in the slave, and restart replication. Since regular downtime isn't an option for us we had to find a better solution.
We finally got the sledge hammer out and went to bitwise disk level volume replication and have never looked back. Crude but effective. MySQL replication is a steaming pile.
>The "victim" was driving 127mph on a public road with other traffic around. Who was placing whom in danger again?
That's not the issue. He was issued a citation and arrested for driving 127mph on a public road.
That's the punishment for that infraction. In this state you get arrested for going that fast. The police officer was *required* to pull him over. In Maryland, a state trooper is never off duty. They are required to carry a gun and intervene if a crime is being committed regardless of whether or not they are "on the clock". The officer did absolutely nothing wrong. Indeed, if he did nothing and ignored the motorcyclist, he'd have been in violation with his employment contract.
Driving 127mph in this state is a "shall arrest" infraction. That's why he was originally arrested, and it's justified.
The state's prosecutor is the one being a douchebag.
What he's also being charged with is wiretapping. He had a helmet cam on (in plain view I might add) which he was using to record his high speed adventure, and got pulled over while the camera was running. Chances are he forgot it was there due to the stress of a gun being pulled on him.
The state is claiming he's violated wiretapping laws because of this camera. In reality they got pissed because he posted it on YouTube. This is ridiculous. The officer in question actually performed admirably and didn't do anything wrong. I'm not sure why the state feels it's necessary to prosecute the guy for breaking wiretapping laws. That's the crux of this case.
Sure give him time for being an idiot, and driving too fast but you can't really, in this situation, prosecute him with wiretapping laws because he had a helmet cam on and forgot to turn it off. Where's the intent? The officer didn't see the camera mounted on top of the helmet? He knew the camera was there and didn't even ask if it was on.
The wiretapping charge is bullshit and is abuse of the law by the prosecution.
>Well the "unwashed masses" are generally products of the system set up by the elites, so if the elites don't like the results, why did they set up a system to produce people like this?
The unwashed masses are that way because they want to be. They are products of their own laziness. I came from a family that fits this description (unwashed masses). All 3 of us (my brothers and I) worked our asses off in school (while most of our friends were getting hooked on heroin), took it on the chin with student loans, and made something of ourselves. We got out of that demographic with hard work.
I have 0 respect for people that claim fate and their economic station are beyond their control. 99% of them made the decisions that brought them to where they are and they deserve where they are. Does that make me elitist? If it does, then I accept the badge with pride.
I am fucking tired of hearing about how "the system" victimizes people.
You make your own reality in this county. We don't need more programs. We need people to take advantage of the ones we've got. If they don't it's on them. People should fucking own it and do something about it if they don't like where they are, instead of playing the victim game. It's bullshit and doesn't help you at all.
People like you perpetuate the liberal victim mentality bullshit. You own your fate and there is no such thing as luck. If you don't like your place, fix the problem. Free your mind and your ass will follow. I'm living proof.
Eff that, I'm not handholding some n00b that doesn't know the quest. We shouldn't be letting n00bs in the guild in the first place. I'm busy farming l00ts biatch.
Since passwords are usually stored hashed, you need to hash the plaintext input. You can either do it in the database or the front end code, but you still need to do it.
Generally you do a select password, username where username = inputusername and password = password(inputpassword);
where password() is the hashing algorithm. If you get a row, it's a successful login.
The database usually does an indexed lookup against the first 4 (lets assume the index is on 4 characters) characters of the hash so the fails are going to usually be pretty consistent in time unless you get one of the first 4 characters right after hashing. Even then it won't have the timing you'd think it would. You could get the first 4 characters of the password right when inputting it, and it's possible that once hashed, none of the first 4 will match when comparing the hashes against what's in the table.
As well the entire hash result changes when you change just one character on the input if you use a good algorithm (sha2 or rijndael aka AES) so it's difficult, if not impossible to predict what change will happen in the hash by changing the input, if you don't know the secret and initialization vector. Much less how it will affect the timing of the query result.
Maybe I don't understand the problem.
Is this an issue with unhashed passwords? If so it's a non issue for most because anyone with half a brain will be using strong-cryptographically hashed passwords in a production system. The actual article says "some" libraries are vulnerable. I'm betting it's the ones that are set up to use text file databases with unhashed passwords. There are options in some of the servers to use a database like this.
This type of attack is one of the reasons we cryptographically hash passwords and use a good algorithm instead of something like md5.
I'd rather see them do it with the command line mysql client.
show databases use database show tables describe table select select into update delete
create function create procedure create index create trigger
If they can do most of this they are at least capable of functioning as a competent mysql-capable developer. I wouldn't expect anyone to know all of mysql's functions from memory. That's what the reference manual is for. You can cap this test by questioning them about design considerations, determining efficiency of operations, maintaining data integrity, and how to ballpark index cardinality etc.
Knowing all of this isn't even necessary, since there's a manual, but if they know 70% of it they are doing better than most people that work with mysql and you can be assured they know how to use a manual.
admin tasks such as setting up HA, replication, backups, disaster recovery etc and managing users are generally outside the scope of the average developer's knowledge so I consider that stuff a bonus, but not a must have
Then again, your accelerator going all the way to full by itself isn't expected behavior. Most drivers aren't prepared for it when this happens because it's never happened to them before. The time it takes to go from "WTF Surprise!" to useful action is too long to prevent an accident in some cases, especially if your foot isn't already on the brake and you are too close to the person in front of you, like taking off from a stoplight. The muscle memory to handle that situation simply isn't there. The actions aren't ingrained.
This happened to me with a floor mat once. If the car in front of me hadn't been 3 car lengths away, I'd have hit him. I was accelerating onto the highway, when I took my foot off the accelerator and it didn't stop accelerating, which is what I expected, I had an "oh shit" moment before I realized what to do (hit the brake, shift to neutral, kill ignition). Had I been closer I'd have rear-ended the person.
You can't say what you'd do til it happens to you. It's pretty easy to say what you'd do in the comfort of your house posting on slashdot. The reality is when your car seems to gain a mind of it's own and accelerate at full throttle all by itself, there will be an "oh shit" moment before you can have a useful reaction.
You are used to dodging idiots on the highway, you can see them before you hit them, expect them to drive like idiots and your reaction will be on point usually, because you expect them to do something stupid. You never expect a car to suddenly go full throttle all by itself.
It's not surprising there's no brake data on some of these.
This isn't surprising at all. All it takes is some idiot to get his prop tangled in one of those, or an angry idiot to vandalize it, to make it even more useless. There are a ton of zoom lenses capable of spanning 65 feet to get a picture.
Climb up high on the boat, put a zoom and polarized filter on (to get through surface reflections on the water) and take the picture.
Slashdot Mirror
pfft that was for the birds. I got mine on 1.44MB floppy at a computer show.
-Republicans and Democrats will still look up to you for your intelligence.
**************
There, all better. Both kinds of sheeple drink too much koolaid and believe whatever politicians tell them.
IBM: 26 years, highly esteemed executive.
Apple: 2 years and he leaves in disgrace.
I wonder if Mark P is the real problem... He probably shouldn't have burned his bridges at IBM due to promises made by someone who's obviously insane.
They're still bamboozled and think that "change" meant change as in "different".
They still think that democrats are different than republicans in some way.
She has almost no court experience, but she _did_ stay at a Holiday Inn Express last night.
Darwin's theory of evolution is a conclusion based on a collection of empirical observations. Darwin never theorized why or how it occurred. He never theorized about it beyond "evolution happens, here's what I've observed that makes me think so". Knowledge of DNA and mutations were still quite a way off in the future.
So in reality there's a lot of truth to it. He didn't make up his observations. They can still be observed today. Selective breeding artificially creates evolution every day. Has been for thousands of years since man domesticated the dog. Evolution can be demonstrated. If you own a dog you own a product of experimental evolution since without man that dog would still be a wolf.
Why and how it occurs in nature is still relatively unknown.
>unreasonable searches unless a warrant is obtained.
Actually you aren't being subjected to an unreasonable search. You choose to get on an airplane. It's optional. If your job forces you to fly, get a new one. If you don't want to be searched you can turn around and walk out of the airport. Airplanes have been hijacked and blown up. If you want to fly, loss of privacy comes with the territory because I want my flight to end in a landing, not an explosion. To me it's perfectly reasonable to search everyone before they get on and make sure they aren't going to blow up the plane, because it's happened before and it will happen again.
That being said, these scanners are security theater. They don't work. You can just put a gun up your ass. You can make your shoe soles out of C4 and hide the detonator in the lining of your luggage, or even your iPhone. You should be strip searched by a person. In fact to do it right, everyone needs to be strip searched and subjected to a mass spectrometer. Every electronic device needs to be disassembled and checked, or not allowed on the plane. These machines are worthless.
This is why I exercise my right to not be searched or blown up by refusing to fly.
This may be the best business idea I've heard in a very long time. I think I'll take some binding classes... Imagine being able to buy any book ever made, have it leather bound and printed on quality acid-free paper, on demand, for a reasonable price.
You could even offer paperback binding for less money. BTW a lot of stuff is in the public domain and available for free at project Gutenberg.
"ir" is a prefix that denotes "opposite of". Irresponsible and irrespective are examples of proper use of the prefix. Technically "irregardless" is a double negative. "Regardless", "irrespective" or "whether or not" have the meaning you are trying to convey.
You aren't alone though, we're heading into a new dark age, and during the last dark age is when this prefix started being abused. "irrigation", for example, made it into the Oxford English dictionary around 1608, most likely because the abuse was so widespread by then, it was too late.
"rigation", which was the proper English use of the word which originated from the latin "rigatio" (rain), was finally killed off in the 1800's. It's no wonder English is confusing to learn for non-native speakers. The language is retarded and backwards and is only getting worse.
Based on this trend, "regardless" will be gone by 2200. Radiate will meet a similar fate, replaced by irradiate. Ir will have been twisted from meaning "opposite" to mean the "opposite of opposite". Oh the irony!
I'm not sure how making words longer by adding prefixes which are meant to be ignored is better but apparently I'm in the minority. It's been the English way since at least the 1600's.
The boys over at Oxford really need to do an audit and start undoing the damage.
One day irregardless will probably be proper English. It already clears the spellchecker in this browser.
>and that whole self-insurance thing... yeah, doesn't actually work when the shit hits the fan.
Neither does buying insurance. My current girlfriend worked for the state and had health insurance. She got cancer and went bankrupt within 3 years. The state fired her, her insurance dropped her, and here we are. She's fully recovered, in remission for a couple of years etc, but she's still un-insurable and basically unemployable. She had to start her own company to get a job. She's doing fine without insurance.
You are better off not paying for health insurance because if something serious happens you are fucked anyway. There will be some loop-hole for your employer and your insurance to drop you. If something minor happens, you will be able to pay for it.
So what good does it do again? You've obviously never had a real problem or you wouldn't be writing this drivel.
I have a few points that are worth considering when taking this article with a grain of salt. My fellow programmers probably won't want to hear this stuff but it's true. I used to work for a large investment firm (3rd largest at the time I was working there).
a. it takes a hell of a lot more work, experience, and intelligence to get a CFA(chartered financial analyst) than a programming degree. The CFA is required if you are going to be a fund manager. Think of it as a much harder bar exam. Most people that manage to pass it have advanced degrees in economics and/or finance from an ivy league school.
b. Half the CFAs and traders I knew, could write code in their sleep. One of the more successful ones developed a whole suite of tools he used, in C. They can do your job if they have to, it's more lucrative for them to wheel and deal than deal with debugging and implementation issues. It boils down to what is the best use of their time. If every programmer disappeared tomorrow, they could learn programming and still get it done. They are Really Smart(tm)
c. CFAs and traders pretty much blow their career if they screw up and lose a billion dollars. A programmer can simply find a new job if their bug rates are too high. They also have a QA team to double check their work. You can see if software will or won't work easily. To know whether or not a market strategy will work requires a ton of research and risk. They are rewarded based on the amount of risk they take and the rewards they get when they are successful. When they fail big, they are truly effed. Your risk level as a programmer is nearly 0.
d. Their ivy league educations ensure that they have an old boys network with lots of friends in the same position to help with getting the best deals. If you don't have this, you aren't ever going to make the kind of money they do. The fact that they have this is invaluable to the firm they work for, and their clients. Hate to say this, but us programmers are replaceable. In the current job market we're a dime a hundred by comparison. Go ahead, quit. There will be 20 people lined up for your job, killing each other to get it, for less money than you make.
Bottom line, if you are unhappy these people make millions of dollars and you don't, go get your CFA. You won't beat them. The only way to play with the big boys is to become one. Getting your CFA and having connections is more valuable than landing an NFL player contract, and just as tough, if not tougher, because it takes talent and connections, not just talent. Good luck with that! If you managed to get your CFA, it's pretty likely without the connections, you'd end up as a research analyst making less than you do as a programmer.
Expecting to cash in on what *they* do with your software is a little unrealistic. If you wrote the same software tools for people without their talent and connections, it would be useless. You are basically like a trainer to an NFL athlete. It's the same kind of royalty->serf relationship. You are replaceable, they are one in 250,000. You can't do what they do and they would still be able to do what they do without you, just like a lawyer or a doctor.
No one's ever denied that it's getting warmer. The debate is over what's causing it.
Since the glaciers receded from North America and Europe 20000 years ago and have never stopped receding (which I learned in elementary school), my money is on the natural cycle theory.
See it's simple actually. No PhD scientists necessary. There's no way the glaciers, in what became the USA and Europe, melted because of anyone's v8 powered SUV (or even millions of them). FYI France used to be under several kilometers of ice. So did New York State.
Put that in your AGW pipe and smoke it. You'd have to be an idiot to believe that man is causing this. It is a cycle that was going on long before we came, and will still be going on after we're extinct. Incidentally, NASA has recorded warming trends on every planet in the solar system. I'm sure man caused that too. /sarcasm off
MySQL, ahead? with replication?
Surely you are either kidding or you've never been responsible for a large MySQL replication setup. Correction: ever been responsible for a MySQL replication setup and actually audited it.
MySQL replication is a joke, the worst. If you actually do a large implementation and monitor it, and you have a modicum of database traffic, you'll watch it go out of sync over and over. Trying to get a reliable replication setup out of MySQL was the only thing I've ever failed at in my IT career. Granted, I am a developer, not a DBA, but I was picked to do it because we don't have an actual DBA. It simply doesn't work the way you need it to if you are responsible for data integrity. Of course you need to write a monitoring script and check every table to catch it and have enough volume to produce the problem. 4 other guys in my company tried and failed to do the same job. We have all the books on the subject and tried everything.
It's not a total fail, it does replicate. You just lose a row randomly here and there. Sure it's only one row out of 10s of thousands, but you lose data on the slave. Usually within a week we lost at least 10 rows. To bring it back in sync you need to schedule downtime, lock the tables, dump the DBs from your master, load them up in the slave, and restart replication. Since regular downtime isn't an option for us we had to find a better solution.
We finally got the sledge hammer out and went to bitwise disk level volume replication and have never looked back. Crude but effective. MySQL replication is a steaming pile.
>The "victim" was driving 127mph on a public road with other traffic around. Who was placing whom in danger again?
That's not the issue. He was issued a citation and arrested for driving 127mph on a public road.
That's the punishment for that infraction. In this state you get arrested for going that fast. The police officer was *required* to pull him over. In Maryland, a state trooper is never off duty. They are required to carry a gun and intervene if a crime is being committed regardless of whether or not they are "on the clock". The officer did absolutely nothing wrong. Indeed, if he did nothing and ignored the motorcyclist, he'd have been in violation with his employment contract.
Driving 127mph in this state is a "shall arrest" infraction. That's why he was originally arrested, and it's justified.
The state's prosecutor is the one being a douchebag.
What he's also being charged with is wiretapping. He had a helmet cam on (in plain view I might add) which he was using to record his high speed adventure, and got pulled over while the camera was running. Chances are he forgot it was there due to the stress of a gun being pulled on him.
The state is claiming he's violated wiretapping laws because of this camera. In reality they got pissed because he posted it on YouTube. This is ridiculous. The officer in question actually performed admirably and didn't do anything wrong. I'm not sure why the state feels it's necessary to prosecute the guy for breaking wiretapping laws. That's the crux of this case.
Sure give him time for being an idiot, and driving too fast but you can't really, in this situation, prosecute him with wiretapping laws because he had a helmet cam on and forgot to turn it off. Where's the intent? The officer didn't see the camera mounted on top of the helmet? He knew the camera was there and didn't even ask if it was on.
The wiretapping charge is bullshit and is abuse of the law by the prosecution.
>Well the "unwashed masses" are generally products of the system set up by the elites, so if the elites don't like the results, why did they set up a system to produce people like this?
The unwashed masses are that way because they want to be. They are products of their own laziness. I came from a family that fits this description (unwashed masses). All 3 of us (my brothers and I) worked our asses off in school (while most of our friends were getting hooked on heroin), took it on the chin with student loans, and made something of ourselves. We got out of that demographic with hard work.
I have 0 respect for people that claim fate and their economic station are beyond their control. 99% of them made the decisions that brought them to where they are and they deserve where they are. Does that make me elitist? If it does, then I accept the badge with pride.
I am fucking tired of hearing about how "the system" victimizes people.
You make your own reality in this county. We don't need more programs. We need people to take advantage of the ones we've got. If they don't it's on them. People should fucking own it and do something about it if they don't like where they are, instead of playing the victim game. It's bullshit and doesn't help you at all.
People like you perpetuate the liberal victim mentality bullshit. You own your fate and there is no such thing as luck. If you don't like your place, fix the problem. Free your mind and your ass will follow. I'm living proof.
Eff that, I'm not handholding some n00b that doesn't know the quest. We shouldn't be letting n00bs in the guild in the first place. I'm busy farming l00ts biatch.
LOL Look closely at the google panel: how to plug an oil leak
http://1.bp.blogspot.com/_1xQeOPE9ePU/TEb7dj5CrMI/AAAAAAAAFEM/CzVHjYyZBHE/s1600/bpjoke.jpg
ROFLMAO
for snort 2.8? snort 2.9.
The linked article wins the title of Dumbass Article of the Week.
Since passwords are usually stored hashed, you need to hash the plaintext input. You can either do it in the database or the front end code, but you still need to do it.
Generally you do a select password, username where username = inputusername and password = password(inputpassword);
where password() is the hashing algorithm. If you get a row, it's a successful login.
The database usually does an indexed lookup against the first 4 (lets assume the index is on 4 characters) characters of the hash so the fails are going to usually be pretty consistent in time unless you get one of the first 4 characters right after hashing. Even then it won't have the timing you'd think it would. You could get the first 4 characters of the password right when inputting it, and it's possible that once hashed, none of the first 4 will match when comparing the hashes against what's in the table.
As well the entire hash result changes when you change just one character on the input if you use a good algorithm (sha2 or rijndael aka AES) so it's difficult, if not impossible to predict what change will happen in the hash by changing the input, if you don't know the secret and initialization vector. Much less how it will affect the timing of the query result.
Maybe I don't understand the problem.
Is this an issue with unhashed passwords? If so it's a non issue for most because anyone with half a brain will be using strong-cryptographically hashed passwords in a production system. The actual article says "some" libraries are vulnerable. I'm betting it's the ones that are set up to use text file databases with unhashed passwords. There are options in some of the servers to use a database like this.
This type of attack is one of the reasons we cryptographically hash passwords and use a good algorithm instead of something like md5.
I'd rather see them do it with the command line mysql client.
show databases
use database
show tables
describe table
select
select into
update
delete
create function
create procedure
create index
create trigger
If they can do most of this they are at least capable of functioning as a competent mysql-capable developer. I wouldn't expect anyone to know all of mysql's functions from memory. That's what the reference manual is for. You can cap this test by questioning them about design considerations, determining efficiency of operations, maintaining data integrity, and how to ballpark index cardinality etc.
Knowing all of this isn't even necessary, since there's a manual, but if they know 70% of it they are doing better than most people that work with mysql and you can be assured they know how to use a manual.
admin tasks such as setting up HA, replication, backups, disaster recovery etc and managing users are generally outside the scope of the average developer's knowledge so I consider that stuff a bonus, but not a must have
If right-click -> full screen is too complicated for a casual user, it's a fair bet they aren't watching movies on the internet in the first place.
Then again, your accelerator going all the way to full by itself isn't expected behavior. Most drivers aren't prepared for it when this happens because it's never happened to them before. The time it takes to go from "WTF Surprise!" to useful action is too long to prevent an accident in some cases, especially if your foot isn't already on the brake and you are too close to the person in front of you, like taking off from a stoplight. The muscle memory to handle that situation simply isn't there. The actions aren't ingrained.
This happened to me with a floor mat once. If the car in front of me hadn't been 3 car lengths away, I'd have hit him. I was accelerating onto the highway, when I took my foot off the accelerator and it didn't stop accelerating, which is what I expected, I had an "oh shit" moment before I realized what to do (hit the brake, shift to neutral, kill ignition). Had I been closer I'd have rear-ended the person.
You can't say what you'd do til it happens to you. It's pretty easy to say what you'd do in the comfort of your house posting on slashdot. The reality is when your car seems to gain a mind of it's own and accelerate at full throttle all by itself, there will be an "oh shit" moment before you can have a useful reaction.
You are used to dodging idiots on the highway, you can see them before you hit them, expect them to drive like idiots and your reaction will be on point usually, because you expect them to do something stupid. You never expect a car to suddenly go full throttle all by itself.
It's not surprising there's no brake data on some of these.
hella cool!
Three words:
Safety
Zoom Lens
This isn't surprising at all. All it takes is some idiot to get his prop tangled in one of those, or an angry idiot to vandalize it, to make it even more useless. There are a ton of zoom lenses capable of spanning 65 feet to get a picture.
Climb up high on the boat, put a zoom and polarized filter on (to get through surface reflections on the water) and take the picture.