Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tessera and passphrase protected keys #729

Closed
saikatsain opened this issue May 7, 2019 · 2 comments · Fixed by #765
Closed

Tessera and passphrase protected keys #729

saikatsain opened this issue May 7, 2019 · 2 comments · Fixed by #765
Assignees
Labels
0.10.0 feature User features

Comments

@saikatsain
Copy link

We had the constellation ver 0.3.2 functionality where if incorrect passphrase is provided, the constellation node waits indefinitely for the correct password to be keyed in.

The same functionality seems not to be present in tessera. Is there a possibility that this feature will be made available anytime sooner.

The background of the question is, we were able to securely pass the passphrase when using constellation using the feature in question but with tessera, we are forced to pass the password as an argument which can be easily extracted from the process monitor.

@prd-fox
Copy link
Contributor

prd-fox commented May 7, 2019

Nice catch. This is definitely a feature that is needed. As for when, I don't have any timeline - if you get any spare time, pull requests are always welcome :)

@prd-fox prd-fox added the feature User features label May 7, 2019
@melowe
Copy link
Contributor

melowe commented May 13, 2019

It sounds like we'd also want this for the remote enclave as well as the tessera app jar.

The general issue of being forced to provide an arg 100% agreed. Prompting the user for input sounds fine. But 'waits indefinitely for the correct password' I think it should fail after N attempts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.10.0 feature User features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants