HNHacker News
TopNewBestAskShowJobs

nknight

4,320 karma · joined June 27, 2011

I do server-side development and operations. When lacking other experienced developers, I'll step in on embedded Linux stuff, to.

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.

submissionscomments
nknight··on Mark Zuckerberg sells 30.2 million shares of $FB common stock at $37.58
That's only partly true. As I recall, he exercised a substantial option (~100 million shares or something like that), half of which were non-qualified and are immediately taxed as ordinary income, so he's got a big tax bill coming and probably will keep less than half of what he just cashed out.
nknight··on The security hole in sudo
If you're having this kind of problem a lot, now might be an excellent time to start using a lint tool in your development process. It'll catch these things.
nknight··on The security hole in sudo
I have, but it was a patched version.

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.

nknight··on SpaceX Falcon 9/Dragon Launch Webcast (starts at 12:00am PDT)
> blowing up their first three Falcon 1 flights

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.

nknight··on Facebook Bankers Secretly Cut FB Revenue Estimates In Middle Of IPO Roadshow
You don't need to.

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.

nknight··on GitHub for Windows
Two different issues got mixed together here, and I wasn't good at distinguishing them in my comments.

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.

nknight··on GitHub for Windows
I'm angry at willful ignorance and attempts to justify it.

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.

nknight··on GitHub for Windows
> The installer keeps failing for some unexplainable reason.

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.

nknight··on GitHub for Windows
It tells you to back them up, that makes it an inconvenience in the worst case, not dangerous.

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.

nknight··on GitHub for Windows
> They don't know, or care what a fingerprint is.

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.

nknight··on GitHub for Windows
All sorts of things can be done without any user intervention, but if the user doesn't understand how it works, they can't use it safely, and they are a danger to themselves and those around them.

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.

nknight··on A Git Horror Story: Repository Integrity With Signed Commits
It's a detailed exploration of git object signing.

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.

nknight··on A Git Horror Story: Repository Integrity With Signed Commits
Corporate networks get broken into all the time. Any machine that a copy of the repository is stored on is a potential attack vector.

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.

nknight··on GitHub for Windows
This is why you protect it with a passphrase, which SSH asks you to do by default. Choose a good passphrase, it's encrypted on disk, and decrypted only as needed.

Seriously guys, you're not even trying. Here are the instructions everyone is freaking out about, they contain an explanation of this very issue.

http://help.github.com/win-set-up-git/

nknight··on GitHub for Windows
http://help.github.com/win-set-up-git/

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.

nknight··on A Git Horror Story: Repository Integrity With Signed Commits
> just plain forgetting to [lock] you PC when you go to the toilet

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··on GitHub for Windows
There is no UX issue, it's entirely an irrational fear of having to read. Putting it in a GUI accomplishes nothing but clutter the screen with irrelevant crap.

    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.

nknight··on GTar: The First Guitar That Anybody Can Play
It seems like they're using the iPhone for pretty much all intelligence, which makes sense. Custom embedded systems are non-trivial to design, manufacture, and bootstrap software for (I've been involved in some capacity with several). You'd save significant effort and trivially enable many more features by relying on something as powerful and mature as an iPhone.
nknight··on GTar: The First Guitar That Anybody Can Play
At least on the prototypes they're showing, that whole panel appears to easily unscrew. I could see it possibly being practical to replace with a more accommodating piece for a few tens of dollars.
nknight··on Feynman’s science lesson for entrepreneurs: Challenge authority.
I think that tries to draw too bright a line between theory and experiment.

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.

nknight··on Feynman’s science lesson for entrepreneurs: Challenge authority.
It'd be remarkably impressive if it was a new video, considering Feynman's been dead 24 years.
nknight··on GitHub for Windows
Here's the fundamental problem. If you can't understand very basic security tools and concepts, you cannot securely operate a computer, much less hope to ever write secure code.

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.

nknight··on GitHub for Windows
It's not insulting to point out that the instructions are very simple, easy to follow, and easy to understand. Everyone here is smart enough to understand these things, and it's utterly bewildering that they angrily refuse to spend 5 minutes learning about something new in order to use something new.
nknight··on GitHub for Windows
No, he isn't, and the relevant Wikipedia article is very poorly written. PKI is a highly generic term. Webs of trust are just as much a PKI as a certificate-based system.

Everything you've said in this thread has been bang-on, and the replies you're getting are deeply depressing.

nknight··on GTar: The First Guitar That Anybody Can Play
But why would you be looking at the iPhone screen other than when interacting with it using said hand?
nknight··on GTar: The First Guitar That Anybody Can Play
While more money is at stake, I'd say the risk is actually substantially lower unless they're lying about everything (I have no reason to believe they are).

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."

nknight··on Supreme Court Lets Stand Student's $675,000 Penalty For Downloading
In areas of tort liability, it's routine for there to be a determination that party A is liable for X%, B is liable for Y%, etc..

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.

nknight··on GitHub for Windows
I don't actively use any git GUI client, but my reaction is to the style in general rather than anything git-specific.

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.

nknight··on GitHub for Windows
Are you serious? I ask this out of genuine ignorance, knowing only a little of what has gone on in the Windows world the last ~4 years. This is what Windows 8 apps are supposed to look like?
nknight··on Microsoft launches so.cl
In my mind, LiveJournal (April 1999) is the first really successful "social network". And as far as I can tell, it's the oldest one of any particular significance that still operates.
← PreviousPage 2 of 34Next →