ynoclo

crt.sh reports that JPL's wildcard certificate was revoked on 2019-01-15: https://crt.sh/?id=273042821

"I'm good at communicating." Really? If I were your prospective employer, I'd be wondering just how often the f-bomb finds its way into your communications, and why you thought it was appropriate to drop twice in a job appeal. Please take this as a constructive criticism of your approach.

Not a hiccup, apparently -- their Verisign-issued EV cert is still revoked. Things look ok to users because they're now using a GoDaddy wildcard domain cert.

iTerm2 and MacVim are now my primary tools (IMO, Xcode 4 has lost the plot as a useful IDE.) You can define the behaviour of :make in vim, plus there are a variety of vim plugins that turn it into a complete development environment.

git for source code management; gdb for debugging. bash can do anything I need it to; never really got into zsh.

Dock seems more customizable and immediate than Launchpad. The way Launchpad takes you completely out of your current context is really distracting to me.

BTW, the Dock should always go on the left or right edge, rather than the bottom of the screen, so windows use the maximum vertical height.

RFC2818 (the 'HTTP over TLS' specification) says that names may contain the wildcard character, which is considered to match any single domain name component or component fragment. E.g., ＊.a.com matches foo.a.com but not bar.foo.a.com. f＊.com matches foo.com but not bar.com.

A careful reading of this wording does not seem to rule out the use of more than one wildcard, e.g. '＊.＊.com'. That's unfortunate. It likely depends on the particular browser's TLS implementation as to whether more than one wildcard in a name would be processed.

I want to use vim as my IDE, so my favorite plugins are the ones that integrate the functionality you'd expect in a development environment.

- 'NERD_tree': provides a hierarchical directory view in a sidebar (much like a project view); open a file by hitting enter, or by double-clicking in MacVim

- 'a': toggle quickly between a source file and its header

- 'cscope_maps': search through my cscope-indexed source files and system headers

- 'fuf' and 'l9' (a.k.a. FuzzyFinder): quick way to open files, auto-completing as you type

- 'tagbar': displays navigable list of functions/methods in a sidebar (better than the old 'taglist' plugin)

This could work if you are always forced to enter the full password to start a login session. The "PIN" password's hash could be generated at that point and held in protected memory (e.g. by a root process); it would go away on logout, as well as after some small number of failed attempts.

As to whether it's a good idea, that's debatable: if you want to solve the problem of being prompted for an admin password many times to perform tasks, a better answer might be to prompt once and get some sort of authorization ticket which allows the user to do a particular task without entering a password until the ticket expires.

Actually, the cert does apply, because 'github.com' is explicitly listed in the subjectAltName extension. (Names in that extension are considered valid alternatives to the common name in the subject; see RFC 5280 4.2.1.6.) It really is a wget bug, or more likely an OpenSSL bug.

Swing Theory has also been attacked, despite a resurgence of popularity in the late '90s... which, coincidentally, was 12 years ago.

A good overview, but some bad examples. For 'find', he says:

<I>Combine with grep to find c++ files.

$ find | grep cpp</I>

That has at least two problems: 1. It will match 'cpp' anywhere in the name, such as 'tcpping.py', resulting in false positives. 2. It's inefficient, as there's no need to invoke grep at all. Much better just to use:

$ find . -name "*.cpp"

I also prefer dashed zeroes. And the curly lowercase 'l' in Menlo really bothers me (the creator of Mensch got it right, IMO, by straightening it out.) Obviously this isn't a poll, but if it were, I'd vote for Inconsolata-dz. :)

On OS X, it is possible to disable just Etisalat's Comtrust certificate. Click the lock icon to view that certificate, drag the large certificate icon to your desktop, then drag it into Keychain Access (i.e. into your login keychain). At that point, you can set the trust settings on that certificate to Never Trust.

This article is disingenuous in that it doesn't mention the "Secure Empty Trash" menu item which is located directly below "Empty Trash". There is no need for this product, as the functionality is already built into Mac OS X.

The app you're looking for is called 'screen'. You can set it up to display a number of split screens in one window, each running a different app like htop. The settings are saved in ~/.screenrc. Try searching for "screenrc examples" to get started.

I think you just answered your own question.

No, not everyone's phone number. You could opt to have an "unlisted" number, and it was easy to check whether or not the book was revealing your number to the world.

Unfortunately, it's kind of a deal-breaker that each Mac OS X guest burns 100% CPU all the time. This is mentioned in the new user guide as something which will be fixed in a future release.

If the client is on Mac OS X, why do they need to create a zip file at all? You can use something like DropDMG <http://c-command.com/dropdmg/>; to create an encrypted .dmg file by dropping files/folders on it. Alternatively, if the client is on Windows, have them use a Windows ZIP utility, and then unzip on the Mac side with The Unarchiver <http://www.apple.com/downloads/macosx/system_disk_utilities/....