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

Algorithms: Should we have support for password based algorithms #6

Closed
jimsch opened this issue Aug 18, 2015 · 2 comments
Closed

Algorithms: Should we have support for password based algorithms #6

jimsch opened this issue Aug 18, 2015 · 2 comments

Comments

@jimsch
Copy link

jimsch commented Aug 18, 2015

JOSE has support for password based algorithms mainly for the purpose of saving private keys for later use. Given that we do not know what the introduction model for small devices is going be and given that many small devices do not have UI to enter a password, does it makes sense for use to skip having password based algorithms on the first pass of COSE. They can always be added at a later time if they are needed.

@cose-ietf
Copy link

+1, I cannot se any use cases where this would be needed.

On Tue, Aug 18, 2015 at 5:46 AM, Jim Schaad notifications@github.com
wrote:

JOSE has support for password based algorithms mainly for the purpose of
saving private keys for later use. Given that we do not know what the
introduction model for small devices is going be and given that many small
devices do not have UI to enter a password, does it makes sense for use to
skip having password based algorithms on the first pass of COSE. They can
always be added at a later time if they are needed.


Reply to this email directly or view it on GitHub
#6.


COSE mailing list
COSE@ietf.org
https://www.ietf.org/mailman/listinfo/cose

@jimsch
Copy link
Author

jimsch commented Oct 4, 2015

Removed from the draft

@jimsch jimsch closed this as completed Oct 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants