Open omac777 opened 8 years ago
Sorry for the belated response. The parameter authKey in the client API is the HMAC key: https://github.com/gocircuit/circuit/blob/master/client/client.go#L56
On 22 February 2016 at 11:12, David Marceau notifications@github.com wrote:
I saw how to start the first node and join nodes using an hmac. I saw how to use the cli to create/run mkproc using an hmac on the command line. On Windows, using mkproc is not evident due to multi-line nature of description of process to run. As the only resort, we need to create an app that uses the go-circuit client api. That said the client api itself does not seem to expose the hmac capability. That capability seems to be exposed in a lower-level code-gangsta api. My question is do you expect others to use the code-gangsta directly or should the go-circuit api not expose the hmac capability and avoid using the codegangsta stuff directly?
— Reply to this email directly or view it on GitHub https://github.com/gocircuit/circuit/issues/25.
I saw how to start the first node and join nodes using an hmac. I saw how to use the cli to create/run mkproc using an hmac on the command line. On Windows, using mkproc is not evident due to multi-line nature of description of process to run. As the only resort, we need to create an app that uses the go-circuit client api. That said the client api itself does not seem to expose the hmac capability. That capability seems to be exposed in a lower-level code-gangsta api. My question is do you expect others to use the code-gangsta directly or should the go-circuit api not expose the hmac capability and avoid using the codegangsta stuff directly?