Conversation
The tokenizer command will support subcommands for displaying its version, running the server, displaying the seal key, sealing tokens, and unsealing tokens. This will allow the deployed binary to be used directly for multiple purposes without shipping seperate helpers and will simplify instructions for setting up and using the tokenizer.
|
As sanity checks, I've deployed to my timkenizer app and tested that it still runs properly. (I found that I forgot to add a new required flag to enable /.fly/fly-src.pub to be used, and fixed that). |
|
I added tokenizer to my vulnbot scanning (since it's smarter/faster than I am!). Here's what it came back with. Bug: discarded error in ParseOpenKey (tokenizer.go:112) if len(privBytes) != 32 { This creates an error but never returns it. A wrong-length key silently proceeds and will panic downstream when used as *[32]byte. go vet also flags this. Should be return nil, nil, fmt.Errorf(...). Bug: double parseFlags in version.go:16 func runVersion(cmd string, args []string) { Copy-paste artifact — parses args twice. |
lol! good catch.
yup yup, this one too. heh. thank you. Both should be fixed now. |
The tokenizer command will support subcommands for displaying its version, running the server, displaying the seal key, sealing tokens, and unsealing tokens. This will allow the deployed binary to be used directly for multiple purposes without shipping seperate helpers and will simplify instructions for setting up and using the tokenizer.
-use-flysrc=trueflag to the Dockerfile, and documentation about running the server, to continue using it with our tokenizer.