disable_core_dumps() and -q

[Sam Roberts]

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

Well, any thoughts?

On Sun, Mar 26, 2000 at 02:23:15PM -0500, sroberts wrote:
> =20
>  disable_core_dumps() appears to want to honor opt.quiet, and not whine if
>  --quiet was specified, but at least the first call doesn't.
> =20
>  It's called before options are parsed, currently, so even gpg --help
>  gives the warning. Would it be ok to move it's call to after options
>  are parsed? It doesn't look to be a security problem, since no passwords
>  are read in during options parsing, and the options are visible from
>  ps listings anyhow (at least to those with permissions to see your
>  core files, I'd guess).
> =20
>  It's quite annoying to me, and I can just chop the warning out, but...
> =20

--=20
Sam Roberts, sroberts at uniserve dot com, www.emyr.net/Sam

--VG2vq6E6ONRkAtlJ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (QNX)
Comment: For info see http://www.gnupg.org

iD8DBQE450hqvXDyoMMkV34RAeALAJ9WV2O4wTZCO3JCbNb76dVkeAR7LACfdfLq
0UKtY2QXMhKYvgbENYtqVms=
=2XyK
-----END PGP SIGNATURE-----

--VG2vq6E6ONRkAtlJ--