Cihat Altuntaş caltuntas

vimgrep

Vimcasts on vimgrep
Uses native vim regexes (which are slightly different from the regexes used by grep, ack, ag, etc) so the patterns are the same as with vim's within-file search patterns.

You can do a normal within-file search first, then re-use the same pattern to

Emoji	Name	Text example
🚀	Rocket	You're up
📦	Package	Installing additional dependencies...
⚓	Hook	Running completion hooks...
📄	Document	Generating README.md...
🎉	Party	Successfully created project hello-vue.
👉	Next	Get started with the following commands:
✔	Tick	Task completed
✨	Magic	Assembling project...

Shell Keybindings

Navigation 🚀

Keybinding	Action
`Alt` + `f/b`	Move cursor to previous/next word
`Ctrl` + `a/e`	Move cursor to beginning/end of command
`Ctrl` + `xx`	Toggle between the start of line and current cursor position

Kerberos cheatsheet

Bruteforcing

With kerbrute.py:

python kerbrute.py -domain <domain_name> -users <users_file> -passwords <passwords_file> -outputfile <output_file>

With Rubeus version with brute module:

Super Guide to the `split-window` tmux Subcommand (and Beyond)

Guide overview

tmux, like other great software, is deceptive. On the one hand, it's fairly easy to get set up and start using right away. On the other hand, it's difficult to take advantage of tmux's adanced features without spending some quality alone time with the manual. But the problem with manuals is that they aren't geared toward beginners. They are geared toward helping seasoned developers and computer enthusiasts quickly obtain the

Tunneling Ethernet Over SSH With Socat and Tap Devices

There are circumstances where one wants to attach the local machine to the same layer 2 ethernet segment, which a remote machine is connected to, with the only available transport being SSH.

While this solution has quite some shortcomings and should not be used to replace a real VPN, it can be beneficial e.g. for debugging network issues remotely.

Life on the Command Line

Stephen Ramsay - Sat, 04/09/2011 - 19:49

A few weeks ago, I realized that I no longer use graphical applications.

That’s right. I don’t do anything with GUI apps anymore, except surf the Web. And what’s interesting about that, is that I rarely use cloudy, AJAXy replacements for desktop applications. Just about everything I do, I do exclusively on the command line. And I do what everyone else does: manage email, write things, listen to music, manage my todo list, keep track of my schedule, and chat with people. I also do a few things that most people don’t do: including write software, analyze data, and keep track of students and their grades. But whatever the case, I do all of it on the lowly command line. I literally go for months without opening a single graphical desktop application. In fact, I don’t — strictly speaking — have a desktop on my computer.

I think this is a wonderful way to wor

I write javascript code. I use CLI for everything I can and Chrome debug tools for everything else. I write code in cli vim, under tmux session.

I normally have tmux sessions (one per project) so I can quickly switch between them without closing/opening new terminal windows, cd'ing, etc.

I also have some automation that allows me to run particular tests from within vim such that it runs in a separate (designated to tests) tmux window.

I really love my setup (even though, at this point, it's probably more out of habit than anything else) and I don't want anything else.

But. The other day I've been pairing with my mate Josh and he kept doing this one thing over and over again and it was such a basic thing, yet such powerful thing at the same time, that I could feel my perfect cli world shaking.

	# Save as ~/.mailcap. Then use run-mailcap to:
	#
	# - open files by `run-mailcap --action=view <file>`, or
	# - view them in the terminal by `run-mailcap --action=cat <file>`.
	#
	# Useful
	#
	# - in mutt by `set mailcap_file $HOME/.mailcap`
	# - in Vim by adding to your vimrc
	#

	(originally written in 2009 and posted to livejournal! https://jdimpson.livejournal.com/6812.html

	The last article teaches how to use socat by comparing it first to cat then to netcat. It skimped on socat's UDP-related features, because netcat only implements a subset of them. This article picks up where the last one left off, with respect to UDP. After this article will be one more that discusses advanced socat features.

	It turns out there are a lot of subleties when dealing with UDP, even before multicast is mixed in. We'll abandon the comparisons to netcat, as we've exceeded what netcat can do. But first a quick reminder of one way socat does UDP.

	socat as a UDP server on port 11111.

	socat STDIO UDP-LISTEN:11111