kulvind3r

#!/bin/bash
set -e

SCRIPT=$0
ARG=$1
ACTIVITIES_FILE=~/what_next_activities.json

# Colors
RED=$(tput setaf 1)
GREEN=$(tput setaf 2)

kulvind3r

SSL Certs Cheatsheet

A quick guide to do all things certificate related.

1. Self signed certificate and private key

Ready to use self signed certificate with SAN extensions.

openssl req -x509 -newkey rsa:4096 -sha256 -days 365 -nodes \
-keyout app.domain.com.key -out app.domain.com.cer \

-subj /C=IN/ST=MH/L=PUN/O=TW/OU=IT/CN=app.domain.com \

kulvind3r

KeePass - Password Manager for Masses

Conventional wisdom recommends using a unique, randomized, long password for each set of credentials you setup for your use. It increases security and prevents loss of multiple accounts if any one account gets hacked thereby leaking your creds.

Conventional wisdom fails to say anything about remembering these unique long hieroglyphs. How very convinient for conventional wisdom.

The solution to this problem, like every other problem is to make it someone else's problem. In this scenario, a password manager's.

A password manager is a software that does the job of generating such unique randomized passwords for you, storing them and giving them to you when you need them, like an obedient lackey. In return all you have to do is to remember the one password for the Password Manager.

kulvind3r

#!/bin/bash
set -e

SCRIPT=$0
ARG=$1

BASE_VERSION="0.1"

validation_error() {
  echo "Not inside a git repo. Exiting."

kulvind3r

#!/bin/bash
set -e

ARG="$1"
WORK_DIR=$(pwd)

run() {
  for DIR in $(find $WORK_DIR/ -maxdepth 1 -type d)
  do
    cd "${DIR}"

kulvind3r

#!/bin/bash
set -e
SCRIPT_NAME=$0
OPT=$1
FILES_PATH=$2
PASSPHRASE=$3

usage() {
  echo -n "${SCRIPT_NAME} [OPTIONS] [FILE_PATH] [PASSPHRASE]