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

Implement security configuration #2333

Open
ddevault opened this issue Jul 23, 2018 · 3 comments
Open

Implement security configuration #2333

ddevault opened this issue Jul 23, 2018 · 3 comments
Labels
enhancement New feature or incremental improvement

Comments

@ddevault
Copy link
Contributor

The commands and config file details can be the same as it was on 0.15, but we should change how we enforce them - only commands run by sway (i.e. via the exec command) should be able to have access to most secure features. We should do this by opening the wayland socket on their behalf and transferring the file descriptors through exec via the WAYLAND_SOCKET environment variable.

@ddevault ddevault added this to the sway 1.0-beta.1 milestone Jul 23, 2018
@emersion emersion added the enhancement New feature or incremental improvement label Jul 24, 2018
@ddevault
Copy link
Contributor Author

ddevault commented Oct 8, 2018

Taking 1.0-beta.1 off of this because the plan sucks. New plan under discussion here:

swaywm/wlr-protocols#27

@ddevault ddevault removed this from the sway 1.0-beta.1 milestone Oct 8, 2018
@emersion
Copy link
Member

@emersion
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or incremental improvement
Development

No branches or pull requests

2 participants