Anyone happen to know how he's getting archey output to be colour for the Apple logo? my iTerm and Terminal is just in white/black.
Probably using an alternate shell like zsh
OS X Command Line Utilities
161–170 of 210 posts
Re: OS X Command Line Utilities
#162I use: open vnc://myServer.local It will open up the screen sharing app and connect for you :)
One of my favorite tricks when I learned it, because I was already in the terminal, no need to reach over for the mouse to remote into a wallboard via screen sharing.
Re: OS X Command Line Utilities
#163Earlier quoted context omitted.
Yes, I know. But telling someone to "chill out" is a jab and superfluous. People do this kind of thing in online comments all the time, to make the other person look bad and rub in a little extra insult. Any one comment isn't much, of course, but they compound into a degraded discourse, and all of it goes against the civility we try to practice here.
Fair enough. I didn't want you to think he was doxing someone.
Ah, I see. Probably should've left Winston out of this :)
Re: OS X Command Line Utilities
#164Anyone happen to know how he's getting archey output to be colour for the Apple logo? my iTerm and Terminal is just in white/black.
archey -c
Re: OS X Command Line Utilities
#165Re: OS X Command Line Utilities
#166Re: OS X Command Line Utilities
#167I'm surprised they didn't mention anything about the command line utilities to manage the mac's airport (scan for wireless networks, list network interface names, etc). I did a quick blog post about these a while back: http://blog.mattcrampton.com/post/64144666914/managing-wifi-...
Re: OS X Command Line Utilities
#168Remove unwanted formatting from text in the clipboard: alias pbclean='pbpaste | pbcopy'
this is pretty cool, added it to my .bashrc
Re: OS X Command Line Utilities
#169Earlier quoted context omitted.
I aliased Sublime to `sub`. Without args it opens the current folder as a project; with args it opens the file[s].
The officially-supported name is `subl`, by the way: https://www.sublimetext.com/docs/2/osx_command_line.html
Huh. I clearly didn't research before I wrote my one-liner. This is certainly a little more ... documented.
Thanks for the heads up!
Re: OS X Command Line Utilities
#170Earlier quoted context omitted.
That's pretty terrible opsec. It presents a risk to separation of roles / compartmentalization if a coworker can walk over to your workstation and have access to it, to say nothing of malicious access by somebody who shouldn't be in the office in the first place.
If locking your computer in the office is required opsec, then you have already lost. First, you shouldn't have random people walking around the office. Once someone has physical access the battle is already over. Second, rogue employees are still rogue employees, and an unlocked computer is the least of your worries. With that said, I always lock my computer out of habit.
Not sure what size company you're working in nor what the requirements for opsec are their nor your privilege levels but it certainly does not mean you have already lost.