Adam Brady SomeoneWeird

Tesla Key Card Protocol

Researched by Robert Quattlebaum [email protected].

Last updated 2020-02-03.

Muh Switch Keys

So you want to decrypt switch content ? Well, the good news is that all the tools required to do that are written up! The great news is, since this is crypto we're talking about, you'll have to find the keys. Yourself. Like it's easter.

So here you can find a template of the $HOME/.switch/prod.keys file that hactool uses to decrypt content. It contains all the SHA256 and location of the keys and seeds, so you can find them yourselves.

Note that all the seeds (the keys that end with _source) are used along with the master_key_## to derive an actual key. If you have somehow obtained the key without the seed, you can rename xxx_source to xxx_## (where ## is the master key number) and put your key there.

How the heck do I obtain dem keys ?

I'm hosting a private Rust game. All players are welcome but especially those from the coding communities I belong to.

PvP will be encouraged but shaped to occur on weekends and certain weeknights or holidays, as appropriate. PvE will be off initially but turned on when required to enforce this.

I've created https://twitter.com/aest_afterdark to communicate game changes and interact with player pop. Please follow it if you use twitter and use this for server news.

Connection

To connect, start your Rust game, press F1 and type client.connect 45.121.209.83:49285 then hit enter.

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

I've known people at nodejitsu for years, since before the company even existed. I still consider many of them friends. That said, somebody over there has lost their mind.

Trademarks are an important part of open source. They protect the integrity of the trust that is built by any project. A classic example of why this is the case is Firefox. Suppose that a malware producer takes the Firefox codebase, which is free and open source, packages up their malware with it and then releases it as "Firefox". Then they buy search advertising and suddenly their bad and malicious version of Firefox is the first result on search engines across the web. This is clearly a bad thing for Firefox and open source everywhere, but what can Mozilla do to protect their community of users?

They can't enforce a software license since the use is permitted under the Mozilla Public License. They can, however, enforce on these hypothetical bad actors using their trademark on the word "Fi

Description

This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.

The script is here:

#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"

	const repl = require('repl');
	const babel = require('babel-core');

	function preprocess(input) {
	const awaitMatcher = /^(?:\s(?:(?:let\|var\|const)\s)?\s([^=]+)=\s\|^\s)(await\s[\s\S]*)/;
	const asyncWrapper = (code, binder) => {
	let assign = binder ? `global.${binder} = ` : '';
	return `(function(){ async function _wrap() { return ${assign}${code} } return _wrap();})()`;
	};

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else

	const merge = (obj, src) => {
	let res = obj;

	for (let k of Object.keys(src)) {
	if (res[k] === src[k]) {
	continue;
	}

	if (typeof src[k] === 'object' && src[k] !== null && src[k].constructor === Object) {
	let sub = res[k];

	ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key
	# Don't add passphrase
	openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub
	cat jwtRS256.key
	cat jwtRS256.key.pub