| import os | |
| import re | |
| import subprocess | |
| from bs4 import BeautifulSoup | |
| import rules | |
| def replacer(url, html): | |
| new = html | |
| reload(rules) |
| #!/bin/bash | |
| # <https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3> | |
| echo -e "\n\nArch Linux ARM to SD Card" | |
| echo -e "For the Raspberry Pi 3, if you want to use the unofficial arm64 variant." | |
| echo -e "(Otherwise use the Raspberry Pi 2 version of this script!)\n\n" | |
| if [[ $EUID -ne 0 ]]; then | |
| echo "This script must be run as root" 1>&2 |
Chrome ExtensionのLive HTTP Headersを調査した。Firefox用のものではない。Firefox用のものではない。
11/7追記
- 類似 or 同様の方法で難読化scriptを埋め込んでいる拡張機能が大量にあったため、Googleに報告済み。
- https://twitter.com/bulkneets/status/795260268221636608
Summary in english.
| #!/usr/bin/python | |
| import sys | |
| import hashlib | |
| from OpenSSL.crypto import * | |
| def main(): | |
| if(len(sys.argv) != 4): | |
| print sys.argv[0] + " /path/to/ssl.crt /path/to/ssl.key ProcessedMachineIdentifier" | |
| sys.exit(0) |
| # ANSI color codes | |
| RS="\[\033[0m\]" # reset | |
| HC="\[\033[1m\]" # hicolor | |
| UL="\[\033[4m\]" # underline | |
| INV="\[\033[7m\]" # inverse background and foreground | |
| FBLK="\[\033[30m\]" # foreground black | |
| FRED="\[\033[31m\]" # foreground red | |
| FGRN="\[\033[32m\]" # foreground green | |
| FYEL="\[\033[33m\]" # foreground yellow | |
| FBLE="\[\033[34m\]" # foreground blue |
Below you is my build instructions for GnuPG 2.1.20 released on 03-Apr-2017. These instructions are built for a headless Ubuntu 16.04 LTS server.
Or if you wish, you may use the install script to install GnuPG 2.1.20 by entring the following:
curl -sL "https://gist.github.com/mattrude/3883a3801613b048d45b/raw/install-gnupg2.sh" |shapt-get -y install libgnutls-dev bzip2 make gettext texinfo gnutls-bin \
| OLD stuff. This was not enough for an A+ anymore. |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".