Yup, another confirmed Hillary voter / shill / corrupt person.
Nope. Just a rational person. I won't be voting for Hillary or Bernie or Trump. The substance of my statement is reasonable. A company considering publishing private information that was hacked risks prosecution.
They are a private company. They can filter, block, promote any speech that they want.
They are also private emails belonging to a private organization, many of which could have copyright belonging to the authors of the emails, that were stolen in by someone making unauthorized access to their computers.
I can imagine what a sane corporate lawyer would advise as a safe course of action.
I hope you're not advocating censorship also.. When mass media becomes the emperor's lapdog we have a problem that needs a solution. If social media, even with all its blemishes, has to fill in, all the better. Now we just need a way to make the connection more robust, so that nobody can block anything.
I was not advocating anything. I was making an observation.
> Suicides shouldn't be counted because banning guns would in no way diminish somebody's desire to kill themselves. Guns make is vastly more likely they will succeed.
>Children accessing guns in the home would be an accident. No, that would be criminal negligence, which seems to be all too common.
>All the other bad things that happen indicates that you can't actually think of anything else.
So your sentence is effectively, No. The first two things were sufficient to make my point.
>The local government feared that if news outlets were to report using signals coming from social media, there was a chance that fake, non-credible, and rumors would slip through the filter.
That's exactly what happens in the West. Vast piles of BS gets propagated as news on social media, leading to large percentages of the population believing untrue things to be true, more than they already do.
The relevant figure to compare would seem to be intentional unjustified gun-related homicides. Can you find that? Or does that not support your worldview?
Way to ignore suicides, accidents, children accessing guns in the home and all the other bad things that happen that wouldn't happen in people didn't have guns laying around. I'm sure your motives are pure.
Any c++ programmer with more than 1 years experience will see this immediately and slap some braces around it. Thanks to modern IDEs and standard indentation (which the IDE will auto-correct) it's extremely unlikely anyone will make this mistake, or it will go unseen for very long.
I'd group this sort of 'error prevention' in the same category as putting the constant first in every if statement e.g.
if (1 == YouShouldHaveDoneThisTheOtherWay) {
Whatever(); }
The people who make the mistakes that this shit prevents have no place working on code.
You assume braces. BEGIN/END is less visually distinguished. You assume only one person will touch the code.
Code for what might happen, not what your ego tells you you will get away with.
I usually write all my C++ if statements, even if they contain just one statement, with curly brackets. I read somewhere it was better to do this, but I can't remember why.
It's a land mine. When you later add a second line to the conditionally executed section, you then need to notice the lack of braces and add them or you will not get the intended behaviour.
The BIG difference between the Google apps package for alternative ROMs like CyanogenMod and the Google apps installed on Nexus phones by default, is that under ROMs like CyanogenMod, you can install a very _limited_ google apps selection. For example, you can have basically just the google play store, and that's it. No Hangouts, Gmail, Google app, Chrome, Drive, etc, etc.
I don't remember that being an issue. However I only used CM for a while to get my flakey Nexus 4 to work with a hack I had to make to get Android to ignore the out of range temp values from the flakey temp sensor. The 5 was great as it came.
After going Google from the G1 through to the N5, I've gone to the Apply side just to see what's it's like over there.
>I suppose Hilary's private email server has saved her from being published by Wikileaks.
This. I would not be at all surprised if the current leaks were not the work of political opponents in government. Yet they don't contain emails from her own server.
If I was in her position, I would consider state department email servers to be far from secure from her political opponents in government and having her own email server seems to have actually kept her personal emails out of their hands. She had pretty much said as much. She did the right thing, whether you like it or not.
The LUX detector (Large Underground Xenon) is designed to pick up signs of weakly interacting massive particles, or WIMPs, when they engage in one of their rare interactions with normal matter.
There are indeed other candidates for dark matter, WIMPs being only one of those. This experiment searched specifically for WIMPs, which only rules them out, while of course the other remaining candidates remain to be explored.
It sets an upper bound for how strongly they interact with matter we know about, if they exist. And it's a very low upper bound indeed.
If I understand this correctly you blame the encoding standard which may or not be useful in some applications for faults in a library? What I found really bad is that somebody modded you into insightful for expressing this silliness.
Yes I did. This is because the ASN.1 encoding standard is and has been shown to be exactly the sort of format that is hard to implement parsers for correctly and securely. Worse, it doesn't need to be that way in most of the places it is used. It is used in protocols that are typically throwing around fixed size fields. But you have to specify the size of the field in the data and a parser has to read it and trust the input and set aside memory on the fly as the data comes in and declares itself to be of whatever size.
You'd be more successful if you tried to achieve that with something less shit than ASN.1. Though this particular fault is a typical "forgot integer overflow check before malloc". If you haven't eradicated those systematically, your processes are bad enough that you'd probably have security holes no matter the standard you implement.
If you knew how big things would be at the start, you would need to be mallocing as TLVs come in. This is one of the many reasons that ASN.1 is bad.
The bug is with a commonly used third party library that implements ASN.1, it has nothing to do with the ASN.1 standard itself. Your solution is for everyone to stop using SSL/TLS because of bugs with OpenSSL?
OpenSSL had it's own ASN.1 bugs.
It is in the nature of ASN.1 that is it hard to implement correctly and securely, yet it is in products that face the outside world on wired and wireless networking equipment. It is a recipe for disaster. We should stop using SSL/TLS because it is built on ASN.1 and many other hard-to-implement technologies that has yielded and will continue to yield a constant dribble of security failures. They can be replaced with protocols that do not express basic formats with turing-complete languages for which the most security properties are formally undecidable.
Slashdot Mirror
Yup, another confirmed Hillary voter / shill / corrupt person.
Nope. Just a rational person. I won't be voting for Hillary or Bernie or Trump. The substance of my statement is reasonable. A company considering publishing private information that was hacked risks prosecution.
They are a private company. They can filter, block, promote any speech that they want.
They are also private emails belonging to a private organization, many of which could have copyright belonging to the authors of the emails, that were stolen in by someone making unauthorized access to their computers.
I can imagine what a sane corporate lawyer would advise as a safe course of action.
https://www.hsph.harvard.edu/n...
This harvard study disagrees.
I hope you're not advocating censorship also.. When mass media becomes the emperor's lapdog we have a problem that needs a solution. If social media, even with all its blemishes, has to fill in, all the better. Now we just need a way to make the connection more robust, so that nobody can block anything.
I was not advocating anything. I was making an observation.
> Suicides shouldn't be counted because banning guns would in no way diminish somebody's desire to kill themselves.
Guns make is vastly more likely they will succeed.
>Children accessing guns in the home would be an accident.
No, that would be criminal negligence, which seems to be all too common.
>All the other bad things that happen indicates that you can't actually think of anything else.
So your sentence is effectively,
No. The first two things were sufficient to make my point.
>The local government feared that if news outlets were to report using signals coming from social media, there was a chance that fake, non-credible, and rumors would slip through the filter.
That's exactly what happens in the West. Vast piles of BS gets propagated as news on social media, leading to large percentages of the population believing untrue things to be true, more than they already do.
The relevant figure to compare would seem to be intentional unjustified gun-related homicides. Can you find that? Or does that not support your worldview?
Way to ignore suicides, accidents, children accessing guns in the home and all the other bad things that happen that wouldn't happen in people didn't have guns laying around. I'm sure your motives are pure.
So Americans are %333.333.. more likely an German to shoot someone with a gun when they have one.
I often have to go in fix problems caused by people's overconfidence. Everyone is fallible.
I design chips, where the tolerance of design errors is substantially lower than for software. You can't just roll out a patch.
Any c++ programmer with more than 1 years experience will see this immediately and slap some braces around it. Thanks to modern IDEs and standard indentation (which the IDE will auto-correct) it's extremely unlikely anyone will make this mistake, or it will go unseen for very long.
I'd group this sort of 'error prevention' in the same category as putting the constant first in every if statement e.g.
if (1 == YouShouldHaveDoneThisTheOtherWay)
{
Whatever();
}
The people who make the mistakes that this shit prevents have no place working on code.
You assume braces. BEGIN/END is less visually distinguished.
You assume only one person will touch the code.
Code for what might happen, not what your ego tells you you will get away with.
It's great now that we have huge screens, we don't have any more bugs.
I usually write all my C++ if statements, even if they contain just one statement, with curly brackets. I read somewhere it was better to do this, but I can't remember why.
It's a land mine. When you later add a second line to the conditionally executed section, you then need to notice the lack of braces and add them or you will not get the intended behaviour.
Gotcha.
I misinterpreted your comment.
The BIG difference between the Google apps package for alternative ROMs like CyanogenMod and the Google apps installed on Nexus phones by default, is that under ROMs like CyanogenMod, you can install a very _limited_ google apps selection. For example, you can have basically just the google play store, and that's it. No Hangouts, Gmail, Google app, Chrome, Drive, etc, etc.
I don't remember that being an issue. However I only used CM for a while to get my flakey Nexus 4 to work with a hack I had to make to get Android to ignore the out of range temp values from the flakey temp sensor. The 5 was great as it came.
After going Google from the G1 through to the N5, I've gone to the Apply side just to see what's it's like over there.
>well, no. "A work of the United States government [wikipedia.org],
The DNC isn't the government.
>I suppose Hilary's private email server has saved her from being published by Wikileaks.
This. I would not be at all surprised if the current leaks were not the work of political opponents in government. Yet they don't contain emails from her own server.
If I was in her position, I would consider state department email servers to be far from secure from her political opponents in government and having her own email server seems to have actually kept her personal emails out of their hands. She had pretty much said as much. She did the right thing, whether you like it or not.
>Now we "know" it's a particle and a wave.
No, it's a wave. The particle thing is just about the way your brain entangles with things.
https://www.youtube.com/watch?...
If you're impatient, jump to 23:00 and listen for a few minutes to be told the same thing by a real physicist.
Yay! We are all saved!
From Ars:
The LUX detector (Large Underground Xenon) is designed to pick up signs of weakly interacting massive particles, or WIMPs, when they engage in one of their rare interactions with normal matter.
There are indeed other candidates for dark matter, WIMPs being only one of those. This experiment searched specifically for WIMPs, which only rules them out, while of course the other remaining candidates remain to be explored.
It sets an upper bound for how strongly they interact with matter we know about, if they exist. And it's a very low upper bound indeed.
It was in Oregon and they were right wing nutjobs.
If I understand this correctly you blame the encoding standard which may or not be useful in some applications for faults in a library?
What I found really bad is that somebody modded you into insightful for expressing this silliness.
Yes I did. This is because the ASN.1 encoding standard is and has been shown to be exactly the sort of format that is hard to implement parsers for correctly and securely. Worse, it doesn't need to be that way in most of the places it is used. It is used in protocols that are typically throwing around fixed size fields. But you have to specify the size of the field in the data and a parser has to read it and trust the input and set aside memory on the fly as the data comes in and declares itself to be of whatever size.
You'd be more successful if you tried to achieve that with something less shit than ASN.1.
Though this particular fault is a typical "forgot integer overflow check before malloc".
If you haven't eradicated those systematically, your processes are bad enough that you'd probably have security holes no matter the standard you implement.
If you knew how big things would be at the start, you would need to be mallocing as TLVs come in.
This is one of the many reasons that ASN.1 is bad.
You mean ANS1 is/was used because of security?
It's the encoding for X.509 certificates.
Those who do not understand ASN1 are doomed to re-invent it. Poorly.
Look at abominations like binary xml.
Those who implement ASN.1 are doomed to introduce more critical security flaws into the world.
The bug is with a commonly used third party library that implements ASN.1, it has nothing to do with the ASN.1 standard itself. Your solution is for everyone to stop using SSL/TLS because of bugs with OpenSSL?
OpenSSL had it's own ASN.1 bugs.
It is in the nature of ASN.1 that is it hard to implement correctly and securely, yet it is in products that face the outside world on wired and wireless networking equipment. It is a recipe for disaster. We should stop using SSL/TLS because it is built on ASN.1 and many other hard-to-implement technologies that has yielded and will continue to yield a constant dribble of security failures. They can be replaced with protocols that do not express basic formats with turing-complete languages for which the most security properties are formally undecidable.