/** | |
* USB HID Keyboard scan codes as per USB spec 1.11 | |
* plus some additional codes | |
* | |
* Created by MightyPork, 2016 | |
* Public domain | |
* | |
* Adapted from: | |
* https://source.android.com/devices/input/keyboard-devices.html | |
*/ |
There is an increasing count of applications which use Authy for two-factor authentication. However many users who aren't using Authy, have their own authenticator setup up already and do not wish to use two applications for generating passwords.
Since I use 1Password for all of my password storing/generating needs, I was looking for a solution to use Authy passwords on that. I couldn't find any completely working solutions, however I stumbled upon a gist by Brian Hartvigsen. His post had a neat code with it to generate QR codes (beware, through Google) for you to use on your favorite authenticator.
His method is to extract the secret keys using Authy's Google Chrome app via Developer Tools. If this was not possible, I guess people would be reverse engineering the Android app or something like that. But when I tried that code, nothing appeared on the screen. My gues
# Use envFrom to load Secrets and ConfigMaps into environment variables | |
apiVersion: apps/v1beta2 | |
kind: Deployment | |
metadata: | |
name: mans-not-hot | |
labels: | |
app: mans-not-hot | |
spec: | |
replicas: 1 |
#!/bin/bash | |
# Get AWS CLI IAM credentials from LastPass CLI | |
# Blog post: https://paulgalow.com/securing-aws-credentials-macos-lastpass | |
# ############################################################################## | |
# Please adjust those properties | |
readonly lastPassEntry="REPLACE-ME" # Name of LastPass entry that stores your IAM credentials | |
readonly lpass="/usr/local/bin/lpass" # Path to LastPass CLI | |
# ############################################################################## |
We (Mozilla Enterprise Information Security team) are encountering a challenge with trying to connect AWS with our identity provider (Auth0) when calling iam:AssumeRoleWithWebIdentity
We've setup an AWS IAM Identity Provider
- ARN
arn:aws:iam::656532927350:oidc-provider/auth-dev.mozilla.auth0.com/
- Provider type : OIDC
- Provider URL :
auth-dev.mozilla.auth0.com/
- Audience :
xRFzU2bj7Lrbo3875aXwyxIArdkq1AOT
And created an IAM Role with a Trust Relationship policy