Create the Dokku instance:
vagrant up
Configure SSH (see how to enable ~/.ssh/config.d
):
vagrant ssh-config --host 'dokku' > ~/.ssh/config.d/dokku
Create the Dokku instance:
vagrant up
Configure SSH (see how to enable ~/.ssh/config.d
):
vagrant ssh-config --host 'dokku' > ~/.ssh/config.d/dokku
# Scratch pad for working with Milacares API for monitoring and controlling their air purifier devices. | |
# Based on the code from https://www.stefaanlippens.net/oauth-code-flow-pkce.html for PKCE code verifier and challenge. | |
import base64 | |
import hashlib | |
import html | |
import json | |
import os | |
import re | |
import urllib.parse |
#!/usr/bin/env python3 | |
"""Flatpak CLI Shortcut Generator | |
A simple no-argument tool that generates launchers with traditional non-flatpak | |
command names for your installed Flatpak applications in ~/.local/bin/flatpak. | |
Does full collision detection and warns you if you forgot to add its output | |
directory to your PATH. Also overrules the command-line specified in the | |
``.desktop`` file if the Flatpak maintainer didn't include support for | |
command-line arguments. |
Some of the privacy features that I developed in the past are now going to be standard Android features in the next major release. In some cases, the implementation that I worked on ended up being a direct inspiration for the upstream work. I also pushed them to enable permissions review by default, which may have had some influence on it finally shipping as enabled. It was seemingly implemented for some niche scenario and most of their privacy / security team didn't know about the feature existing when I talked to them about it in the past.
Most of my work has focused on improving security, and that focus will be somewhat increased in Android Q due to many of the privacy improvements being part of the baseline OS.
Android P had previously replaced some of the privacy features developed as part of the AndroidHardening project such as restricting access to the camera, microphone and sensors in the background.
Features that were not implemented by my past work:
#include <stdio.h> | |
#include <stdlib.h> | |
#include <unistd.h> | |
#include <netdb.h> | |
#include <netinet/in.h> | |
#include <arpa/inet.h> | |
#include <memory.h> | |
#include <sys/socket.h> | |
/* |
#include <stdio.h> | |
#include <stdlib.h> | |
#include <stdint.h> | |
#ifdef _MSC_VER | |
#include <intrin.h> /* for rdtscp and clflush */ | |
#pragma optimize("gt",on) | |
#else | |
#include <x86intrin.h> /* for rdtscp and clflush */ | |
#endif |
npm config set loglevel http | |
npm config set progress false | |
npm config set package-lock false | |
npm config set save false | |
mkdir -p ~/.config/configstore/ | |
printf '{"optOut": true,"lastUpdateCheck": 0}' > ~/.config/configstore/update-notifier-npm.json |
""" | |
Alex Berke (aberke) | |
Problem: | |
-------- | |
https://www.hackerrank.com/contests/101hack29/challenges/xaero-and-palindromic-strings/copy-from/1300744544 | |
A string is called a palindromic string if it can be read the same going forward as well as backwards. | |
What is the probability of choosing a substring of such that the letters of the chosen substring can be | |
shuffled to make it a palindromic string? |
RCFs we will read!
Terms: https://tools.ietf.org/html/rfc2119
RFC Statuses: https://en.wikipedia.org/wiki/Request_for_Comments
TOTP - https://tools.ietf.org/html/rfc6238 Evil bit - https://tools.ietf.org/html/rfc3514
# Version key/value should be on his own line | |
PACKAGE_VERSION=$(cat package.json \ | |
| grep version \ | |
| head -1 \ | |
| awk -F: '{ print $2 }' \ | |
| sed 's/[",]//g') | |
echo $PACKAGE_VERSION |