Denis Krivak tetafro

## main.go
package main

import (
	"fmt"
	"log"

	"github.com/hashicorp/vault/api"
)

var client *api.Client

## traceicmpsoftirq.py
#!/usr/bin/python
bpf_text = """
#include <linux/ptrace.h>
#include <linux/sched.h>        /* For TASK_COMM_LEN */

#include <linux/icmp.h>
#include <linux/netdevice.h>

struct probe_icmp_data_t
{

## approle.sh
#!/bin/bash

# start vault
VAULT_UI=true vault server -dev -dev-root-token-id=root -dev-listen-address=127.0.0.1:8200

# login as root - DO NOT DO THIS IN PRODUCTION
vault login root

# write some secrets
vault kv put secret/test color=blue number=eleventeen

## kcgroups.md

      
              1 file
            
          
              9 forks
            
          
              4 comments
            
          
              34 stars
            
          
                mcastelino
                / kcgroups.md
            
            
              Last active
              July 5, 2024 11:53
            
              
                Kubernetes and cgroups Resource Management/Static cpuManagerPolicy/Memory and Resource Isolation & Scheduling
              
          
    Overview

The goal of this document to cover all aspects of Kubernetes management, including how resources are expressed, constrained and accounted for. This started a way to ensure that alternate container runtime implementation like Kata containers will behave from a resource accounting and consumption point of view in the same manner as runc.
Location of the latest version of this document: https://gist.github.com/mcastelino/b8ce9a70b00ee56036dadd70ded53e9f
If you do not understand cgroups please refer to a quick primer at the bottom of this document. This will help you understand how the resource enforcement actually works.
Kubernetes Resource Management


## go-table-driven-tests-parallel.md

      
              1 file
            
          
              13 forks
            
          
              17 comments
            
          
              246 stars
            
          
                posener
                / go-table-driven-tests-parallel.md
            
            
              Last active
              July 10, 2024 13:19
            
              
                Be Careful with Table Driven Tests and t.Parallel()
              
          
    Be Careful with Table Driven Tests and t.Parallel()

We Gophers, love table-driven-tests, it makes our unittesting structured, and makes it easy to add different test cases with ease.
Let’s create our table driven test, for convenience, I chose to use t.Log as the test function.
Notice that we don't have any assertion in this test, it is not needed to for the demonstration.
func TestTLog(t *testing.T) {
	t.Parallel()

  
## clickhousedump
#!/bin/bash

OUTDIR=.

while read -r db ; do
  while read -r table ; do

  if [ "$db" == "system" ]; then
     echo "skip system db"
     continue 2;

## jwt-decode.sh
# will not work in all cases, see https://gist.github.com/angelo-v/e0208a18d455e2e6ea3c40ad637aac53#gistcomment-3439904

function jwt-decode() {
  sed 's/\./\n/g' <<< $(cut -d. -f1,2 <<< $1) | base64 --decode | jq
}

JWT=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ

jwt-decode $JWT

## SSL-certs-OSX.md

      
              2 files
            
          
              85 forks
            
          
              871 comments
            
          
              257 stars
            
          
                croxton
                / SSL-certs-OSX.md
            
            
              Last active
              March 3, 2024 18:58
                — forked from leevigraham/Generate ssl certificates with Subject Alt Names on OSX.md
            
              
                Generate ssl certificates with Subject Alt Names
              
          
    Generate ssl certificates with Subject Alt Names on OSX

Open ssl.conf in a text editor.
Edit the domain(s) listed under the [alt_names] section so that they match the local domain name you want to use for your project, e.g.
DNS.1   = my-project.dev

Additional FQDNs can be added if required:

  
## main.go
package main

import (
	"fmt"
	"log"
	"os"
	"os/signal"
	"syscall"
)

## compress.go
package main

import (
	"bytes"
	"compress/gzip"
	"fmt"
	"encoding/base64"
	"io/ioutil"
)
	package main

	import (
	"fmt"
	"log"

	"github.com/hashicorp/vault/api"
	)

	var client *api.Client
	#!/usr/bin/python
	bpf_text = """
	#include <linux/ptrace.h>
	#include <linux/sched.h> /* For TASK_COMM_LEN */

	#include <linux/icmp.h>
	#include <linux/netdevice.h>

	struct probe_icmp_data_t
	{
	#!/bin/bash

	# start vault
	VAULT_UI=true vault server -dev -dev-root-token-id=root -dev-listen-address=127.0.0.1:8200

	# login as root - DO NOT DO THIS IN PRODUCTION
	vault login root

	# write some secrets
	vault kv put secret/test color=blue number=eleventeen
	#!/bin/bash

	OUTDIR=.

	while read -r db ; do
	while read -r table ; do

	if [ "$db" == "system" ]; then
	echo "skip system db"
	continue 2;
	# will not work in all cases, see https://gist.github.com/angelo-v/e0208a18d455e2e6ea3c40ad637aac53#gistcomment-3439904

	function jwt-decode() {
	sed 's/\./\n/g' <<< $(cut -d. -f1,2 <<< $1) \| base64 --decode \| jq
	}

	JWT=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ

	jwt-decode $JWT
	package main

	import (
	"bytes"
	"compress/gzip"
	"fmt"
	"encoding/base64"
	"io/ioutil"
	)