Skip to content

Instantly share code, notes, and snippets.

@chrisbanm
chrisbanm / netgear-private-key-disclosure.md
Created January 20, 2020 12:25 — forked from nstarke/netgear-private-key-disclosure.md
Netgear TLS Private Key Disclosure through Device Firmware Images

Netgear Signed TLS Cert Private Key Disclosure

Overview

There are at least two valid, signed TLS certificates that are bundled with publicly available Netgear device firmware.

These certificates are trusted by browsers on all platforms, but will surely be added to revocation lists shortly.

The firmware images that contained these certificates along with their private keys were publicly available for download through Netgear's support website, without authentication; thus anyone in the world could have retrieved these keys.

@chrisbanm
chrisbanm / GitHub-Forking.md
Created February 27, 2019 15:40 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

@chrisbanm
chrisbanm / gitaliases.md
Last active July 1, 2019 15:25 — forked from cyberis/gitaliases.md
My Favorite Git Aliases

My Favorite Git Aliases

I use git alot since I prefer the command line for improving developer velocity. A part of that is configuring the tool to do whatever tricks it offers to reduce typing and increase usability. Git is great tool for CVS but sometimes there is a lot to remmeber and a lot to type. Thankfully, git allows you to create aliases for your favorite, most used, or most lengthy commands. Git aliases can even take parameters. So here are few so I don't have to look them up any more.

Git Status Without All the Verbiage (The s Alias)

The git status command produces an aweful lot of output, much of it only interesting to the newbie or under special circumstances (like when you are a bit lost in the code). Observe: