You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently had a group discussion about using CROPS, and somebody mentioned that for our use case of a build server, the built in VNC server would be undesirable from a bloat / security perspective.
It is my understanding this service wont run by default, so an unauthorized user or code would be required to invoke it anyways. However, you can't really argue that its unnecessary bloat for this use case.
So I started to wonder that perhaps there should be a toggle to include or exclude it. On a local PC the VNC could be a useful to the development workflow. However for a build server, it wouldn't necessarily need it.
So just wanted to capture this idea, and see if anybody wanted to discuss perhaps providing a better user story in this case.
Thanks
The text was updated successfully, but these errors were encountered:
richnetdesign
changed the title
headless / cli only image tags (remove tightvnc)
headless / cli only image toggle (remove tightvnc)
Feb 9, 2022
I recently had a group discussion about using CROPS, and somebody mentioned that for our use case of a build server, the built in VNC server would be undesirable from a bloat / security perspective.
It is my understanding this service wont run by default, so an unauthorized user or code would be required to invoke it anyways. However, you can't really argue that its unnecessary bloat for this use case.
So I started to wonder that perhaps there should be a toggle to include or exclude it. On a local PC the VNC could be a useful to the development workflow. However for a build server, it wouldn't necessarily need it.
So just wanted to capture this idea, and see if anybody wanted to discuss perhaps providing a better user story in this case.
Thanks
The text was updated successfully, but these errors were encountered: