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

dial-only setting #660

Open
dovholuknf opened this issue May 15, 2023 · 2 comments
Open

dial-only setting #660

dovholuknf opened this issue May 15, 2023 · 2 comments
Labels
enhancement New feature or request orange

Comments

@dovholuknf
Copy link
Member

Currently devices are able to be set into 'host-only' mode which is great for a server, but client devices need to be able to control which services they are allowed to 'host' as well. As a user, I want to be able to specify which services I specifically allow to be hosted. Initial implementation could start as an "all or nothing"/binary option, but eventually I could see a need/desire for fine-grained, dynamic control over which services my client could bind, allowing me to override the controller.

@dovholuknf dovholuknf added the enhancement New feature or request label May 15, 2023
@qrkourier
Copy link
Member

This strikes me as critically important for adoption by the administrator of the device and network where the hosting tunneler is installed. In short, that administrator is not necessarily the same party that controls Ziti, and so there's no expectation that the device and network admin trusts the Ziti admin to only host friendly services for friendly Ziti clients.

@scareything
Copy link
Member

possibly specify/enable this with an identity attribute e.g. secureTunneler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request orange
Projects
Status: No status
Development

No branches or pull requests

3 participants