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
It isn't even a big deal and since the whole operating system will be hackable, I question the point of bringing it up. However, Its worth questioning.
Its possible to create a dummy user with no permissions and run the child process from within that context. http://linux.die.net/man/8/sudo. This allows processes to be forced to go through us to do anything. This may or may not be a good thing however as it basically limits freedom and/or enable frustration for developers used to doing whatever they want. That being said, it is useful for ensuring ports and etc all run without conflicts.
As for the client permissions, that is strictly web based and not as easy to implement.
The text was updated successfully, but these errors were encountered:
How much security Silk needs is an interesting question. Running processes in a dummy user would allow us to make sure apps don't go beyond any permissions they have. Currently we don't have permissions and most apps let Silk handle their public server and routing so ports isn't a concern yet.
It isn't even a big deal and since the whole operating system will be hackable, I question the point of bringing it up. However, Its worth questioning.
Its possible to create a dummy user with no permissions and run the child process from within that context. http://linux.die.net/man/8/sudo. This allows processes to be forced to go through us to do anything. This may or may not be a good thing however as it basically limits freedom and/or enable frustration for developers used to doing whatever they want. That being said, it is useful for ensuring ports and etc all run without conflicts.
As for the client permissions, that is strictly web based and not as easy to implement.
The text was updated successfully, but these errors were encountered: