Skip to content

Potential arbitrary command execution #75

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.

Sign up for GitHub

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

Jump to bottom
Closed
mastrolinux opened this issue Mar 1, 2016 · 0 comments
Closed

Potential arbitrary command execution #75

mastrolinux opened this issue Mar 1, 2016 · 0 comments
Assignees
@matteosuppo
Labels
priority: high Resolution is a high priority type: enhancement Proposed improvement

Comments

@mastrolinux
Copy link
Contributor

Now the command line is sent via the backend to the daemon and is not signed. The #70 is an intention to fix this issue by signing every command line request to a trusted client. The signing key is server side.
@mastrolinux mastrolinux added type: enhancement Proposed improvement priority: high Resolution is a high priority labels Mar 1, 2016
@matteosuppo matteosuppo mentioned this issue Mar 1, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matteosuppo matteosuppo

Labels
priority: high Resolution is a high priority type: enhancement Proposed improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mastrolinux @matteosuppo