You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any confidential data in notifier.conf.yaml file?
Could it possible to move the confidential data to a db or can at-least encrypt the data so that it will be more secured and might not required to hide the files to others.
The following rpmlint errors found in release 1.5.4 to be fixed:
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/email_auth.conf.yaml.sample 640
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/notifier.conf.yaml 640
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/email.conf.yaml 640
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/snmp.conf.yaml 640
Is there any confidential data in notifier.conf.yaml file?
Could it possible to move the confidential data to a db or can at-least encrypt the data so that it will be more secured and might not required to hide the files to others.
The following rpmlint errors found in release 1.5.4 to be fixed:
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/email_auth.conf.yaml.sample 640
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/notifier.conf.yaml 640
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/email.conf.yaml 640
tendrl-notifier.noarch: E: non-readable /etc/tendrl/notifier/snmp.conf.yaml 640
tendrl-notifier.noarch: W: non-conffile-in-etc /etc/tendrl/notifier/email_auth.conf.yaml.sample
tendrl-notifier.noarch: W: incoherent-version-in-changelog 1.5.4-1 ['1.5.4-1.el7.centos', '1.5.4-1.centos']
tendrl-notifier.noarch: W: non-conffile-in-etc /etc/tendrl/notifier/notifier.conf.yaml
tendrl-notifier.noarch: W: non-conffile-in-etc /etc/tendrl/notifier/email.conf.yaml
tendrl-notifier.noarch: W: non-conffile-in-etc /etc/tendrl/notifier/snmp.conf.yaml
tendrl-notifier.noarch: W: no-manual-page-for-binary tendrl-notifier
The text was updated successfully, but these errors were encountered: