Skip to content
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.

Restrict permissions on .conf files #306

Open
unsystemizer opened this issue May 18, 2017 · 1 comment
Open

Restrict permissions on .conf files #306

unsystemizer opened this issue May 18, 2017 · 1 comment

Comments

@unsystemizer
Copy link
Contributor

Currently "others" can read config files in subdirs of FedNode's config directory.
unsystemizer added a commit to CounterpartyXCP/Documentation that referenced this issue Sep 9, 2017
@unsystemizer
Update composer, add clarifications
c27d2ff 
- Update docker composer to address CounterpartyXCP/federatednode#308
- Add a note on volumes to help with CounterpartyXCP/federatednode#309 if it happens again
- Add a note on security to address CounterpartyXCP/federatednode#306 until it gets fixed in code
- Clarify locations and accounts which need to be used to install, to help first time users
@unsystemizer
Copy link
Contributor Author

For now I mentioned in install document that fednode shouldn't be used on shared systems, but we should check how to tighten ownership and permissions in install script on extras/host_security.

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

No branches or pull requests
1 participant
@unsystemizer