[Infrastructures] Version control over sensitive config files

[Ryan Nowakowski]

--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 14, 2003 at 10:57:37AM -0500, ph-infrastructure@bluepenguin.us =
wrote:
> The application also has some config files with sensitive information -
> clear text passwords for communicating with other applications.  (Not
> what I'd like to see, but that's what I've got to work with.)  There are
> perhaps 60 config files; perhaps 5 of them have this kind of sensitive
> information.  The people who maintain template files and graphics should
> not be automatically allowed to see these config files
>=20
> The thought of putting those config files directly into CVS does not seem
> like a great idea, but I would like some kind of version control or
> tracking; these files control everything about how the application works.

Depending on how you set your CVS repository up, there are several ways
to allow only certain people to see certain files.  You should have some
luck doing a google on "cvs file permissions security" or "cvs group
permissions".

- Ryan

--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+Tnrh6ZA8+1/wXqMRAg1IAJ9cTQbhxi9tIyisGujVrTeZ3zlqjQCfdsC6
JcHUbhNt36WFKHLSz5og4As=
=PlV6
-----END PGP SIGNATURE-----

--M9NhX3UHpAaciwkO--