Alex Stanciu

Any updates on this? Seems like a pretty important security issue..

but you sometimes cannot control the input string and make sure there are commas in the right place. maybe I'm wrong, but this seems to behave exactly the same as:...

> as it will run as a daemon Does it though? It seems to open a new shell, and the server is only working while that shell's process is running....

Right, that's what this issue was suggesting, improving this feature and making it a bit friendlier, more prominent.. for ex, running --server would just display the output of the server,...

This app shouldn't be prescriptive in how I choose to manage my security. All I'm saying is that the current behavior is very unnatural, for any cli command. Its just...

Thanks for the details @lox, very helpful. I submitted a simple PR (#224) that solves at least the issue I described. (not really a go dev here, may not be...

Digging into this a little deeper, I found the root cause, but I still don't understand the reasoning. I've traced the code execution to this spot: https://github.com/uport-project/veramo/blob/next/packages/credential-ld/src/ld-credential-module.ts#L68 The credential I'm...

Thank you for the explanation. Preloading context maps might solve the issue temporarily but don't think it's feasible long term. There are many cases where the agent is setup once...

Actually, that's what I ended up doing. But for some reason, not sure if it's something I'm doing, but for me `event.target` is never the actual input, but its container.

Yeah, maybe even just wrapping that into a proper object with some kind of code would be useful. ``` { error: 'exists', message: 'Already exists', original: {original obj} } ```