-
Notifications
You must be signed in to change notification settings - Fork 10
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
Supporting NetHSM #132
Comments
That looks very interesting! The Nitrokey devices and the NetHSM don’t
have any shared features, and NetHSM won’t be supported by libnitrokey,
right?
In this case, a separate application would probably be easier to
maintain and to test. Though it would make sense to try to create a
consistent UI for both tools (configuration, command structure, option
and command names, etc.).
From a user’s perspective, it doesn’t make a big difference whether I
have to call `nitrocli nethsm ...` or, let’s say, `nethsmcli ...`, as
long as we make sure that the UI is similar.
|
That's correct.
You mean a separate application also packaged separately? |
You mean a separate application also packaged separately?
I think that’s up to Daniel. Both could work. In theory, both
applications could also share some of the configuration and command-line
parsing code, but off the top of my head, most of that code would be
application-specific.
|
It could be an extension, mostly just to have it accessible under a unified UI. I would not consider it to belong into |
Soon we will launch NetHSM which is a network appliance HSM containing a REST interface. Would you be interested to support NetHSM? Obviously it would require entirely different dependencies.
The text was updated successfully, but these errors were encountered: