Artyom Pervukhin artyom

Native Secure Enclave backed ssh keys on MacOS

It turns out that MacOS Tahoe can generate and use secure-enclave backed SSH keys! This replaces projects like https://github.com/maxgoedjen/secretive

There is a shared library /usr/lib/ssh-keychain.dylib that traditionally has been used to add smartcard support to ssh by implementing PKCS11Provider interface. However since recently it also implements SecurityKeyProivder which supports loading keys directly from the secure enclave! SecurityKeyProvider is what is normally used to talk to FIDO2 devices (e.g. libfido2 can be used to talk to your Yubikey). However you can now use it to talk to your Secure Enclave instead!

In the olden days, HTML was prepared by the server, and JavaScript was little more than a garnish, considered by some to have a soapy taste.

After a fashion, it was decided that sometimes our HTML is best rendered by JavaScript, running in a user's browser. While some would decry this new-found intimacy, the age of interactivity had begun.

But all was not right in the world. Somewhere along the way, we had slipped. Our pages went uncrawled by Bing, time to first meaningful paint grew faster than npm, and it became clear: something must be done.

And so it was decided that the applications first forged for the browser would also run on the server. We would render our HTML using the same logic on the server and the browser, and reap the advantages of both worlds. In a confusing series of events a name for this approach was agreed upon: Server-side rendering. What could go wrong?

In dark rooms, in hushed tones, we speak of colours.

This page has moved!

Please see here: contour-terminal/vt-extensions

Synchronized Output

Synchronized output is merely implementing the feature as inspired by iTerm2 synchronized output, except that it's not using the rare DCS but rather the well known SM ? and RM ?. iTerm2 has now also adopted to use the new syntax instead of using DCS.

Semantics

ANSI Escape Sequences

Standard escape codes are prefixed with Escape:

Ctrl-Key: ^[
Octal: \033
Unicode: \u001b
Hexadecimal: \x1B
Decimal: 27

stage 1: You believe you can make Go do object oriented programming. You want to do this by using clever struct embedding.
stage 2: You believe goroutines will solve all of your problems. You want to use goroutines for anything and everything that you can, who cares if the code becomes a bit more complicated
stage 3: You believe that instead of object oriented programming, interfaces will solve all of your problems. You want to define everything in terms of interfaces
stage 4: You believe channels will solve all of your problems. You want to do everything from synchronization, returning values, and flow control using channels.
stage 5: You now believe Go is not as powerful as people claim it to be. You feel like you're stripped of all of the nice tools and constructs that other languages provide.
stage 6: You realize that stages 1~5 were all just your imagination. You just didn't want to accept the Go way. Everything starts to make sense.
stage 7: You are now at peace

	package main

	import (
	"bytes"
	"context"
	"encoding/json"
	"errors"
	"flag"
	"fmt"
	"io"

	#!/bin/bash
	set -eo pipefail

	TOKEN=${GITHUB_TOKEN:?environment variable is empty or unset}

	[ -n "$1" ] && GITHUB_REPOSITORY=$1

	GITHUB_REPOSITORY=${GITHUB_REPOSITORY:? please provide a name of a repository}

	OWNER=$(echo $GITHUB_REPOSITORY \| cut -d/ -f1)

	pattern,cnt
	^,1657
	-$,376
	--,355
	root./file.\n,348
	(?m)^hello world,338
	\s+,296
	\s*,278
	^[a-z],275
	[cg]pu,245

	package main

	import (
	"bufio"
	"fmt"
	"net/url"
	"os"
	"regexp"
	"sort"
	"strconv"

	#!/bin/sh -eu
	LOGPIPE=/tmp/logpipe.$$
	mkfifo $LOGPIPE
	logger -t "$0.$$" -f $LOGPIPE &
	exec 1>$LOGPIPE
	exec 2>&1
	rm -f $LOGPIPE
	echo "hello on stdout"
	echo "hello on stderr" >&2
	exec sleep 20