Building a Transparent Keyserver

#1

Post by noident » Fri, Dec 19, 2025, 2:54 PM UTC

Building a Transparent Keyserver
words.filippo.io

Re: Building a Transparent Keyserver

#2

Post by noident » Fri, Dec 19, 2025, 2:54 PM UTC

Filippo Valsorda discusses his server for storing age keys

Re: Building a Transparent Keyserver

#3

Post by xeonmc » Fri, Dec 19, 2025, 4:18 PM UTC

noident wrote: post #2

Filippo Valsorda discusses his server for storing age keys

At first glance I misread this as "stone age keys" and thought it was a dig at gpg

Re: Building a Transparent Keyserver

#4

Post by notyourancilla » Fri, Dec 19, 2025, 4:29 PM UTC

> The author pronounces it [aɡe̞] with a hard g, like GIF, and is always spelled lowercase.

Of all the words we could've used to explain how to pronounce something

Re: Building a Transparent Keyserver

#5

Post by Thom2000 » Fri, Dec 19, 2025, 4:29 PM UTC

I wonder if they think of a deeper integration of this into the age binary. Currently the invocation looks extremely ugly:

    age -r $(go run filippo.io/torchwood/cmd/age-keylookup@main joe@example.com)

Re: Building a Transparent Keyserver

#6

Post by akerl_ » Fri, Dec 19, 2025, 4:38 PM UTC

Thom2000 wrote: post #5

I wonder if they think of a deeper integration of this into the age binary. Currently the invocation looks extremely ugly: age -r $(go run filippo.io/torchwood/cmd/age-keylookup@main joe@example.com)

I assume once it's stabilized you'd swap the `go run` for just installing and using a binary, similar to what you're already doing with age.

Re: Building a Transparent Keyserver

#7

Post by FiloSottile » Fri, Dec 19, 2025, 4:59 PM UTC

notyourancilla wrote: post #4

> The author pronounces it [aɡe̞] with a hard g, like GIF , and is always spelled lowercase. Of all the words we could've used to explain how to pronounce something

>:)

Re: Building a Transparent Keyserver

#8

Post by FiloSottile » Fri, Dec 19, 2025, 5:08 PM UTC

akerl_ wrote: post #6

Thom2000 wrote: post #5

I wonder if they think of a deeper integration of this into the age binary. Currently the invocation looks extremely ugly: age -r $(go run filippo.io/torchwood/cmd/age-keylookup@main joe@example.com)

I assume once it's stabilized you'd swap the `go run` for just installing and using a binary, similar to what you're already doing with age.

Honestly not sure why I didn't do that once the tool had stabilized.

Switched to

    go install filippo.io/torchwood/cmd/age-keylookup@main
    age -r $(age-keylookup alice@example.com)

age is designed to be composable and very stable, and this shell combination works well enough, so it's unlikely we'll build it straight into age(1).

Re: Building a Transparent Keyserver

#9

Post by tptacek » Fri, Dec 19, 2025, 5:16 PM UTC

notyourancilla wrote: post #4

> The author pronounces it [aɡe̞] with a hard g, like GIF , and is always spelled lowercase. Of all the words we could've used to explain how to pronounce something

It's pronounced "aggie".

Re: Building a Transparent Keyserver

#10

Post by [deleted] » Fri, Dec 19, 2025, 5:24 PM UTC

notyourancilla wrote: post #4

> The author pronounces it [aɡe̞] with a hard g, like GIF , and is always spelled lowercase. Of all the words we could've used to explain how to pronounce something

[deleted]