4,320 karma · joined June 27, 2011
Recruiters, HR, hiring managers, etc.: I've been trying to make a success out of something for several years. I intend to keep at it until it works, explodes, or I have a complete nervous breakdown. If you're trying to fill a position before 2012, I'm probably not your guy.
I think there's a sense, which I generally agree with, that random applications asking for your password is something we don't want users to get used to.
Only the first flight did anything close to "blow up", and the payload was recovered largely structurally intact (sensitive components irreparable). It would almost certainly have been survivable in an LES-equipped capsule.
Flights 2 and 3 were prevented from reaching orbit but did not blow up, catch fire, or do anything else that would have precluded a safe, if rather early, return of the crew.
Groupon's business model was ridiculous from the beginning, and they actively engaged in attempts to manipulate their earnings numbers.
Facebook's model is fundamentally unremarkable and quite similar to a number of other profitable companies. You can question the strategy and execution, but the general model is known to work. Here questions are being presented about how forecasts were handled in the run-up to the IPO. Based on what we know/suspect, the underwriters would necessarily be implicated in any actual wrongdoing, but there is thus far little evidence to suggest Facebook made any sort of Groupon-like manipulation or coverup attempt. It can and should be investigated, but we're a long way from torches and pitchforks on Zuckerberg's front lawn.
It should take five minutes for them to learn the basics of public key crypto so that their eyes don't glaze over when you say "public key", "private key", "fingerprint", or "RSA". I consider this basic knowledge absolutely essential for anyone using these concepts, even indirectly. Without it, you're dangerous.
Once those concepts are in place, it shouldn't even take five minutes for them to understand what SSH is doing, because SSH is a very simple and obvious application of the concepts. It should be self-evident from the brief discussions in github's instructions what is going on.
And once you've taken the five minutes to understand the concepts, not being dangerous is likewise simple and obvious:
* Put a good passphrase on your key.
* Don't share your key with others.
* Don't type in the passphrase for your key on any computer you don't trust at least as much as your own.
Notice how these aren't fundamentally different from protecting a password.
We are talking about inherently intelligent people with a good capacity for learning. It is mind-boggling to me that anyone would argue that these people should not have to spend five minutes to understand at even the most basic, limited level, how critical tools they want to use work.
I truly, TRULY have no problem with making key generation push-button. I really don't. I have a very BIG problem with people who don't understand it pushing that button.
But you're right, I give up. All I can do is ensure that these people who demand of themselves nothing but the most disgusting of human characteristics -- willful ignorance -- do not come anywhere near my systems or projects.
Not a problem following the instructions -- such a failure is clearly outside their scope.
You also conveniently ignore the reality that if they don't have permissions to install it... They're not supposed to be installing it in the first place. Report them to their corporate IT department, you'll be doing everyone a favor.
> When they get to the line ending conversions part; what if they don't understand the options and abandon the process?
Purely hypothetical. But if they give up that easily, yes, I consider it PEBKAC. People must take responsibility for their own ignorance and laziness.
> Even though the instructions are nicely laid out, not everyone is accustomed to the command line.
It. Is. Text. Read it. We read every day, we type every day. This is not difficult. Fear of the command line is irrational, which is exactly why I excluded it.
More fundamentally, you had SSH keys and no understanding of what they were for? Sorry, but this is exactly what I'm talking about. You are choosing to use systems you have no understanding of, and taking no time at all to learn about them. You are dangerous.
Then they cannot use the system safely and should walk away.
> I still have no idea what the 'randomart' images are about.
First result for "ssh randomart" in Google:
http://superuser.com/questions/22535/what-is-randomart-produ...
So long as you're unwilling to learn, very simple things will forever elude you.
> I don't see any benefit to all of that over having a button marked "make keys" which just gets me set up so I can use github.
It's not that the form has any strong benefit in itself, it's that if you understand what is going on, which is required for security, the text form is in no way mysterious, complicated, or intimidating. The GUI isn't fixing anything, it's just masking a serious problem with the user.
I also like being told where semi-automated processes are placing critical files on my filesystem. I'm surprised that annoys you.
One can perform the act of driving a car without any understanding of what the engine does, but if you lack any understanding of what it does, you're going to park it in a closed garage, leave it running, and kill yourself or someone else because you were too afraid of scary mechanical stuff to learn.
If you can't be bothered to learn about public key crypto, someone's going to social engineer your key out of you without you having any clue what happened.
It's not trying to describe a "ground-shaking vulnerability". There is a current, known issue with display of git signature verifications, and he's including it in his article. That's not the point of the article.
The point is an exploration of options for securing your repository history. That's it.
Various strategies are used to specifically protect all kinds of sensitive systems far beyond simple network security. This article is a detailed exploration of a/some strategy/ies for protecting your git repository against malicious modification -- a scenario that is rare but far from unprecedented.
Seriously guys, you're not even trying. Here are the instructions everyone is freaking out about, they contain an explanation of this very issue.
Please, bring me someone who actually had trouble with those instructions, and not because they freaked out at the first sign of a command line. They must have actually read them, including the expandable bits, made a serious effort to follow them, and failed.
You're not even trying. Physical access, game over, the lock is irrelevant.
You fear what you don't understand, and you don't understand because you're afraid to learn. You have simply crafted a vicious cycle for yourself, and are making the world that much more unsafe by spreading your fear and acting as if everyone should share in your fear.
nknight@unassigned-hostname:~$ ssh-keygen -t rsa -C "foo@example.com"
Generating public/private rsa key pair.
Enter file in which to save the key (/home/nknight/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/nknight/.ssh/id_rsa.
Your public key has been saved in /home/nknight/.ssh/id_rsa.pub.
The key fingerprint is:
d3:c0:19:ae:5b:ff:46:fd:a0:b5:9c:a2:93:a4:ca:c2 foo@example.com
The key's randomart image is:
+--[ RSA 2048]----+
| . |
| o o |
| = |
| . o |
| . S . . |
| o o. . + |
| . . o.o + = |
| E. . o.+ + .|
| .o. .+.. |
+-----------------+
nknight@unassigned-hostname:~$
Read. READ. Comprehend. Don't throw your hands up and say "But it's sooooo confusing!". It's not. It's very simple, and it is not possible to simplify further, no matter how you try to dress it up in eyecandy, you still must read and comprehend the exact same concepts. If you do not, you cannot be secure. Ever. The basic concepts of public key crypto are mandatory knowledge for everybody.Get over your irrational fear and you will have no more trouble than you would reading a technical book.
If you view a theory as human understanding of reality, the only reason an experiment would be fundamentally flawed (as opposed to forgetting to carry the 2) is if the understanding, and thus theory, is wrong or at least incomplete.
SSH is one of the easiest security tools to use safely that has ever existed. I would say it is second in usability only to HTTPS in browsers, while having a much better actual security record, and is infinitely more powerful, while keeping basic operation so simple I once taught my mother to use it.
I am 100% confident that anyone competently engaged in development or systems administration can understand the basic concepts and operations of SSH in five minutes. Any fear of it is irrational. It is not hard, it was specifically designed not to be hard.
I'm equally confident you've not taken the five minutes to understand these relevant concepts, because your statement about setting up a "safe" environment makes no sense in the context of OpenSSH. The defaults are inherently safe, as they should be. You must take specific actions to make the system unsafe.
Everything you've said in this thread has been bang-on, and the replies you're getting are deeply depressing.
These guys aren't totally green, they have multiple working prototypes/pilots, the software is done, manufacturing is ready. This isn't really much different from any other pre-order. They're saying "The product is tested and ready, give us money to buy a bunch of parts and put them together."
Historically, I don't think this would come up as much in copyright law. General torts often involve a confluence of events triggered by multiple actors, whereas copyright violations have usually been clearly the act of a single person or entity, so I'm not sure there's much case law around this.
I don't claim to be a design guru, but it looks like somebody was going for minimalism, but used a nuke instead of a scalpel. My eyes don't know what to focus on, there's limited indication of what things are, and in places it's hard to tell at a glance where one component ends and the next begins.
It's not so much ugly as it is intensely vague and somewhat undiscoverable.
Edit: Just to be clear, I don't want this to be seen as a criticism of this app or its developers specifically, I'm operating under the impression I'm getting from other commenters that this is very Windows 8-ish in general, so take this as bewilderment at the Windows 8 style.