a secret could happen due to signatures. Anyways. Would love to hear why this couldn’t work but also if I’m missing some easy way to pass secrets around in a way that they are easily used in both applications and simple bash scripts ect. 🧵/🧵
A pain point in systems that have bugged me for a long time is secretes management. Apps like Vault are nice but some of the admin tasks could be much simplified. Would love to see somebody like @oxidecomputer who controlled the whole stack some up with something simpler. 1/🧵
infrequent. 2)adding and authorizing secrets and application authorizations would happen totally out of band. 3) the api would be simple and could be used in applications or scrips with only a couple of lines. 4) deauthorizing an app version from accessing 4/🧵
I imagine a system where any app could make a request to a special zdoor with the secrete id. And then get the secrete back. A single call, no unlocking ect. The “magic” would be that the gz could inspect the process making the request. The gz would get a signature of 2/🧵
@toddanglin From there is a matter of adding loops, flow control, functions ect. Have them create their own challenges. And then split into groups. Get them thinking more about how to solve the problem than how to manipulate the language. 3/3
@toddanglin Errors or having to spend hours setting up editors/environments, figuring out nuances of libraries, ect ect. With thinks like the Lego and blocky it can be start programming, Bluetooth pair, and deploy. In 60 minutes you can make a simple robot move forward 2/
@nahumshalman@Tailscale@illumosorg Nice! I put together a little bootstrap script for anybody that might come across this later... https://t.co/hmglTeYGMU
@nahumshalman for @Tailscale on @illumosorg I was unable to get exit nodes to work without setting to user mode tunnel. Might be worth dropping a note in the blog or smf xml that the command should be `tailscaled --state /opt/tailscale/statefile --tun=userspace-networking`