Hi,
I honestly did not know where to best ask this question, so please forgive
me if this is not the right place, but :
The cron job that creates weekly cppcheck reports on the libreoffice
codebase, sends an success/failure email to this list. It does so with a
gmail account. For this, it needs a gmail password, and a subscription to
the mailing list.
Up until now, that password (both for the gmail account and the list
subscription) is best-effort stored in a ~/.foo file on the vm that runs
the job.
Perhaps it should also be administered 'elsewhere', so that if the vm
crashes irrecoverably, the password is still known. Perhaps that password
should also be stored somewhere else, perhaps alongside the documents that
describe what jobs run where, or somewhere else 'safe' ?
Just my 2$.
- Maarten Hoes.
Context
- Cppcheck report password storage · Maarten Hoes
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.