8 Commits (d4e185764f4413a085076468c9e91d6e5eaa0cee)

Author	SHA1	Message	Date
Michael Prokop	a42248419e	TT#22411 Fix spelling mistakes/typos ... s/Syncronizes/Synchronizes/ s/Wheras/Whereas/ s/configuation/configuration/ s/exisiting/existing/ s/explicitely/explicitly/ s/files files/files/ s/has has/has/ s/initialise initialise/initialise/ s/mulitple/multiple/ s/ouput/output/ s/propogates/propagates/ s/successfull/successful/ s/syncronizes/synchronizes/ s/the the/the/ s/uncommited/uncommitted/ Change-Id: Id13ec889c5de620b675e357d99066688cfc97617	8 years ago
Michael Prokop	f7501760c0	MT#22675 decrypt: ignore shared storage on CE systems ... Change-Id: Ia90d022eabc518e60643019fadc84e8570fba5b3	10 years ago
Alexander Lutay	98c94656ae	MT#19043 decrypt: check for glusterfs 'mgmt-share' instead of 'shared_config' ... We need to use some folder on glusterfs to ensure it is reachable. /mnt/glusterfs/mgmt-share is good enough here as /mnt/glusterfs/shared_config is no longer available. Change-Id: I9f604db9604af41405cfd7b088abb332a463fe4d	10 years ago
Michael Prokop	08f68c829b	MT#22361 Remember file permissions through pre-commit hook + restore-permissions helper script ... Git doesn't track file permissions (except for the executable flag). For sensitive data (like the 'ssl' directory and file 'constants.yml' with passwords included) we've to prevent non-root users from accessing those files. hooks/pre-commit is inspired and based on the implementation as present in etckeeper (and luckily we're license compatible) and takes care of storing the file permissions inside file /etc/ngcp-config/.ngcpcfg_perms. The restore-permissions helper script takes care of restoring the permissions after cloning the ngcpcfg repository via ngcpcfg itself (being actions decrypt, pull (PRO-only) + initialise (PRO-only)). It can be executed manually as well via `usr/share/ngcp-ngcpcfg/helper/restore-permissions /etc/ngcp-config/` (or wherever the according ngcpcfg repository is placed at). Regarding the commit integration: git(1) itself doesn't track file permissions, so we can't detect changes to file permissions using git itself. Our new pre-commit hook records file permissions via the .ngcpcfg_perms file. Now by just invoking it during 'ngcpcfg commit' time we can ensure that even if there have been any file permission changes in the working directory the file .ngcpcfg_perms is then up2date and committed. JFTR: The solution via the git pre-commit hook ensures that no matter whether you're using 'ngcpcfg commit …' or 'git commit …' you always get the file permissions handled via .ngcpcfg_perms. Now if you want to change file permissions in a clean working directory and commit *without* using 'ngcpcfg commit' but directly via git itself then you've to use 'git commit --allow-empty ...' and thanks to the pre-commit hook the file .ngcpcfg_perms will still be up2date. Change-Id: I84d608585c626b52112ff649893e232e441c59d8	10 years ago
Michael Prokop	f009806409	MT#22567 Create /etc/ngcp-config-crypted.tgz* files with more restrict file permissions ... The file should be accessible only to user root. Also don't leave the unencrypted file /etc/ngcp-config-crypted.tgz around. Change-Id: I82f7f36d8561d8d5e82435edb70e11170fa6c082	10 years ago
Victor Seva	eac494cb42	MT#14229 clean shellcheck warnings ... While at it spread support for testsuite Change-Id: I60c4dae5479827b0d28ffa135105d9dbdf603825	11 years ago
Michael Prokop	2deea0fb39	MT#9557 Provide timestamps in console output ... Change-Id: I5be915fa876014cbb9c792b03be325d6595daac9	11 years ago
Michael Prokop	3436c08361	Initial checkin	13 years ago