vncsna

set -e, -u, -o, -x pipefail

The set lines

• These lines deliberately cause your script to fail. Wait, what? Believe me, this is a good thing.
• With these settings, certain common errors will cause the script to immediately fail, explicitly and loudly. Otherwise, you can get hidden bugs that are discovered only when they blow up in production.

• set -euxo pipefail is short for:

set -e
set -u

johnwgillis

How to setup GPG for signing commits with Git, SourceTree, and GitHub on Mac

1. Install GPG tools
   1. Install GPG tools and setup pin entry by running:

   brew install gnupg pinentry-mac
   mkdir -m 700 -p ~/.gnupg
   echo "pinentry-program /usr/local/bin/pinentry-mac" >> ~/.gnupg/gpg-agent.conf
   killall gpg-agent
   

jonjack

Using an Access Token for the first time

Follow the instructions on Github to Create an Access Token in Github

Configure Git to use the osxkeychain

By default, git credentials are not cached so you need to tell Git if you want to avoid having to provide them each time Github requires you to authenticate. On Mac, Git comes with an “osxkeychain” mode, which caches credentials in the secure keychain that’s attached to your system account.

You can tell Git you want to store credentials in the osxkeychain by running the following:-

it-sec-std

Security event log format and specs review

Sources

Specs

• ArcSight CEF guide
• Common Event Format Configuration Guide F5 Networks
• Common Event Format ArcSight, Inc.
• CEF Imperva Secure Sphere
• Syslog message formats: CEF&LEEF

slav

package main

import "fmt"

func f(c chan func() (int, string)) {
	c <- (func() (int, string) { return 0, "s" })
}

func main() {
	c := make(chan func() (int, string))

samiraguiar

Note for newcomers:

In the shortcuts below, "C" stands for CTRL and "A" stands for "ALT". This is a convention
used in the Midnight Commander documentation and was kept here.

You can also use "ESC" instead of "ALT", which is useful on Macbooks.

Main View
---------------------------------------------------------------
- File/directory operations

Chaser324

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

kevin-smets

Default

Powerlevel10k