-
Notifications
You must be signed in to change notification settings - Fork 15
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
sshnp - list devices #184
Comments
A notification from clients which daemons respond to, or put an atKey shared with the client/manager atsign |
I like the notification route best.. This way only listening sshnpd's respond.. using an atKey could leave some "junk" in place. |
I'd like to see a list of all of my devices, with the ones which respond marked as such Junk is a valid concern but could be mitigated with a suitable ttl e.g. N days? i.e. a combination of
|
I've started the work on this based on what @gkc listed above. Will resume in this sprint after addressing some of the other issues first. |
Last step is less related to this issue so I've made it a separate issue so that this can be closed |
Is your feature request related to a problem? Please describe.
Can't really tell what devices can be connected to, especially in an organization where you may have had an admin setup sshnpd for you.
Describe the solution you'd like
A subcommand / flag which allows you to list available devices for connecting to.
Describe alternatives you've considered
No response
Additional context
Depending on the implementation, the client may have to state that only devices with version greater than x.x.x will be listed...
Tasks
The text was updated successfully, but these errors were encountered: