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.

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

authentication & security #17

Open
jrandall opened this issue Feb 18, 2014 · 1 comment
Open

authentication & security #17

jrandall opened this issue Feb 18, 2014 · 1 comment
Labels
enhancement

Comments

@jrandall
Copy link

As the terminal session could contain sensitive information (e.g. passwords, private data, etc), permissions on files and authentication to the backend servers (i.e. redis) should be employed.
nc6 added a commit that referenced this issue Mar 14, 2014
@nc6
Add permissions for file-based destinations.
c60a2cd 
User projects now have only user permissions, whereas global ones are
readable and writable more generally.

This is reflected in listed projects.

This partially addresses issue #17, although only for files.
@nc6
Copy link
Owner

nc6 commented Mar 14, 2014

Permissions on files now addressed. Redis lacks any real authentication so to speak, so for now the answer is to not use redis for anything where you may type sensitive information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jrandall @nc6