Re: [Nagios-devel] Need a way to prevent custom object

[Guest]

--=-KLOVNKppI40L6iMKLFv+
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

hey guys,

On Tue, 2007-01-02 at 21:21 -0600, Ethan Galstad wrote:
> >=20
> > Still have the problem of how to make the custom variable useful
> > though since it can't be on the command line for the same reason.
> >=20
> > -- rouilj
> > John Rouillard
>=20
> Yeah, probably the only safe way to do it would be to pass the name of a=20
> file (which contains the password, etc. and is locked down) to the=20
> command that's being run. As you noted, command lines and environment=20
> vars are viewable by other processes/people.

just fyi, there was a similar-but-slightly-broader-scoped discussion on
the nagios-plugins devel list a few months back. the consensus is that
we'll be extending the core plugins and probably providing hooks for
3rd party plugins to use an updated configuration file format
(orthogonal to the checkcommands stuff) which will let the admin specify
additional cmdline arguments which will then be fed to getopt without
being put on the command line. so you could have something like:


[check_mysql]
user=3Droot
password=3Dsupersecret

and so on.

while there might still be an argument for passing/hiding custom
variables through nagios' config, i thought i should mention this so we
don't have multiple groups of people doing the same but slightly
different thing seperately.



sean

--=-KLOVNKppI40L6iMKLFv+
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

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

iD8DBQBFocFsynjLPm522B0RAhvYAJ45yUA+k0KgUPFhnay9piG++sKsvgCaAxJs
emHcBFJcvlEKA818Yn5XQtE=
=bpXJ
-----END PGP SIGNATURE-----

--=-KLOVNKppI40L6iMKLFv+--






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]