glome-login refers to a mysterious "embedded" service key

[delroth]

In glome-login --help I spotted the following:

 -k KEY    use KEY as the hex-encoded service key (defaults to the embedded key)

I can't seem to find any reference to what this embedded key is and where it lives, and from looking at the source code I suspect it might not exist. Could you clarify the documentation and/or remove this?

[bluecmd]

Internally we do not use a config file, we instead call login_run straight away with hardcoded public keys - that's where the awkward description comes from.

Right now -k is parsed before config is read, so the config file takes precedence - which is a bit odd.

I'd suggest we:

• Change the description of -k to say .. (defaults to key from configuration)
• Change that -k overrides the key possibly present in the configuration file

[burgerdev]

The last occurrence I knew of has been removed in #73.