Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

Saw this pointed out in an LWN comment:

> Apparently, RSA Security BSAFE Share for Java 1.1 has DUAL_EC_DRBG as a default:

> "The default Pseudo Random Number Generator (PRNG) is the Dual EC-DRBG using a P256 curve with prediction resistance off."

> I didn't find an obvious link for the equivalent C/C++ library documentation, but the RSA BSAFE CNG Cryptographic Primitives Library 1.0 FIPS 140-1 Security Policy document from RSA Security at the NIST site says (p.14):

> "The Module provides a default RNG, which is the Dual EC DRBG, using a P256 curve and SHA-256."

https://lwn.net/Articles/566329/

So yes, there are real products out there using Dual EC DRBG. In other news, never trust any crypto from RSA Security. After the SecureID fiasco, and this, it's pretty clear that they are not worth trusting for anything security related.


That's why the generally design the backdoor so that it's based on a key that only they have.

For example, with Dual EC DRBG, researchers discovered that it would be possible to create the constants based on another constant, with which you could predict the output easily. But without prior knowledge of that constant, it would be an infeasible brute-force search to find it.

Likewise, previous publicly known backdoors like the one in the export version of Lotus Notes depended on a key that the NSA had. There it was even simpler, and not obfuscated; it would just encrypt a portion of the session key with the NSA's public key, which they could decrypt and the easily brute-force the rest of the session key.[1]

The NSA doesn't want to make security weak against arbitrary attackers, they just want to give themselves the keys.

[1]: http://www.cypherspace.org/adam/hacks/lotus-nsa-key.html


Ah, it makes sense now. Thank you for explaining it.


> It's an awfully weird trojan horse --- or, as Daniel Franke put it on Twitter, a trojan platypus.

Heh, that is a pretty good term for it.

> no OS I know of uses a design taken directly from NIST.

Except for all of the pressure recently on the Linux kernel developers to use Intel's RdRand directly rather than mixing it into their existing entropy pool (see, for example, https://plus.google.com/117091380454742934025/posts/SDcoemc9... and https://lkml.org/lkml/2013/9/5/212), where apparently the reason is "Customers want a SP800-90 source available through the OS interface" (quote from David Johnston, designer of the RdRand hardware, on the Google Plus link).

So, apparently there is a lot of pressure to get the OS to adopt the NIST standards directly.

There are lots of reasons for this kind of pressure. Obviously, if you sell to the government, it'll be easier if you follow the NIST standards. There are likely lots of other compliance related reasons you would want to, such as encryption requirements for HIPAA. I wouldn't be surprised if some of those standards either required or were easier to comply with if you just used NIST approved algorithms, and it's easiest to use those NIST algorithms systemwide if the OS CSPRNG uses them (and directly, without extra unapproved random number generation on top).

> Second: Dual EC DRBG is a CSPRNG that uses elliptic curve point multiplications; in other words, it requires bignum math. If you're unfamiliar with CSPRNG design: that's not a normal requirement. Dual EC is very slow. Nobody would willingly use it.

Yes, this is the odd part. On the other hand, you do have to recall that the NSA is a big government bureaucracy. It may be that their SIGINT enablement department (the one that's responsible for weakening exportable crypto, planting backdoors, and the like) had promised to get some backdoors into widely used standards, but couldn't find a better way to do so surreptitiously and effectively without weakening security against foreign attackers as well.

It may be that Dual EC DRBG was just inserted so they could check off a box and continue to get funding for the standards body division of SIGINT enablement, and not as an actually realistic attack.


> but couldn't find a better way to do so surreptitiously and effectively without weakening security against foreign attackers as well.

Have we seen any evidence that the NSA cares _at all_ about avoiding "weakening security against foreign attackers" in their quest to weak security against themselves as attackers?

Aren't they _neccesarily_ weakening security against foreign attackers when they intentionally weaken crypto, which we now know they do?


> Aren't they _neccesarily_ weakening security against foreign attackers when they intentionally weaken crypto, which we now know they do?

No. In fact, most of the schemes that we know about in which they have tried to weaken crypto have involved them having some secret key which can be used to crack it, but without which you don't have a better attack than the standard brute-force attack.

That's the case with Dual EC DRBG. What researches discovered was that the constants in it could have been picked such that with knowledge of a secret constant, you can predict future output given only a relatively small amount of past output. Without knowing those constants beforehand, you wouldn't be able to do better than brute force.

Previous attempts have been similar; the Clipper Chip was supposed to have strong crypto, but store a master key in escrow with the NSA that they could use to crack it. Lotus Notes would encrypt part of the session key with a public key, for which the NSA had a corresponding private key, so if the NSA wanted to eavesdrop they could decrypt that and use it to speed up the brute-forcing process[1].

So, there are numerous cases of the NSA trying to balance the need for crypto that is strong for other attackers, while leaving them a backdoor that only they can use.

1: http://www.cypherspace.org/adam/hacks/lotus-nsa-key.html


It's unclear what the NSA thinks it's doing.

Backdooring the RNG, if they can keep the trapdoor secret(and the NSA would think that, despite the fact that given Snowden, it seems they have some security problems), doest obviously weaken security against foreign attackers who don't have the key unless they can solve the discrete log problem. Plus, it's possible(I think likely) they didn't intend for it to be widely used( it's slow as hell after all and they knew that), but wanted it on systems so they could swap it out for targeted attacks.

Weakening crypto standards(as the NYT reported), on the other hand, seems very counter productive. Though I suppose from the NSA's point of view, it depends which standards. Screwing with IPSEC would seem to hurt US national security and they've been accused of doing that. Screwing with the encryption standards of mobile phone voice communications, on the other hand, would seem to have a far lower consequence.


> No, I am not taking responsibility for an imaginary problem.

Are you claiming that the original authors daughter was imagining her classmates bullying her?

Are you saying that I'm imagining the fact that there are far more men than women in the programming profession?

These aren't "imaginary problems". These are very real problems. Now, there may be some debate about exactly which behavior is problematic; some people have different standards. But you're not going to tell me that bullying someone and telling them to get into the kitchen is not a problem.

> You are making the field off-putting to her, not the evil chauvinist boogeymen she has never seen.

I'm sorry, are you saying that someone who's saying it's bad to push women out of the profession is more off-putting than someone in her class telling her to get into the kitchen and make them a sandwich?

These are not "evil chauvinish boogeymen she has never seen", they are actual bullies in her actual class.


>Are you claiming that the original authors daughter was imagining her classmates bullying her?

No, I am claiming that the problems the post I replied to was putting forth are imaginary. I am quite aware that bullying is a real problem.

>Are you saying that I'm imagining the fact that there are far more men than women in the programming profession?

No, I am saying that is not an indication of a problem, much less systemic oppression. There is a strong correlation between increased freedom to choose "non-traditional" professions and fewer people choosing them. More women worked "men's jobs" when they were told they were men's jobs than they do now that they are encouraged to seek those jobs.

>But you're not going to tell me that bullying someone and telling them to get into the kitchen is not a problem.

Stop presenting such a ridiculous strawman. You can read the post I replied to. You can see that it is clearly not the article. Your entire response is predicated on ignoring the context of the conversation and repositioning my post as being a response to something completely different.


OK. Let's start from the beginning. The post you are replying to was a reply to the general tenor of a lot of posts, like yours, in this kind of thread. Posts which try to deny that there's a real problem, that the only reason that there aren't as many women in tech is that they have chosen not to.

Anecdotes like the original article, as well as many others that have come before, demonstrate that there is a real problem. There is some seriously problematic behavior out there. Now, how much of the gender disparity in tech is due to these kinds of problems, and how much is due to simple self-selection? That's hard to say; there may be arguments either way. But that doesn't really matter; even if the entire gender disparity can't be explained by odious behavior, at least some of it can, because there are very clearly women who are being off-put by very obnoxious, sexist behavior.

And furthermore, people are offput by defensive behavior, where tons of people come out of the woodwork and deny that there is any problem whatsoever. If you mention that some behavior makes you uncomfortable, and then a lot of people come out saying "there's no problem. It shouldn't make you uncomfortable. You just aren't all that into tech, you don't have thick enough skin" is that going to make you feel welcome and safe?

He's saying that we need to stop being defensive about it, stop trying to deny that problem, and start taking responsibility for hostile and off-putting behavior. Taking responsibility can include not doing it ourselves, and can also include not treating it as if it's acceptable behavior, not turning a blind eye to it, and not denying that that it actually exists.

So by telling him that he was discussing imaginary problems, you were doing exactly that. You were ignoring the actual, real, live example of the problem in the original post, and saying that what he was talking about is imaginary. That's why I brought up the original post; in order to claim that RyanMcGreal's problems were imaginary, you must be claiming that the original post is imaginary.

Now, in other posts, you seem to be trying to make the distinction between bullying and sexism, brushing this off as mere bullying. What you've missed is that it can be both. There is racist bullying. There is homophobic bullying. There is sexist bullying. There is bullying just for the sake of bullying. Just because it's also bullying, doesn't mean that it's not sexist, and part of the pattern of behavior that drives some women from the field.

Taking responsibility does not mean saying "oh, I'm an oppressor, thus I should be ashamed of myself." It means speaking up when you hear someone being harassed, it means stopping bullying that's going on right in your classroom (and being aware enough of your classroom to notice it going on), it means trying to understand why someone's upset or offended and try to think of reasonable, fair ways to fix that, rather than immediately jumping to the conclusion that the problem they are describing is not actually a problem.

> There is a strong correlation between increased freedom to choose "non-traditional" professions and fewer people choosing them. More women worked "men's jobs" when they were told they were men's jobs than they do now that they are encouraged to seek those jobs.

So, where is your evidence to back up this claim? It's a pretty strong claim, so you had better have some pretty good evidence to back it up.


>Anecdotes like the original article, as well as many others that have come before, demonstrate that there is a real problem.

Sure. And that problem is bullying. It has absolutely nothing to do with women in technology. Saying "imaginary problem X is totally real because real problem Y is real" is not logical.

>He's saying that we need to stop being defensive about it, stop trying to deny that problem, and start taking responsibility for hostile and off-putting behavior

And I am saying he is wrong. That's how it works, one person gives their opinion, and another person gives theirs.

>It means speaking up when you hear someone being harassed, it means stopping bullying that's going on right in your classroom

None of which has to do with the nonexistent "technology is full of chauvinists who scare women away" problem.

>So, where is your evidence to back up this claim?

http://www.dailymotion.com/playlists/user/BrainwashingInNorw...

>It's a pretty strong claim, so you had better have some pretty good evidence to back it up.

Why don't you need evidence to back up the claim that women are avoiding certain professions because of sexism?


> Sure. And that problem is bullying. It has absolutely nothing to do with women in technology. Saying "imaginary problem X is totally real because real problem Y is real" is not logical.

The problem is not bullying alone, though that is part of the problem. Something can be both bullying and sexism at the same time. Bullies will frequently reach for the strongest ammunition they can get, whether it's racist, sexist, homophobic, or any of a number of other ways to hurt their victims.

Just because it's bullying doesn't mean that it's automatically not sexism as well.

> http://www.dailymotion.com/playlists/user/BrainwashingInNorw...

Really? A video series called "BranwashingInNorway" about how there are a few people in Norway who are too politically correct to admit that there are some sex-linked behavioral differences?

Did you have any particular evidence for your actual claim that that once it's no longer taboo women don't want to cross traditional gender lines any more that you wanted me to look at, or am I supposed to trawl through the whole four and a half hours?

How about an actual reliable citation in an academic paper, rather than someone who's just trying to demonstrate that there are a few Norwegian academics who are a little too PC for their own good.

> Why don't you need evidence to back up the claim that women are avoiding certain professions because of sexism?

I do. There is plenty of evidence. For instance, the original post that this whole thread is about, though you choose not to believe it, or somehow are trying to classify it as not sexism. But there's plenty more as well:

http://web.archive.org/web/20070503012914/http://headrush.ty...

This is a woman who was terrorized from showing up at tech conferences due to threats of rape and murder.

Or how about this, a compilation of several sexual harassment issues that explain why Valerie Aurora, a Linux Kernel developer, no longer goes to certain hacker cons:

https://adainitiative.org/2012/08/defcon-why-conference-hara...

But OK, maybe you'd rather have statistics than anecdotes. How about this study which shows that women are more likely to leave fields which are more heavily male dominated:

http://www.nber.org/papers/w15853.pdf

That, of course, doesn't address harassment directly, but the general sense of unease that being in a small minority can give you, which can drive you out of the field.

I'm not claiming that the entire gender disparity in tech is due to harassment, or a poisonous atmosphere, or anything of the sort. What I am claiming is that it happens, it does drive some people out, and it's a bad thing. You seem intent on denying that there's any problem whatsoever.


You can't complain that my evidence isn't an academic citation, and then post even worse as your evidence. You are jumping to a conclusion, and I am saying the hypothesis you should be testing doesn't appear to be true. But since you skipped the testing the hypothesis step and went straight to a conclusion, you find this offensive and unimaginable. When you observe an uneven sex ratio in a particular field, you need to form a hypothesis to explain that ratio, and then test it. You can't just jump to "it is sexism" as a conclusion.


What part of my evidence do you consider worse? The evidence of actual women who have avoided conferences because of harassment? Or you mean a paper that actually gathers statistics that demonstrate that women are more likely to leave male-dominated fields than ones which have a more even gender distribution?

And half of what I was complaining about was that you linked me to a 4 and a half hour long video series, which from a brief glance at the first video, appeared to be some guy just trying to get some Norwegian academics to claim that both sexes are exactly equal, and then catch them out on that. I had no idea where to look in those videos for evidence of the actual claim that you made, that once a profession is no longer taboo for women to join, they have less desire to do so. Could you please tell me where in those videos to find that evidence? Or, since he doesn't seem to be doing any original research himself, just interviewing academics on a variety of topics, can you point out the research that he summarizes that contains this information?

> When you observe an uneven sex ratio in a particular field, you need to form a hypothesis to explain that ratio, and then test it. You can't just jump to "it is sexism" as a conclusion.

The paper I linked to did test certain hypotheses about why it happened, and one of them that it found evidence for is that the larger ratio of men in the industry leads to more women leaving; which forms a self-perpetuating cycle.

You're right, this doesn't directly address sexism, but it does provide evidence for why there's an uneven ratio, and why it continues to be that way, even if more women enter the profession than before.

> But since you skipped the testing the hypothesis step and went straight to a conclusion, you find this offensive and unimaginable.

But it's not just the uneven ratio that we're concerned about. As I said many times, there may be multiple reasons for it; perhaps harassment is only a small portion of the reason. It is obviously a part of the reason; as I've pointed out, there is plenty of anecdotal evidence for that, of people who have been harassed out of the industry, or out of certain communities within it. But you're right, without a rigorous study, we don't know how much of an effect that is, versus other factors.

The "offensive" part is denying that there is any harassment, and denying that men should try to stop it. There is harassment. There is behavior that makes women feel uncomfortable. Rather than being defensive and claiming that people shouldn't jump to the conclusion that sexism isn't the reason why there are few women in the field, why don't we try to not act sexist, stop sexism when we see it, actively try to eliminate at least that problem? Perhaps it won't lead to a lot more women in the industry, as they are avoiding it for other reasons. That's OK; we're still at least working to fix the sexism problem.

Note that I'm not claiming that all, or even most, men in tech are sexist. I'm not claiming that there is a unique sexism problem in tech. What I'm saying is that there is sexism, that it does hurt real people, and so if you see it, you should do something about it.


Or make sure that they have full-disk encryption and are cold shutdown when you cross the border.

While jurisprudence is still a bit fuzzy on this (it has flipped back and forth on a few appeals in a few separate cases, and never been conclusively decided by the Supreme Court), there have been ruling upholding the fact that you can't be forced to hand over your password due to the fifth amendment, unless the Government can already show that they know via other means that you have incriminating files on there.[1]

On the border, you would probably be safe from mandatory disclosure of your password without the border patrol getting a court order, and of course the whole point of this complaint is that the government is using border crossing as an end-run around the courts, being able to do searches that a court wouldn't otherwise approve.

So, using full-disk encryption that you trust, on all electronic devices that you carry, and making sure that they are cold shutdown, is probably sufficient. You should of course have a backup as well, as the border patrol may impound your devices while they try to decrypt them.

All in all, how much effort we have to do to defend ourselves from our own government is getting ridiculous. I don't know how to convince the American public of this, but we are not only violating the privacy of tons of people, but killing people who choose to drive rather than fly[2] due to the excess hassle that our "security" systems provide.

1: https://en.wikipedia.org/wiki/Key_disclosure_law#United_Stat... 2: https://www.schneier.com/blog/archives/2013/09/excess_automo...


Even with full-disk encryption, an image will be made of the drive, and the government will keep a copy on the chance that the password will be revealed later. Or the algorithm gets broken/weak enough at some point in the future.


Silly question.

Let's assume you have a device like a Macbook Pro or a Macbook Air, where you can't physically remove the drive without ungluing the device. You hotrod the firmware so only trusted USB devices with a specific encryption key are permitted to connect. How would the drive be imaged?


Thunderbolt target disk mode: http://support.apple.com/kb/PH3838

Perhaps you could solve this by "hotrodding" the firmware, but it's not particularly obvious how you could do that without risking bricking your laptop.


Perhaps Apple needs to require a password to boot off USB or to access target disk mode.


It's too bad the newer Macbook Pros don't come with ExpressCard slots anymore. I used to boot off a fast SSD expresscard. No disadvantages at all, other than the card ran hot. Remove the internal drive and when you pop out the Expresscard, much lower attack surface.


After the past week's NSA revelations, just what full disk encryption system should we be trusting? I think it's fair to assume that any commercial implementation is compromised.


[TrueCrypt](http://www.truecrypt.org/) or [dm-crypt](https://en.wikipedia.org/wiki/Dm-crypt) are both open source (technically, TrueCrypt has source available but doesn't meet the definition of an open-source license, though there's some debate on that point), and thus publicly auditable.

Also, I'm less worried about FDE being vulnerable to Border Patrol than about, say, SSL vulnerabilities across the whole network. The plausible deniability, which they would need to use to protect their sources if they found information, is a lot lower if you know you have been stopped and your laptop searched, rather than just tapping all internet traffic so you don't even know when you've been searched. Mac OS X's File Vault 2 and Windows's BitLocker are probably sufficient if if you aren't particularly paranoid about being individually targeted for something big, but I would be more inclined to trust the open solutions.


I FDE (on macs, FileVault 2 is by far the easiest, even though Apple is one of the more likely backdoor providers), but I also don't keep anything sensitive on it.

If seized at the airport, it provides a useful bit of information on whether they can break filevault 2. It seems implausible they would even if they could without a "plausible non-cryptographic alternative".


I know I shouldn't respond to the troll, but here goes.

> This use of "privilege" as a targeted weapon to silence specific demographics has to stop.

Sorry, no specific demographic is being "silenced" here. If you think that men are being silenced, well, why are you able to speak?

> Women in the western world have always been among the safest, most privileged people on Earth.

Always been, hm? So they were privileged when they were denied suffrage until less than 100 years ago? They were privileged when they were denied admission to some of the country's top universities until just 30 years ago?

> This entire thread, in fact, has been a shining example of female privilege.

What, exactly, do you see as female privilege? What do you see women being allowed to do, that men are not allowed to, that men are harassed for doing, that men are driven out of the industry for doing due to attacks? And if you do see any such behavior, perhaps someone being harassed for being a dancer, or into musicals, or the like, please note whether it's women doing those attacks, or other men.

> No one cares that women soundly outnumber men in university admission, and university graduation, and even high school graduation.

Awful generous of you to round down to "no one." If no one cares, why have you heard about it? Wouldn't people who don't care not be writing articles about it? There are plenty of people who care, who are concerned about this, who write about it and worry about it. That's not "no one" caring.

However, despite all of that, there are many fewer women in technology, and fewer still are programmers. Just because there might be other biases in other fields, doesn't mean that we shouldn't worry about biases and harassment in our own.

> Instead, we're having a collective anxiety attack because a hyper-privileged white woman is upset that her hyper-privileged white daughter might have had her feelings hurt in high school. This is surreal.

I'm not really clear on what you mean by "hyper-privileged". Is it a privilege to be bullied and told to get into the kitchen? That doesn't really sound like the definition of "privileged" to me.

Yes, there may be ways in which she is privileged compared to others. There are other problems out there. But that doesn't mean that we shouldn't try to address this one.

It is a problem when women don't enter a career due to harassment, and indifference from others in face of said harassment. Can we have a realistic discussion if a casual dirty joke counts as harassment? Sure. But there's a difference between a casual dirty joke told by one conference attendee to another, and several kids harassing another and telling her to get into the kitchen while the teacher does nothing about it.

You sound fairly threatened and insecure; it sounds like you're worried that women might do better than you at technology, and then the one way you use to make yourself feel secure in yourself may fall away. You seem to have caught on to the power of being a victim and having other people come out to defend you, so you're trying to apply that tactic to defend yourself from women who threaten your sense of technological superiority. It's not a very attractive tactic, however; it makes you look defensive and reactionary. I'd recommend trying to find other ways to feel good about yourself; for instance, by being supportive and welcoming of new people, and making programming a skill and trade that is accessible to all.


You sound fairly threatened and insecure; it sounds like you're worried that women might do better than you at technology, and then the one way you use to make yourself feel secure in yourself may fall away.

Why do you have to make your points while simultaneously being a complete douche about them? Personal attacks on HN, on purpose?


Did you read the grandparent post? Bringing up complete strawmen, making vague censorship claims, making off-topic arguments about "well, men have it tough too in these other cases, so really men are the victims", and so on.

I tried to find some reason to explain why someone would do something like that, and that's the best I could come up with. I was also trying to point out how ridiculous an argument of "stop playing the victim card, look how much of a victim I am" is. Perhaps I went a little beyond what I should have when trying to point out how ridiculous it is, but I'm not really sure how to point that out much more gently.

Perhaps you have a better suggestion for how to deal with such ridiculous, hysterical, off-topic arguments? Perhaps one that doesn't involve calling someone a "complete douche" in the same breath as criticizing personal attacks?


> I'm not really clear on what you mean by "hyper-privileged".

If we're doing this, it's privilege to not be starving on the streets of Calcutta, it's privilege to know how to read, and it is damn sure privilege to be so surrounded by functioning computers that learning how to use them sounds like a real option instead of fairy tales and bullshit.

So, yeah, if you really want to double-down on the privilege concept, we'll go into how privileged the subject of this article actually is.


Sure, you can always find someone who you are privileged relative to. Why does that matter?

That doesn't change the fact that in America, in high-tech industries, there are many privileges that men enjoy that women do not.

It's a derailing tactic to say "you're privileged relative to some extremely impoverished, down on their luck person over there, so you shouldn't ever complain." Just because I don't have the worst boss in the world doesn't mean I shouldn't ever complain about my boss. Just because the US may not spy on its citizens as much as China does doesn't mean we shouldn't be complaining about the US spying on its citizens.

That's what I mean when I don't understand what he means by hyper-privileged. If he's referring to relative to some hungry orphan on the streets of Calcutta, that's just not relevant. If he means relative to the other people in the class, which is the comparison that actually matters for this discussion, then I'm not sure what he means as she obviously is not privileged relative to them, as they were able to harass her into deciding not to continue that course of study.


> Sorry, no specific demographic is being "silenced" here. If you think that men are being silenced, well, why are you able to speak?

The verb "silence" is not restricted to scenarios in which someone is rendered literally incapable of speech. It never has been.

> Always been, hm? So they were privileged when they were denied suffrage until less than 100 years ago? They were privileged when they were denied admission to some of the country's top universities until just 30 years ago?

Definitely. The members of the anti-suffrage movement, both men and women, pointed to those female privileges as the primary reason women shouldn't be allowed an equal say in setting the course of government.

> Awful generous of you to round down to "no one." If no one cares, why have you heard about it? Wouldn't people who don't care not be writing articles about it? There are plenty of people who care, who are concerned about this, who write about it and worry about it. That's not "no one" caring.

You got me. There aren't literally zero people who care about the myriad of ways men are disadvantaged to women. Unfortunately, there are close to literally zero people with power who seem care about men's issues, which is why society allocates an outrageously disproportionate amount of attention, money, time, and energy toward women's issues.

> However, despite all of that, there are many fewer women in technology, and fewer still are programmers. Just because there might be other biases in other fields, doesn't mean that we shouldn't worry about biases and harassment in our own.

Agreed, but we need to realize that attention, money, time, and energy aren't limitless.

> You sound fairly threatened and insecure; it sounds like you're worried that women might do better than you at technology

Cut it out.

I'm not worried about myself at all. Like many of us, from a young age, I make more money than I'll ever know what do with. I have a growing a set of skills that are almost guaranteed provide me with gainful employment for my entire life.

I'm worried about the men at the bottom of society who are always marginalized by feminist policing and hand-wringing.

Feminists always point to the top of society, notice that there are more men than woman, then use that as evidence that men are more privileged.

However, they never point to the bottom of society, notice that there are more men than women, then use that as evidence that women are more privileged.

Never, never, never.

That's because they have a particular agenda. And that's fine. But it's also fine for people like me to point out that we are allocating an outrageously disproportionately amount of attention, money, time, and energy to women's issues.


> The verb "silence" is not restricted to scenarios in which someone is rendered literally incapable of speech. It never has been.

Please clarify, then, about who exactly is being "silenced" and how, and what you mean by "silenced" if it doesn't mean that the person is unable to speak publicly about the topic.

> Definitely. The members of the anti-suffrage movement, both men and women, pointed to those female privileges as the primary reason women shouldn't be allowed an equal say in setting the course of government.

Wait a minute. Are you actually aligning yourself with the anti-suffrage movement? Are you serious?

> Feminists always point to the top of society, notice that there are more men than woman, then use that as evidence that men are more privileged.

> However, they never point to the bottom of society, notice that there are more men than women, then use that as evidence that women are more privileged.

Wait a second. There can't be more men than women on both the top and bottom of society, as there are more women than men in general.

So, let's look at actual numbers from the Census Bureau: http://www.census.gov/hhes/www/poverty/data/historical/peopl...

In the Poverty by Sex chart, in 2011, we see 151 million men, of whom 21 million, or 13.6% are below the poverty line. There are 157 million women, of whom 26 million, or 16.3%, are below the poverty line.

Looks to me like in both absolute numbers and percentages, there are more women than men at the "bottom of society".

> That's because they have a particular agenda. And that's fine. But it's also fine for people like me to point out that we are allocating an outrageously disproportionately amount of attention, money, time, and energy to women's issues.

We spend a lot of time and effort on women's issues because, historically, they have been discriminated against and prevented from holding positions of power, they still make less money for the same work as men, and they are overwhelmingly the victims of domestic violence.

There are very few instances of problems that men face specifically, which women don't (or face at much lower proportion), which are not self-imposed (more men in jails is, overwhelmingly, due to more men being violent criminals). You might argue about the draft or issues of being able to be in combat in the military, and there I agree, that should be equal opportunity. However, there hasn't been a draft in 40 years, so unless something big comes up, that's more of a theoretical issue than a practical one.


> Wait a minute. Are you actually aligning yourself with the anti-suffrage movement? Are you serious?

No. (?) All adults should have the right to vote.

> Looks to me like in both absolute numbers and percentages, there are more women than men at the "bottom of society".

You're not looking low enough.

Look at the homeless. Look at homicide victims. Look at workplace deaths (including and excluding the military). Look at high-school dropouts. Look at suicide victims. Look at prisons (both violent and non-violent offenses). It's possible that men are biologically predisposed to violence, but they also live in a culture that coddles women to the detriment of men in need.

> We spend a lot of time and effort on women's issues because, historically, they have been discriminated against and prevented from holding positions of power,

Historically, almost everyone has been prevented from holding positions of power. The tiny circle of powerful people in each country had penises, but that doesn't mean the lives other penis owners were cushy.

Historically, men received significantly more severe punishments for the exact same crimes (still the case), women were given priority over men when provisioning protection and aid (still the case), and men were expected and often forced to perform significantly more brutal and dangerous labor on a daily basis (still the case, though to a lesser extent). As a result, men lived significantly shorter lives, even taking deaths from childbirth into account (still the case, though to a lesser extent).

Interestingly, the fact that men live shorter lives doesn't matter to most people. In fact, it's become the expectation: http://news.nationalgeographic.com/news/2013/04/life-expecta...

Here's a direct quote:

> In the U.S., women live longer—81 years on average, 76 for men—but a recent study by the Institute for Health Metrics and Evaluation reveals a troubling trend. Though men's life spans have increased by 4.6 years since 1989, women have gained only 2.7 years

"Surreal" is again the most fitting word.

> they still make less money for the same work as men,

False: http://www.slate.com/articles/double_x/doublex/2013/08/gende... and http://www.npr.org/blogs/money/2013/09/11/220748057/why-wome... and http://www.politifact.com/virginia/statements/2013/jul/15/te...

> and they are overwhelmingly the victims of domestic violence.

False, and we've known this for some time: http://en.wikipedia.org/wiki/Domestic_violence#Violence_agai...

However, women are overwhelmingly victims of serious injury from domestic violence, as that source does indicate.

Women and men violently attack each other equally; men simply hurt the women more when they do so.

> Please clarify, then, about who exactly is being "silenced"

"Check your privilege!" and "stop mansplaining!" are almost exclusively hurled at men discussing gender, not at women discussing gender, though it is equally applicable to both. Hence my phrase "targeted weapon".

Of course, the notion of "privilege" could be useful. It could be useful to discuss the specific advantages different people have in specific situations, such as female privileges at universities vs male privileges at universities.

Unfortunately, it's almost exclusively employed to bully men into feeling that their objections are automatically invalid and unwelcome unless they conform to specific set of views.

> and what you mean by "silenced" if it doesn't mean that the person is unable to speak publicly about the topic.

Bullying is silencing -- it's one of the reasons that the bullying of the girl in the linked article is a problem.

Bullies don't have to literally sew anyone's mouth shut to dissuade their victims from wanting to speak out again.


Birthday attacks can work against content-based addressing schemes too. Sure, they may be a little bit harder (you need to convince someone to merge something that is able to carry a large random payload), but given that, say, the Linux kernel has a bunch of binary blob firmwares, it wouldn't be too hard for a hardware manufacturer to submit a driver for new hardware with one firmware, and then replace it with another later on.

For a similar example, you may think that generating a CA signing certificate would involve a second preimage attack, as you would need to generate a certificate that had a hash that matched one of an existing CA. But it turns out that you only need a birthday attack, because you just need to submit a certificate for signing that is one of two that collide, where the second one is marked as being a CA cert. This has actually been done a with certificate authority that used MD5 for signing certificates.[1]

There are lots of file formats that allow you to fairly easily create MD5 collisions, by virtue of being able to stick a random string that won't be interpreted somewhere in them.[2] If it were feasible to produce such a collision using SHA-1, anyone who got such a file merged in Git could then substitute it for an evil file and no one would be the wiser.

That said, this attack does require the ability to generate a collision on SHA-1 (which has not yet been done), the ability to convince Linus (or a subsystem maintainer) to pull your tree containing a big binary blob, and that binary blob being able to do something harmful when substituted that it couldn't do just by virtue of being a difficult to audit binary blob (otherwise, why bother with the birthday attack when you could just subvert the blob anyhow).

It's true that the writeup should distinguish between these cases, and contrast their difficulty, but you shouldn't be quite so quick to handwave away the possibility of collision attacks rather than second-preimage attacks.

If I were to build a content-addressed storage system or design Git today, I'd probably use a SHA-2 or SHA-3 hash to be on the safe side. While no one has yet demonstrated a SHA-1 collision publicly, it's been substantially weakened; it just doesn't give a good enough security margin. Current estimate are that finding a collisions would cost about $2.7M in cloud computing time[3], and there are lots of adversaries who have well more than those kinds of resources.

1: http://www.win.tue.nl/hashclash/rogue-ca/ 2: http://www.mscs.dal.ca/~selinger/md5collision/ 3: https://www.schneier.com/blog/archives/2012/10/when_will_we_...


Fair point. Although it's important to note that not any collision attack would work. The collision attack still had to meet certain properties before it could be used to successfully attack x509 certificates. So the ability to use this to succesfully attack a git tree from a cryptographic perspective falls somewhere between a collision attack and a pre-image attack.

Making the binary blob do something useful also assumes that you know enough about the firmware that you could figure out how to create a valid blob as well as a malicious blob. Very often with these binary blobs the low-level detail of the hardware is not generally available except to the manufacturer --- and if the manufacturer were malicious, they could insert the malware into the official firmware image (or to an update of the official firmware image) in the first place.

Finally, the cost estimates in [3] are for a brute force birthday attack, which is definitely not going to be enough for the sort of replacement attack which you are describing. That being said, certainly if we were starting from scratch today, using a newer hash would probably be a good idea. But it's still true that there's a goodly distance from "we can generate a collision" to we can use that to attack a CBA system in real life.


> I grant that this is not a very practical attack, but it can be made arbitrarily hard to detect, based on the threat model the original attacker (who compromised the C compiler) uses.

Not really. The more binaries you have to be able to subvert for it to work, the harder the attack becomes. There are lots of binary diff tools out there, lots of compilers, lots of assemblers, etc. Writing an attack that could detect them all and defeat them all would be so hard as to be impractical; being able to generically recognize something like "this is a compiler" or "this is an implementation of AES" would probably involve solving the halting problem. And if you can't solve it generically, you have to start adding bigger and bigger suspicious binary blobs in which encode all of the patterns for all of the programs you're looking to subvert.

Remember, the NSA does not have infinite resources, nor can they solve unsolveable problems. There is a practical limit to how paranoid you need to be.

Practically, subverting general purpose computation, like subverting a compiler or subverting general purpose instructions on a CPU, is likely to be too easy to detect and too hard to implement to be worth it.

Much easier is subverting a random number generator. That's incredibly hard to detect, and easy to implement. AES encrypting an incrementing counter with a key known only to the NSA looks an awful lot like a random stream, but with that key they can trivially figure out where it is in the stream and what will come next.

That's why Intel's insistence on getting the Linux kernel to blindly trust the RdRand instruction was quite worrying[1], while applying only a bit of paranoia and using David A Wheeler's approach to defeat the trusting trust attack[2] is likely sufficient to have faith in things like your compiler.

1: https://en.wikipedia.org/wiki/RdRand 2: http://www.dwheeler.com/trusting-trust/


You are addressing a completely different issue than the paper did. Yes, the general case is nearly impossibly hard.

But that is not the point. The point is that against a determined adversary, you can not trust an arbitrary program, even if that program is compiled from source, unless you can also trust every other component on your system.

The point then, is to encourage that "bit of paranoia" and make people understand that thinking you're safe just because you can read through the source or have another mechanism for producing or obtaining what you might think is a pristine, safe copy of a piece of software is a false sense of security.

While this particular attack to my knowledge was only a thought experiment and I've never heard of it occurring in the wild, note that at least a few viruses for example propagate by modifying binaries to act as carriers, and often modify the system to obscure their presence (e.g. report incorrect file sizes, and not read back the modified data). This is largely the same threat, and in many ways far more practical because it doesn't require people to take the step of trying to recompile applications.

Having the source (or a "known good" source of your application) does not help you, as your binary is infected when it is handled by the compromised system. Taking checksums etc. on the compromised systems may not help you.


Yes. David A Wheeler did his PhD thesis on this[1], both with some toy compilers to demonstrate that it did detect a trusting trust attack, and eventually bootstrapping gcc using icc, and was able to get it to compile deterministically and verify that it produced identical binaries.

1: http://www.dwheeler.com/trusting-trust/


My convention is usually to clone from the upstream project, thus it winds up being "origin", and then adding my own repository as another remote, named after my username. If there are any other users whose repositories I'm following, I add theirs as other remotes named after their usernames as well, remaining consistent.

That way, when I pull from origin, I'm pulling from whatever the official origin repository is; when I pull from another named repo, it's named after whose repo it is.

It's also frequently the case that I've cloned from upstream before ever forking the repo on GitHub. It's only once I have any changes I need to make that I create a fork and add my own remote.


This is an excellent workflow and then one I use as well.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: