Actually the behavior of Home/End is one of the few things that still varies between Mac and PC and between various PC apps. Some have them move to the end of the line, some to the end of the document. A few that move to the end of the line move to the end of the document when you press them a second time.
We all saw the wounded police officer shot in the head.
Actually, no. I only saw a version where the police officer was blurred out and it cut before the shot. This was on several stations in both here in the US and in France.
The income tax percentage is graduated based on the income level and thus varies. In addition most deductions and refunds are fixed amounts and not any kind of percentage of income. This is a basic understanding that everybody has, so your attempt at humor fails completely because you are not extrapolating or exaggerating from any assumed situation or proposal.
You also screwed up with your $15/hour statement. After much analysis I figured out that you were talking about "people who *want* the minimum wage to be $15/hour", but your wording sounded like "the correct amount is 100% for people making $15/hour". That seems absurdly high so I thought you were making some kind of joke, but boy was I stumped as to what it was. I think you also seem ignorant of the fact that the minimum wage *is* $15/hour in some places.
In any case your attempt at humor was pretty dismally bad. You should maybe not try.
I'm not using a $ in Microsoft's name. My complaint is that the knee-jerk responders are the ones who look immature. They should be able to ignore it but it apparently it sooo annoys them that they cannot help but make fools of themselves by responding.
For those relative few that do significant driving off public roads, they can use a GPS tracker.
That is a very sensible solution (only people who want to prove they are not using the public roads would need to install one). Probably means it will never happen.
I am serious. There is a set of people who are so upset by the appirations of "M$" that they knee-jerk respond, and ALWAYS use the word "childish". Every single time. Yet actual childish actions, like calling somebody a 'fucking retard' or silly insults of Microsoft like calling it "microshit" are ignored. It seems they are desperate to try to stop something that bothers them and realizing it is hopeless.
If it actually was "childish" then IGNORING it would be the correct response.
Reading comprehension much? The negative income tax he was proposing was a fixed amount (500/month for 22+ years old, for instance). The opposite end (money paid to the goverment) would be a percentage of your income.
Whether a negative income tax is a good idea or not, you should not post such stupid responses indicating that you completely did not understand it.
More to the point, if this really is the MIT license then (unlike the previous Microsoft "open source" licences) you can in fact combine it with GPL code. So he should not be complaining because it is just as useful as GPL code.
If it was GPL you would have to include the source code for your changes, thus if everybody else felt they had to be compatible they could use this to duplicate the changes in their version.
This is the basic reason behind the GPL. You can argue whether it is a good idea or not, but you should at least not completely miss the point.
So what they see is "picture.jpg" If they don't notice the picture icon next to it that would be the same as a.exe, then they fall for it.
Actually it will show the embedded icon from the.exe which can easily be set to look like a picture file.
But what has always confused me is the filename actually shows as "picture.jpg", while an actual picture.jpg would show as just "picture", right? Therefore it should still be possible to distinguish them because a real one does not have ".jpg". Though I can imagine people not noticing, I'm wondering if there is (or was) a much worse bug, such as the display truncating at the first period while file-type lookup used the last period?
As pointed out in the article, the program must use gethostbyname() on a name supplied by the attacker.
A much more mitigating factor is that the bug is only exercised if the name looks like a numerical id, and according to their search most software first checks this using inet_aton() and only calls gethostbyname() if this fails, thus avoiding the bug.
strncpy will not overflow the buffer provided you pass the size of the buffer (if you don't pass the size of the buffer, *none* of the safer functions are going to help). It's problem is that it will not write a nul at the end of the buffer, thus reading will read right off the end. It also wastes a huge amount of time filling the unused part of the buffer with nul.
strlcpy is far, far better and does pretty much what is wanted.
However in this case they really did try to figure out if the buffer would overflow, so neither strlcpy or strncpy should be needed. They did the calculation wrong, claiming it needed 4-8 bytes less than it really did.
AB airlines flys A->B, and also A->B->C. Without any other reason, an A->B->C ticket would cost more or equal to the A->B ticket.
But AC airlines flies A->C, and is charging a smaller price than AB airlines.
AB airlines decides to complete by lowering the price for A->B->C so that it is less or equal to AC airlines A->C price. But they are not competing on A->B so they keep the price higher for A->B.
"regular users" click on files in a list or 2-d grid. They would not even notice if the filesystem allowed more than one file with the same name, and the certainly do not give a damn about case insensitivity. Even if they type at a terminal they use filename-completion and do not care either.
It is also clear that it has nothing to do with user-friendliness or they would map more common errors, such as multiple spaces to single ones, removing leading and trailing whitespace, or mapping equivalent unicode to the same files. They don't do this because they realize that such complex details of the encoding do not belong in the file system api.
Case-insensitivity is a throwback to ancient ASCII-only systems. If you live in the stone age you may think it is a good idea. If you have been exposed to it all your life you may think it is a good idea. But if you were actually intelligent you would know it is wrong.
All modern systems are capable of storing different strings for filenames in different cases. So no, Linux has it right and Windows has it wrong. Sorry to burst your bubble, but you are simply Wrong, with a capital W.
No. Two different byte strings should identify two different files (unless one or both of them are invalid byte streams). Anything else is introducing complexity into the filesystem and potential bugs and security violations, of which this it an excellent example. Sorry, but Unix has it right, and Microsoft and lots of other systems are *WRONG*.
The new news that the government thinks they did it certainly changes my opinion, though I would be curious exactly what the evidence is. I find it hard to believe they would risk making a stupid blunder of an incorrect accusation, so the info must be pretty good, such as directly from a spy inside NK at the hacker facility.
My gut feeling is this is disgruntled Sony employees. Somebody thought it would sound cool to threaten theaters and are probably amazed at the result.
Slashdot Mirror
Actually the behavior of Home/End is one of the few things that still varies between Mac and PC and between various PC apps. Some have them move to the end of the line, some to the end of the document. A few that move to the end of the line move to the end of the document when you press them a second time.
Up to this point, most people considered ISIS to be human. They were someone that could be negotiated with.
What?!?! I don't think that is true at all.
We all saw the wounded police officer shot in the head.
Actually, no. I only saw a version where the police officer was blurred out and it cut before the shot. This was on several stations in both here in the US and in France.
The income tax percentage is graduated based on the income level and thus varies. In addition most deductions and refunds are fixed amounts and not any kind of percentage of income. This is a basic understanding that everybody has, so your attempt at humor fails completely because you are not extrapolating or exaggerating from any assumed situation or proposal.
You also screwed up with your $15/hour statement. After much analysis I figured out that you were talking about "people who *want* the minimum wage to be $15/hour", but your wording sounded like "the correct amount is 100% for people making $15/hour". That seems absurdly high so I thought you were making some kind of joke, but boy was I stumped as to what it was. I think you also seem ignorant of the fact that the minimum wage *is* $15/hour in some places.
In any case your attempt at humor was pretty dismally bad. You should maybe not try.
I'm not using a $ in Microsoft's name. My complaint is that the knee-jerk responders are the ones who look immature. They should be able to ignore it but it apparently it sooo annoys them that they cannot help but make fools of themselves by responding.
For those relative few that do significant driving off public roads, they can use a GPS tracker.
That is a very sensible solution (only people who want to prove they are not using the public roads would need to install one). Probably means it will never happen.
No I didn't.
I am serious. There is a set of people who are so upset by the appirations of "M$" that they knee-jerk respond, and ALWAYS use the word "childish". Every single time. Yet actual childish actions, like calling somebody a 'fucking retard' or silly insults of Microsoft like calling it "microshit" are ignored. It seems they are desperate to try to stop something that bothers them and realizing it is hopeless.
If it actually was "childish" then IGNORING it would be the correct response.
Reading comprehension much? The negative income tax he was proposing was a fixed amount (500/month for 22+ years old, for instance). The opposite end (money paid to the goverment) would be a percentage of your income.
Whether a negative income tax is a good idea or not, you should not post such stupid responses indicating that you completely did not understand it.
Ohhh! The "childish" retort! I have not seen that in a while.
It's really interesting that somebody can say "Microshit" and nobody jumps up and down and rants and cries "childish! Childish! Childish!".
But when they say "M$" you shit your diapers and start yelling. CHILDISH! CHILDISH! CHILDISH! I insist it is Childish!!!!! Childish!
Give it up. It is obvious you is childish.
Every single manufacturer of Android phones has been threatened enough to pay up.
More to the point, if this really is the MIT license then (unlike the previous Microsoft "open source" licences) you can in fact combine it with GPL code. So he should not be complaining because it is just as useful as GPL code.
If it was GPL you would have to include the source code for your changes, thus if everybody else felt they had to be compatible they could use this to duplicate the changes in their version.
This is the basic reason behind the GPL. You can argue whether it is a good idea or not, but you should at least not completely miss the point.
Wow it sure didn't take long for a "ibertarian fucktard" to show up, just as the gp promised. Very good!
So what they see is "picture.jpg" If they don't notice the picture icon next to it that would be the same as a .exe, then they fall for it.
Actually it will show the embedded icon from the .exe which can easily be set to look like a picture file.
But what has always confused me is the filename actually shows as "picture.jpg", while an actual picture.jpg would show as just "picture", right? Therefore it should still be possible to distinguish them because a real one does not have ".jpg". Though I can imagine people not noticing, I'm wondering if there is (or was) a much worse bug, such as the display truncating at the first period while file-type lookup used the last period?
Anybody know? I don't have windows here to test.
Also the A380 is pretty silly looking. Have you seen one? It's like a fat guppy.
And they use more burp and fart sound effects than all of Hollywood!
As pointed out in the article, the program must use gethostbyname() on a name supplied by the attacker.
A much more mitigating factor is that the bug is only exercised if the name looks like a numerical id, and according to their search most software first checks this using inet_aton() and only calls gethostbyname() if this fails, thus avoiding the bug.
I have yet to have one such buffer overflow bug in my code
Yea, right. You know the authors of this function probably thought that too. They had no counter examples until now, just like you and your code.
strncpy will not overflow the buffer provided you pass the size of the buffer (if you don't pass the size of the buffer, *none* of the safer functions are going to help). It's problem is that it will not write a nul at the end of the buffer, thus reading will read right off the end. It also wastes a huge amount of time filling the unused part of the buffer with nul.
strlcpy is far, far better and does pretty much what is wanted.
However in this case they really did try to figure out if the buffer would overflow, so neither strlcpy or strncpy should be needed. They did the calculation wrong, claiming it needed 4-8 bytes less than it really did.
My theory is that a competitor airline is needed.
AB airlines flys A->B, and also A->B->C. Without any other reason, an A->B->C ticket would cost more or equal to the A->B ticket.
But AC airlines flies A->C, and is charging a smaller price than AB airlines.
AB airlines decides to complete by lowering the price for A->B->C so that it is less or equal to AC airlines A->C price. But they are not competing on A->B so they keep the price higher for A->B.
No, stop being an idiot.
"regular users" click on files in a list or 2-d grid. They would not even notice if the filesystem allowed more than one file with the same name, and the certainly do not give a damn about case insensitivity. Even if they type at a terminal they use filename-completion and do not care either.
It is also clear that it has nothing to do with user-friendliness or they would map more common errors, such as multiple spaces to single ones, removing leading and trailing whitespace, or mapping equivalent unicode to the same files. They don't do this because they realize that such complex details of the encoding do not belong in the file system api.
Case-insensitivity is a throwback to ancient ASCII-only systems. If you live in the stone age you may think it is a good idea. If you have been exposed to it all your life you may think it is a good idea. But if you were actually intelligent you would know it is wrong.
All modern systems are capable of storing different strings for filenames in different cases. So no, Linux has it right and Windows has it wrong. Sorry to burst your bubble, but you are simply Wrong, with a capital W.
No. Two different byte strings should identify two different files (unless one or both of them are invalid byte streams). Anything else is introducing complexity into the filesystem and potential bugs and security violations, of which this it an excellent example. Sorry, but Unix has it right, and Microsoft and lots of other systems are *WRONG*.
The new news that the government thinks they did it certainly changes my opinion, though I would be curious exactly what the evidence is. I find it hard to believe they would risk making a stupid blunder of an incorrect accusation, so the info must be pretty good, such as directly from a spy inside NK at the hacker facility.
My gut feeling is this is disgruntled Sony employees. Somebody thought it would sound cool to threaten theaters and are probably amazed at the result.
Chrome also complains about self-signed https, so you lose. Sorry.