unrelentingfox

#!/usr/local/bin/python3

import base64
import hashlib
import hmac
import json
import os
import requests
import time
import urllib.parse

abajwa-hw

#!/usr/bin/env bash
# Launch Centos/RHEL 7 Vm  with at least 4 cores / 16Gb mem / 60Gb disk
# Then run:
# curl -sSL https://gist.github.com/abajwa-hw/b7c027d9eea9fbd2a2319a21a955df1f/raw | sudo -E sh  

export ambari_password=${ambari_password:-StrongPassword}
export db_password=${db_password:-StrongPassword}
export nifi_password=${nifi_password:-StrongPassword}
export ambari_services="ZOOKEEPER STREAMLINE NIFI KAFKA STORM REGISTRY NIFI_REGISTRY AMBARI_METRICS"
export cluster_name=${cluster_name:-hdf}

bzz

roycewilliams

# 17020 words.
# Goal: recognizable, unambiguous words for most semi-fluent speakers of English.
# Superset of diceware-improved, the GPG wordlist, and BIP-39:
# * https://github.com/heartsucker/diceware
# * https://en.wikipedia.org/wiki/PGP_word_list
# * https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt
a
aardvark
abacus
abandon

DigiTec

Transform a React VR CLI project into an OVRUI project.

To get started npm install -g react-vr-cli for the React VR CLI to make new projects.

Then react-vr init PROJECT_NAME to create a project directory with all of the React VR code.

From here you can copy the below files into the root and they will automatically reference the node_modules versions of THREE and OVRUI.

rogeriopradoj

# include ppa for asciinema
sudo apt-add-repository ppa:zanchey/asciinema
# update registry
sudo apt-get update
# install dependencies
sudo apt-get install python-setuptools python3-setuptools
# finally install asciinema
sudo apt-get install asciinema

peteruhnak

Nautilus Shortcuts Cheatsheet

All shortcut keys are with the Meta key, e.g. F P = Meta+F Meta+P.

Meta key depends on your platform (Ctrl for Linux, Alt for Windows).

Running shortcuts from code editor

Unfortunately when you are in the source code editor, the editor will consume most of the shortcuts which is annoying as **** (some, such as running tests seems to always work though).

jdevoo

"**************************************************************************
 * Allowable characters:                                                  *
 *    - a-z                                                               *
 *    - A-Z                                                               *
 *    - 0-9                                                               *
 *    - .+/\*~<>@%|&?                                                     *
 *    - blank, tab, cr, ff, lf                                            *
 *                                                                        *
 * Variables:                                                             *
 *    - variables must be declared before use                             *

Xarkam

#!/bin/sh

# How to block a scanner on your server for example “w00tw00t.at.ISC.SANS” using $ipt?
# $ipt -I INPUT -p tcp --dport 80 -m string --algo bm --string 'GET /w00tw00t.at.ISC.SANS.' -j DROP

# Check if ran with root permissions
if [ `id -u` -ne 0 ]; then
   echo "The script must be run as root! (you can use sudo)"
   exit 1
fi

jamestalmage

Note: There is a lot of information here, but if I have provided a link, it is probably something you should click on and read. OAuth is a complex enough subject on it's own, and hacking these two services together only adds to it.

Even so, I have found Firebase's API to be simpler than almost any other OAuth solution I have explored. When all is said and done, the important bits of code related to authentication is actually less than 10 lines. If you have ever tried to implement your own OAuth flow before, you know how amazing that is.

In the end, it may be worth using Firebase for authentication, even if that's the ONLY thing you use it for.