AJ ONeal

I believe what's supposed to happen is that Caddy should send a "hello" / "accepted" style packet back, then the client will send SNI + ALPN like a normal TLS...

Looks like I was wrong. The packet is a postgres-specific `SSLRequest`: ```lua postgres_prepare_tls_without_reconnect = function(host, port) -- http://www.postgresql.org/docs/devel/static/protocol-message-formats.html -- 80877103 is "SSLRequest" in v2 and v3 of Postgres protocol local...

Verified: ## Terminal 1 ```sh printf 'S' | nc -l localhost 54321 | hexyl ``` ## Terminal 2 ```sh psql 'postgres://postgres:postgres@localhost:54321/postgres?sslmode=require' ``` ## Result (Terminal 1) ```text ┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐ │00000000│ 00...

FYI: I've submitted a request to Postgres to add `--tls` and `--alpn` options of some sort to the client - in which case the plaintext matching that caddy is already...

Speak of the Zeitgeist! https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d39a49c1e459804831302807c724fa6512e90cf0 This discussed a little over a year ago, and the commits are beginning to land.

More specifically: http://v6.ipv6-test.com/api/myip.php Unfortunately it doesn't support https...

Ah, here we go: https://myexternalip.com/raw ``` curl -6 https://myexternalip.com/raw ``` Beware: there's a sneaky nasty little newline at the end.

Contact Digital Ocean. They host a number of open source projects. I bet this would be worthy of them. https://twitter.com/coolaj86/status/829726921239908353

> Ask, and it shall be given you; seek, and ye shall find; knock, and it shall be opened unto you: 

> The problem with it is that initool isn't written in Go. Oops! Sorry, I had several tabs open as I was surveying the landscape and I got my wires...