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

Don't touch aliases #1010

Merged
merged 2 commits into from
Jan 11, 2017
Merged

Don't touch aliases #1010

merged 2 commits into from
Jan 11, 2017

Conversation

SYN-cook
Copy link
Contributor

@SYN-cook SYN-cook commented Dec 27, 2016

.bash_aliases is called from .bashrc and can contain any kind of bash script. As a consequence, this file (which usually only exists if created deliberately) should be restricted as read-only.

SYN-cook added 2 commits December 27, 2016 20:33
manipulating aliases means manipulating users (to do things they don't want to do)
@SYN-cook SYN-cook closed this Dec 28, 2016
@SYN-cook
Copy link
Contributor Author

SYN-cook commented Dec 28, 2016

Closed, because this file on most systems doesn't exist (e.g. default Debian/Ubuntu installation), and read-only wouldn't prevent creation of a new .bash_aliases file.

@SYN-cook
Copy link
Contributor Author

SYN-cook commented Jan 10, 2017

Sorry, dear rest of the world, for sharing my confusion with you. But having .bash_aliases set read-only is the right thing to do, even if on most systems it doesn't exist.

@SYN-cook SYN-cook reopened this Jan 10, 2017
@netblue30 netblue30 merged commit 4a4f091 into netblue30:master Jan 11, 2017
@netblue30
Copy link
Owner

Merged, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants