Frick

function openfiles {
    if [ "${1}" = "-h" ]; then
        echo -e "Usage: openfiles [r|w|m|R|W] regex\n    -r    opened for reading or read/write\n    -w    opened for writing or read/write\n    -m    accessed from memory (includes running command)\n    -R    opened for reading only\n    -W    opened for writing only"
        return
    fi
    if [ "$#" = "0" ]; then
        echo "Process signature/regex required."
        return
    fi
    MODE="(w|u)"

Frick

function listening {
    if [ "${1}" = "-h" ]; then
        echo "Usage: listening [t|tcp|u|udp] [ps regex]"
        return
    fi
    DISP="both"
    NSOPTS="tu"
    if [ "${1}" = "t" -o "${1}" = "tcp" ]; then
        DISP="tcp"
        NSOPTS="t"

toringe

#!/usr/bin/env python
#
# Example 1: All blocks in list.txt, one CIDR per line
#   cat list.txt | cidr.py
#
# Example 2: Echo CIDR blocks to stdout
#   echo 1.2.3.0/25 1.2.3.128/25 | cidr.py

import sys
from netaddr import *

Faheetah

node {
    echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1'
    echo 'No quotes, pipeline command in single quotes'
    sh 'echo $BUILD_NUMBER' // 1
    echo 'Double quotes are silently dropped'
    sh 'echo "$BUILD_NUMBER"' // 1
    echo 'Even escaped with a single backslash they are dropped'
    sh 'echo \"$BUILD_NUMBER\"' // 1
    echo 'Using two backslashes, the quotes are preserved'
    sh 'echo \\"$BUILD_NUMBER\\"' // "1"

ursuad

Kafka Topics

List existing topics

bin/kafka-topics.sh --zookeeper localhost:2181 --list

Describe a topic

bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic mytopic

Purge a topic

bin/kafka-topics.sh --zookeeper localhost:2181 --alter --topic mytopic --config retention.ms=1000

... wait a minute ...

technion

References on modern password policies

Below links provide source, reference link and relevant quote

Standards

NIST

https://github.com/usnistgov/800-63-3/blob/nist-pages/sp800-63b/sec5_authenticators.md

Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically).However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

Major organisations

dend

function Show-Notification {
    [cmdletbinding()]
    Param (
        [string]
        $ToastTitle,
        [string]
        [parameter(ValueFromPipeline)]
        $ToastText
    )